Hi guys,
It seems that the avalon:meta tag generates the MyServiceProvider.xinfo inside following packageL
com.mycompany.component.impl.mycompoent.MyServiceProvider
and therefore expects MyServiceProvider to abide by the above package hierarchy.
Correct.
I wanted to use com.mycompany.component.mycomponent.impl.MyserviceProvider instead.
what happens is that I get the following error when I run maven with a AbstractMerlinTestCase...
[junit] org.apache.avalon.composition.model.ModelException: Cannot load component type because the type class com.mycompany.component.impl.mycomponent.MyServiceProvider does not exist in the classloader.
You getting this because the xinfo is in the classpath but the class is not. Merlin is attempting to load the class as a candidate but the class does not exist.
Is there a way to have *.xinfo generated to my desired package
hierarchy: com.mycompany.component.mycomponent.impl.MyServiceProvider ?
Not sure what you mean by "desired". If you have package x.y.z and class Widget then you will get x.y.z.Widget.xinfo. The existence of the xinfo does not mean that the component will be deployed - it simply declares that a component of a particular type exists.
Cheers, Stephen.
regards Korosh
--------------------------------------------------------------------- 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]
