I think your problem is unrelated to the maven plugin.
It seems your component uses the BaseBootstrap for
its bootstrap, right ? The problem is that this class is only
available in the servicemix-shared SL, but shared libraries
are not available at bootstrap time. You should copy
this class inside your own component, or just remove
the bootstrap class (the plugin will create it for you).
On 2/14/07, Tam, William <[EMAIL PROTECTED]> wrote:
I am running 3.2 snapshot. I tried with and without "deployDependencies" but I had no
luck with "mvn jbi:projectDeploy".
On the server (started by bin/servicemix.bat), I saw NoClassDefFoundError. Any
ideas? Thanks.
ERROR - InstallationService - Deployment of Component failed
java.lang.NoClassDefFoundError: org/apache/servicemix/common/BaseBootstrap
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
4)
at org.apache.xbean.classloader.JarFileClassLoader.access$200(JarFileCla
ssLoader.java:48)
at org.apache.xbean.classloader.JarFileClassLoader$6.run(JarFileClassLoa
der.java:272)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.xbean.classloader.JarFileClassLoader.findClass(JarFileClas
sLoader.java:224)
at org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiPa
rentClassLoader.java:200)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.apache.servicemix.jbi.framework.InstallerMBeanImpl.createBootstra
p(InstallerMBeanImpl.java:118)
at org.apache.servicemix.jbi.framework.InstallerMBeanImpl.<init>(Install
erMBeanImpl.java:66)
at org.apache.servicemix.jbi.framework.InstallationService.initializeIns
taller(InstallationService.java:445)
at org.apache.servicemix.jbi.framework.InstallationService.doInstallComp
onent(InstallationService.java:427)
at org.apache.servicemix.jbi.framework.InstallationService.doInstallArch
ive(InstallationService.java:378)
at org.apache.servicemix.jbi.framework.InstallationService.install(Insta
llationService.java:303)
at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchi
ve(AutoDeploymentService.java:276)
at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateExter
nalArchive(AutoDeploymentService.java:201)
at org.apache.servicemix.jbi.container.JBIContainer.updateExternalArchiv
e(JBIContainer.java:473)
at org.apache.servicemix.jbi.container.JBIContainer.updateExternalArchiv
e(JBIContainer.java:483)
at org.apache.servicemix.jbi.framework.AdminCommandsService.installCompo
nent(AdminCommandsService.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.jav
a:216)
at org.apache.servicemix.jbi.management.BaseStandardMBean.invoke(BaseSta
ndardMBean.java:318)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImp
l.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
BeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784
)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnecti
onImpl.java:1408)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectio
nImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run
(RMIConnectionImpl.java:1245)
at java.security.AccessController.doPrivileged(Native Method)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(R
MIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImp
l.java:782)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
66)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
.java:707)
at java.lang.Thread.run(Thread.java:595)
-----Original Message-----
From: Anders Hammar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 14, 2007 10:02 AM
To: [email protected]
Subject: RE: deployment?
Haven't tried the 3.1 release, but for 3.0 I defined the 'deployDependencies'
configuration of the plugin to false. This is explained here:
http://incubator.apache.org/servicemix/maven-jbi-plugin.html
(look under "Running under ServiceMix")
Have you tried that?
/Anders
Bompart Cedric-2 wrote:
>
> Ah cool thanks a lot!! The problem of the hot deployment was the missing
> shared components.
>
> For the Maven jbi plugin, I've just created a SA and a LW SU projects with
> the archetype maven tasks. And after I've used the jbi:projectDeploy with
> the -DforceUpdate=true for subsequence deployment, and it failed.
>
> Regards,
> Cedric.
>
> -----Message d'origine-----
> De : Guillaume Nodet [mailto:[EMAIL PROTECTED]
> Envoyé : 14 February 2007 11:37
> À : [email protected]
> Objet : Re: deployment?
>
> There are mainly two ways to deploy something on ServiceMix:
> * use the hot deployer by copying the file in the /deploy or /install
> folder
> * use JMX, directly, via ant tasks, or maven.
>
> Wrt to the jbi:projectDeploy goal, do you have a reproducible test case
> where it fails ?
>
> For your problem wrt to the hot deployer, make sure you have copied the
> servicemix-shared SL to the install folder. This is a dependency of all
> servicemix components.
>
> On 2/12/07, Bompart Cedric <[EMAIL PROTECTED]> wrote:
>> Hello,
>>
>> Sorry to ask a so trivial question but how do you deploy a SA project
>> during the development cycle with SM 3.1?
>>
>> So far I've using "mvn jbi:projectDeploy" but only for the first time,
>> otherwise for subsequence deployment I need to stop SM, remove the data
>> folder and restart SM... a little bit boring... :-)
>>
>> I've tried "mvn -DforceUpdate=true jbi:projectDeploy", but I'm getting
>> this:
>>
>> [INFO] Unable to deploy project, Error accessing ServiceMix
>> administration
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message";
>> version="1.0
>> ">
>> <jbi-task-result>
>> <frmwk-task-result>
>> <frmwk-task-result-details>
>> <task-result-details>
>> <task-id>shutDown</task-id>
>> <task-result>FAILED</task-result>
>> <message-type>ERROR</message-type>
>> </task-result-details>
>> </frmwk-task-result-details>
>> </frmwk-task-result>
>> <component-task-result
>> xmlns="http://java.sun.com/xml/ns/jbi/management-message";
>> >
>> <component-name>servicemix-lwcontainer</component-name>
>> <component-task-result-details>
>> <task-result-details>
>> <task-id>shutDown</task-id>
>> <task-result>FAILED</task-result>
>> <message-type>ERROR</message-type>
>> <task-status-msg>
>> <msg-loc-info>
>> <loc-token/>
>> <loc-message>Service Unit 'test-lw-su' is not deployed</loc-message>
>> </msg-loc-info>
>> </task-status-msg>
>> </task-result-details>
>> </component-task-result-details>
>> </component-task-result>
>> <component-task-result
>> xmlns="http://java.sun.com/xml/ns/jbi/management-message";
>> >
>> <component-name>servicemix-eip</component-name>
>> <component-task-result-details>
>> <task-result-details>
>> <task-id>shutDown</task-id>
>> <task-result>FAILED</task-result>
>> <message-type>ERROR</message-type>
>> <task-status-msg>
>> <msg-loc-info>
>> <loc-token/>
>> <loc-message>Service Unit 'test-eip-su' is not deployed</loc-message>
>> </msg-loc-info>
>> </task-status-msg>
>> </task-result-details>
>> </component-task-result-details>
>> </component-task-result>
>> </jbi-task-result>
>> </jbi-task>
>>
>>
>> Is there a more simple way to deploy/undeploy a project? Like remove a
>> file, copy a file, etc.
>>
>> I've tried to copy the SA jar/zip to the deploy directory but it
>> complained that I need to deploy the servicemix-eip, servicemix-script
>> and servicemix-lwcontainer. So I've copied them from the components
>> folder, but same thing...
>>
>> My SA project contains a LW SU (using the provided Maven archtype), EIP
>> SU (using the provided Maven archtype) and Script SU (based on the EIP
>> one because no Maven archetype).
>>
>>
>> I'm sure it's easy but... :-)
>>
>> Regards,
>> Cedric.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/
>
>
>
>
--
View this message in context:
http://www.nabble.com/deployment--tf3214745s12049.html#a8966504
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
