Gert, I will continue to use Maven for the build procedure, but I will use Ant to deploy to the hotdeploy directory. Is it sufficient to copy all ZIP files in the SA/target/classes directory ?
Regards, Stefan. Gert Vanthienen wrote: > > Stefan, > > No, we definitely recommend using Maven. The JBI tooling will generate > the jbi.xml descriptors you need and can take care of JBI packaging. What > are the drawbacks you encountered with the archetypes? > > The only exception is the jbi:projectDeploy. It's often much more > convenient to deploy SAs using hotdeploy -- it makes it easier to see > what's deployed without having to use JMX and moving something from > staging to production is as easy as copying the file. > > If you delete the data directory, ServiceMix looses all of its data > (deployments, logging, pending messages in ActiveMQ, ...). You should > only use it if everything else fails. However, there too, hot-deployment > is more convenient because after deleting the data directory, every SA in > the hotdeploy folder will just get reinstalled without having to use Maven > again. > > Regards, > > Gert > > > stlecho wrote: >> >> Hi, >> >> I like your "but from time to time it doesn't work" quote. I am new to >> ServiceMix and I followed the steps explained in the Tutorial section of >> the website. Therefor I'm using the mvn archetypes, but apparently they >> have some drawbacks :o(. Is it a best practice to use Ant instead of mvn >> ? If yes, are there some build files/targets I could re-use ? >> >> I suppose that with "a clean install" you're removing files/directories >> from ServiceMix. How do you know which files/directories should be >> removed: all versions of all dependencies, all versions of the SA, all >> versions of the SUs, ... ? But what about dependencies that are shared >> with other SAs ? >> >> Regards, Stefan. >> >> >> lhe77 wrote: >>> >>> Sure you can, but from time to time it doesn't work. I also never use >>> the mvn >>> jbi:deploy archetype. I always do a clean install and copy the SA over >>> to the >>> hotdeploy folder. This is by far the more stable way. >>> >>> regards >>> Lars >>> >>> >>> >>> Am Mittwoch 20 August 2008 17:47:45 schrieb stlecho: >>>> Does this mean that I can not re-deploy an existing SA without >>>> stopping, >>>> cleaning and starting ServiceMix ? >>>> >>>> lhe77 wrote: >>>> > All deployment will be done to the data folder inside servicemix >>>> install >>>> > folder. So if you run in trouble check if you can delete the assembly >>>> > from the >>>> > data/smx/service-assemblies/ folder and restart smx. >>>> > >>>> > Deleting the whole data folder will clean all deployments. This can >>>> only >>>> > be >>>> > done when SMX is not running. On next start of smx all things in >>>> > hotdeploy folder will be redeployed. So be sure not to delete >>>> something >>>> > you can't recover. >>>> > >>>> > Regards >>>> > Lars >>>> > >>>> > Am Mittwoch 20 August 2008 16:08:58 schrieb stlecho: >>>> >> Hi, >>>> >> >>>> >> When using the "mvn jbi:projectDeploy" artifact, I'm receiving an >>>> error. >>>> >> >>>> >> On the server-side I get the following WARN: "InstallationService >>>> | >>>> >> .framework.InstallationService 420 | Failed to delete old >>>> installation >>>> >> directory: >>>> >> >>>> G:\progs\esb\servicemix\apache-servicemix-3.2.2\data\smx\components\serv >>>> >>ice mix-file\version_6". >>>> >> >>>> >> On the client-side (deployment) I get :"Unable to deploy project, >>>> Error >>>> >> accessing ServiceMix administration". >>>> >> >>>> >> How can this be solved ? >>>> >> >>>> >> Regards, Stefan Lecho. >>> >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/Failure-on-re-deploying-same-SA-tp19069912p19097137.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
