Hi Gert, There is no problem when I hotdeploy another version of the same SA. When I hot deploy the new version, within the same sa folder (data/smx/service-assemblies/jbsubmission-sa ) another version of the the deployed SA is created alongside the older version. These two version dont conflict. However the trace of the previous version dosent make the undeployment clean.
Regards, Ganesh Gert Vanthienen wrote: > > Ganesh, > > Do you have a problem with this when you redeploy another version of the > SA or something? Normally, the new version should go in a new directory > and shouldn't really be blocking something else there. What version of > ServiceMix are you using? Are you still on a 3.0.x release as in the > original message? > > I'd usually advice people to use hotdeploy instead, because it's less > likely to fail (no upload over the network) and because it's easier to > see what has been deployed on an instance (by just looking at the > contents of the hotdeploy directory. Not sure it will fix your > specific problem here though. > > Regards, > > Gert > > navigator09 wrote: >> Hi, >> >> I am trying to undeploy service-assemblies without shutting down service >> mix >> by using the ant command. The command is as follows >> >> ant -f servicemix-ant-task.xml -Dsm.username=smx -Dsm.password=smx >> -Dsm.service.assembly.name=jbsubmission-sa undeploy-service-assembly >> >> >> After the execution of the command, a message that the serviceassembly >> and >> its constituent jsr-181 is undeployed is displayed on the servicemix >> console.But the data/smx/service-assemblies still containes the >> jbsubmission-sa directory. The reason for this is the dependent jars >> packaged inside the jsr181-su which are being still used by servicemix ( >> mentioned in the below subject). The rest of the content is deleted. Is >> it >> possible to have a complete undeploy without shutting down servicemix? >> >> Regards, >> Ganesh >> >> >> gnodet wrote: >> >>> Components that use an XBean based SU can create a classloader >>> for the SU. The jbi maven plugin will help a bit and package the >>> jars in the SU. However, there is still one manual step involved >>> (which should be automatic in 3.1). You need to add the following >>> tags at the top of your xbean.xml / servicemix.xml file in the SU: >>> <classpath> >>> <location> xxx </location> >>> </classpath> >>> >>> where xxx is the path of the jar relative in the SU zip. >>> So you should have: >>> <classpath> >>> <location>lib/oro-2.0.8.jar</location> >>> <location>lib/commons-net-1.4.1.jar</location> >>> </classpath> >>> >>> On 10/5/06, robottaway <[EMAIL PROTECTED]> wrote: >>> >>>> I have a SU which uses the ftp poller in a light weight container. When >>>> deploying the SA I have created I get exception: >>>> java.lang.NoClassDefFoundError: org/apache/commons/net/SocketClient. I >>>> included dependencies >>>> >>>> <dependency> >>>> <groupId>oro</groupId> >>>> <artifactId>oro</artifactId> >>>> <version>2.0.8</version> >>>> </dependency> >>>> <dependency> >>>> <groupId>commons-net</groupId> >>>> <artifactId>commons-net</artifactId> >>>> <version>1.4.1</version> >>>> </dependency> >>>> >>>> In the SU's pom.xml. What else do I need to do for the FTP Poller to >>>> work? >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/Problem-with-dependencies-tf2386188.html#a6651741 >>>> Sent from the ServiceMix - User mailing list archive at Nabble.com. >>>> >>>> >>>> >>> -- >>> Cheers, >>> Guillaume Nodet >>> >>> >>> >> >> > > > > ----- > --- > Gert Vanthienen > http://gertvanthienen.blogspot.com > -- View this message in context: http://www.nabble.com/Problem-with-dependencies-tp6651741p20316995.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
