Gert Vanthienen wrote:
>
> Monika,
>
> I think this might be related to a version mismatch between your
> products and the ServiceMix instance you are targeting with the mvn
> jbi:projectDeploy goal.
> Actually, the easiest way to deploy a SA on ServiceMix is by using the
> hotdeploy instead of mvn jbi:projectDeploy. Could you:
> - stop ServiceMix
> - delete everything inside the data directory (this essentially gives
> you a clean copy of ServiceMix again)
> - start ServiceMix
> - copy the SA zip file into the hotdeploy directory
>
> Does this fix you problem?
>
> Regards,
>
> Gert
> -----
> ---
> Gert Vanthienen
> http://gertvanthienen.blogspot.com
>
You maybe right that there is version mismatch. Version of ServiceMix I have
installed is 3.3 , but it seems the latest version of the maven plugin is
3.2.3 I can locate is.
Should I delete EVERYTHING in the data directory? Because as I mentioned in
my followup post, this exactly what I noticed after I got the exception -
data directory is gone. I still have all zip files in hotdeploy directory,
but none of the components are deployed (I see nothing in the log no through
the jconsole) when I restart ServiceMix.
Monika
--
View this message in context:
http://www.nabble.com/Class-not-found%3A-org.apache.servicemix.eip.EIPBootstrap-in-tutorial-exercise-tp20566412p20566861.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
