| Custom scope support in blueprint [message #674149] |
Wed, 25 May 2011 19:36  |
Brian Messages: 2 Registered: May 2011 |
Junior Member |
|
|
|
Hi, I am currently working on a project that requires the use of a custom scope in blueprint as specified in the attached blueprint XML document. I managed to get this working on Apache Aries by providing an org.apache.aries.blueprint.NamespaceHandler, via the OSGi service registry, to any blueprint container that needs to process that particular namespace. I am now hoping that I can get this working on Eclipse Gemini as well, in a similar manner if possible. I am hoping to be able to provide my own implementation of an org.springframework.beans.factory.xml.NamespaceHandler, once again via the service registry, that would be called to register my custom scope. Is this a feasible approach? If not, then how can I support my blueprint custom scope in Gemini?
|
|
|
|
| Re: Custom scope support in blueprint [message #682515 is a reply to message #681824] |
Sat, 11 June 2011 06:18  |
Brian Messages: 2 Registered: May 2011 |
Junior Member |
|
|
Hi Costin,
Thanks for the response. The requirement for my project is to use blueprint exclusively, and I am able to do this when using Gemini, but only with a work around. I have an implementation of a BeanDefinitionDecorator in which I perform all of the Spring-specific configuration for a custom scope. This works fine, except that there is currently no mechanism to allow me to register it so that it gets called when a custom scope, with the correct namespace, is used.
My work around is to always use a dummy custom attribute along with the custom scope on the bean definition. This allows my BeanDefinitionDecorator to be called in order to drive the configuration of the custom scope. IMO I should not need to use this work around, especially as what I am trying to do is well within the confines of the Blueprint specification. I have therefore raised a bug, 348776, against Gemini to address this issue.
|
|
|
Powered by
FUDForum. Page generated in 0.01639 seconds