You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Nodet Guillaume <gn...@gmail.com> on 2007/08/17 10:21:51 UTC
Changes to distribution
Hi everybody !
I'm wondering if we should change a few things to the distribution so
that it is easier to use:
* keep a single hot deploy folder instead of install / deploy
* put components inside the hot deploy folder so that users do not
have to install them the first time
* do not use the current folder as the servicemix home (unless a
specific parameter is used): this would avoid the problem of starting
smx in the bin directory, but we need to find a way to specify an
alternate location for the examples to work
Wdyt ?
Cheers,
Guillaume Nodet
Re: Changes to distribution
Posted by Bruce Snyder <br...@gmail.com>.
On 8/17/07, Nodet Guillaume <gn...@gmail.com> wrote:
> Hi everybody !
>
> I'm wondering if we should change a few things to the distribution so
> that it is easier to use:
> * keep a single hot deploy folder instead of install / deploy
> * put components inside the hot deploy folder so that users do not
> have to install them the first time
> * do not use the current folder as the servicemix home (unless a
> specific parameter is used): this would avoid the problem of starting
> smx in the bin directory, but we need to find a way to specify an
> alternate location for the examples to work
+1 on all. I like making the default configuration more sensible in
this manner.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Castor - http://castor.org/
Re: Changes to distribution
Posted by Alex Boisvert <bo...@intalio.com>.
Perfect! I think it's a nice simplification.
alex
On 8/17/07, Guillaume Nodet <gn...@gmail.com> wrote:
>
> I'm just thinking about a configuration change.
> We just need to make a few changes in the configuration:
>
> <smx:container ...
> monitorDeploymentDirectory="false"
> monitorInstallationDirectory="true"
> installationDirPath="./hotdeploy"
>
> should be enough to use a single directory named "hotdeploy" instead
> of the "install" and "deploy" folders. Both are handled exactly the
> same way btw ...
>
>
Re: Changes to distribution
Posted by Guillaume Nodet <gn...@gmail.com>.
I'm just thinking about a configuration change.
We just need to make a few changes in the configuration:
<smx:container ...
monitorDeploymentDirectory="false"
monitorInstallationDirectory="true"
installationDirPath="./hotdeploy"
should be enough to use a single directory named "hotdeploy" instead
of the "install" and "deploy" folders. Both are handled exactly the
same way btw ...
On 8/17/07, Alex Boisvert <bo...@intalio.com> wrote:
> Great ideas! I'm favorable on all 3.
>
> Does unifying install and deploy directories mean you can't have them
> separate? Or is that just a configuration thing? When you have a lot of
> components, it's nice to be able to easily tell the SEs/BCs from the service
> assemblies. And I guess there are implications for system administration
> in cases where you want different permissions for hot-deploying SEs/BCs and
> assemblies.
>
> alex
>
>
> On 8/17/07, Nodet Guillaume <gn...@gmail.com> wrote:
> >
> > Hi everybody !
> >
> > I'm wondering if we should change a few things to the distribution so
> > that it is easier to use:
> > * keep a single hot deploy folder instead of install / deploy
> > * put components inside the hot deploy folder so that users do not
> > have to install them the first time
> > * do not use the current folder as the servicemix home (unless a
> > specific parameter is used): this would avoid the problem of starting
> > smx in the bin directory, but we need to find a way to specify an
> > alternate location for the examples to work
> >
> > Wdyt ?
> >
> > Cheers,
> > Guillaume Nodet
> >
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Changes to distribution
Posted by Alex Boisvert <bo...@intalio.com>.
Great ideas! I'm favorable on all 3.
Does unifying install and deploy directories mean you can't have them
separate? Or is that just a configuration thing? When you have a lot of
components, it's nice to be able to easily tell the SEs/BCs from the service
assemblies. And I guess there are implications for system administration
in cases where you want different permissions for hot-deploying SEs/BCs and
assemblies.
alex
On 8/17/07, Nodet Guillaume <gn...@gmail.com> wrote:
>
> Hi everybody !
>
> I'm wondering if we should change a few things to the distribution so
> that it is easier to use:
> * keep a single hot deploy folder instead of install / deploy
> * put components inside the hot deploy folder so that users do not
> have to install them the first time
> * do not use the current folder as the servicemix home (unless a
> specific parameter is used): this would avoid the problem of starting
> smx in the bin directory, but we need to find a way to specify an
> alternate location for the examples to work
>
> Wdyt ?
>
> Cheers,
> Guillaume Nodet
>