Date: 2004-06-24T06:31:22 Editor: 200.69.248.193 <> Wiki: Jakarta HiveMind Wiki Page: FrequentlyAskedQuestions URL: http://wiki.apache.org/jakarta-hivemind/FrequentlyAskedQuestions
no comment Change Log: ------------------------------------------------------------------------------ @@ -66,10 +66,4 @@ DanielFeist: Yes that's a good workable solution the downside it that its not 100% IOC i.e. the !DataSource is not being injected but rather work has to be done in the services init method to obtian the datasource. In !HiveMinds current state that is the best solution I suppose. I do believe though that the ability to be able to inject other objects that are not services or configurations (obtained from a lookup/factory service) is an important functionality that should certainly be considered as not everything we might want to use and inject can or should de represented as a service. -DanielFeist: I've just been looking at the BeanFactory and translator and it would seem that you have actually started implementation of something that allows the us to obtain objects from a factory. The PiplineFactoryService, for example uses, in its configuration contributions, beans obtained from the BeanFactory. This is a good and works well for the needs of the PipelineFactoryService configuration but it would be far far more flexible to be able to obtain an object from any factory and not just from a BeanFactory. - -What i would suggest is the following: - -1) That we try to work out a simple way of doing the same sort of thing but allowing the use of arbitary user implemented factories (not neccessarly implementing BeanFactory). Maybe it would be possible to extend the !ObjectTranslator so that it optionally returns an object obtained from a factory or maybe a seperate translator would be best? I personally would probably choose to rename and extend the bean translator to accomplish the additional functionality. (Only making changes to the translator while leaving the rest of the new BeanFactory code as it is.) - -2) If this can be achieved without over complicating things we could then add to the BuilderFactory schema the element neccessary to be able to inject these objects. +DanielFeist: I've just been looking at the BeanFactory and translator and it would seem that you have actually started implementation of something that allows the us to obtain objects from a factory. The PiplineFactoryService, for example uses, in its configuration contributions, beans obtained from the BeanFactory. This is good and works well for the needs of the PipelineFactoryService configuration but it would be far more flexible to be able to obtain an object from any POJOF (plain old java object facotry) and not just from a BeanFactory. Is there anyway of doing the same sort of thing but allowing the use of arbitary user implemented factories (not neccessarly implementing BeanFactory)? Maybe it would be possible to extend the !ObjectTranslator or !BeanTranslator to do this. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
