Julien:
Any class can be a component - all that you need to to add a xinfo file. You can create this manually or use javadoc tags to automate the process. A simple xinfo for the root object you describing could look like:
<type>
<info>
<name>whatever</name>
<lifestyle>singleton</lifestyle>
</info>
<dependencies>
<dependency key="hello" type="tutorial.Hello" version="1.1"/>
</dependencies>
</type>The only constraint is that the object has a null constructor (and chances are that even this will be eliminated in the near future).
Cheers, Steve.
Mathews Julien wrote:
Hi Guys,
I want to know if the starting point of an application can be a non component class.
For example say I want to use the HelloComponent with a class that is not a component. Normally we define the dependencies for a component using the avalon meta tags.
Can we define a component as a dependency for a non component class and modify the xml property files, so that the non component class is started by the container as the starting point.
Thanks
_________________________________________________________________
Let the new MSN Premium Internet Software make the most of your high-speed experience. http://join.msn.com/?pgmarket=en-us&page=byoa/prem&ST=1
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
