Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide mechanism for injecting a Serializable Provider<T> or ObjectFactory<T> via XML [SPR-6998] #11663

Closed
spring-projects-issues opened this issue Mar 17, 2010 · 1 comment
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Mar 17, 2010

Mike Youngstrom opened SPR-6998 and commented

This issue is related to #11417 though I think it should work for non EL situations as well. To fix this I would be happy if something like ObjectFactoryCreatingFactoryBean were created for the Provider<T> interface as well. And that both were enhanced to make the respective Provider or ObjectFactory serializable similar to what can be done with @Inject/@Autowired with #10747. That said if the decision were made to only support this through EL (#11417) that would be fine too though it may be less risky to simply make ObjectFactoryCreatingFactoryBean return a serializable ObjectFactory sooner?


Affects: 3.0.1

Issue Links:

Referenced from: commits 16eb915

@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Mar 30, 2010

Juergen Hoeller commented

As of Spring 3.0.2, ObjectFactoryCreatingFactoryBean creates a serializable ObjectFactory reference. I've also added a ProviderCreatingFactoryBean, exposing a serializable JSR-330 Provider reference.

We'll use #11417 for tracking the general effort of detecting an ObjectFactory/Provider dependency with <property> and <constructor-arg>, populated with an external EL value or any other bean definition value. This is less trivial since bean definition values may have nested value structures...

Juergen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants