On Monday 03 November 2003 20:33, Magnus Johansson wrote: > As I understand it the meta files generated based on the @avalon javadoc > tags differ from the ones generated with the @phoenix tags. How do I go > about if I want to use @avalon tags to generate meta files compatible with > released versions of Phoenix?
I don't think you can at present day. You can use both in the source though. > If I specify a component as having the lifestyle "transient" when and how > is the first instance of the component configured and created if I use > Phoenix as my container and does that differ from Merlins way of handling > things? Phoenix have no notion of "transient", all named instances are "singletons", and created on start-up. Merlin is much more flexible. For "singleton" lifestyle, I think (but not sure) that they are created on start-up, where as "transient" would be created upon requested over the ServiceManager. Also, I think that Merlin still supports the Phoenix block info format, so if you use the @phoenix tags, they probably work in Merlin, but not vice versa. > And now a more general question. Is it possible to configure and create an > instance of a component during runtime,..That is a component that is not > configured and instanciated when the container is started? IIUC, you want to provide the Configuration object to a newly created instance at "some point", for instance when the Configuration can be composed?? In such case, I believe that you need to look into how you nest Merlin within other applications, such as your component that knows how to create the Configuration. This is a little bit beyond my experience, but I think Stephen will fill you... Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
