Magnus Johansson wrote:
Hi,
I have some general questions about Avalon and the Avalon Meta package that I hope someone can help me out with.
As I understand it the meta files generated based on the @avalon javadoc
tags differ from the ones generated with the @phoenix tags.
Correct. The @avalon tages are used to describe a <type> whereas @pahoenix describes a <blockinfo>
How do I go about if I want to use @avalon tags to generate meta files compatible with released versions of Phoenix?
You can include a [classname].xnfo containing the <blockinfo> description and when you generate the @avalon tags, you can set of property to tell the plugin to generate and output under [classnamer].xtype. This allows coexistance - if you component is depoyed in Merlin it will pickup the xtype in preference to the xinfo - check the plugin docs for details on available properties.
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 does not support transient components. Merlin will trigger instantiation of a transient either (a) on request via a service manager lookup, or (b) as a result of a activation policy declared on the component directive .. e.g.
<component name="fred" type="Demo" activation="startup"/>
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?
Yes - but if you embedding merlin - i.e. you code is in container space. I've
started on container side plugins that will allow this sort of activity much
more easily - but you will have to wait a bit because some structural pieces
are still needed at the level of the kernel. Basically what this allow is
container-side compoents that have complete access to the SPI classloader.
That will enable things like scriptable components, dynamic programatic
component handling, etc.
Cheers, Steve.
Regards, Magnus
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
