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 <[EMAIL PROTECTED]> 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
>

Reply via email to