On Wednesday 03 March 2004 07:55, Stephen McConnell wrote:
Cameron Fieber wrote:
I'm using the avalon meta plugin packaged with merlin 3.2.5. It is generating .xinfo files for my components but not .meta files.
Why do you need a .meta? - this is only only needed if your describing a factory that is loaded as a plugin via the repository system.
Because I told him :o) perhaps incorrectly so.
Can Merlin resolve that cornerstone-thread-impl is dependent on excalibur-thread ?
I thought it couldn't, unless the .meta with the dependency declarations were present....
The excalibur-thread-impl package comes pre-bundled with a phoenix compatible xinfo which is recognized by the avalon-meta package. This means that as a component is declaring itself as a ThreadManager which in term reference api classes in excalibur threads. The implementation uses Excalibur Threads implementation classes to establish the thread manager. The actual structural dependency between cornerstone thread-manager-impl and excalibur-thread is declared in the block definition's <classloader>.
But at the end of the day - doing a api/impl split on Excalibur Threads is a good move as it will help cleanup the overall classloading implications that this service currently introduces.
Cheers, Steve.
Niclas
--
|------------------------------------------------| | 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]
