Static vs Hot Deployment?

[roger]

Hi all,

We're experiencing problems deploying ServiceMix BC's and SE's. As a first task, we're building an ESB with two servicemix-file BC's and one servicemix-eip SE. The first ones were easily deployed using the servicemix.xml file. The latter, the EIP one, though, seems like it requires to be hot-deployed (a.k.a. JBI deployed). As we're trying to configure the EIP SE in servicemix.xml (by creating an XBean whose NS refers to the servicemix-eip class files, the ones being hot-deployed), we receive the following exception:

"Unable to locate Spring NamespaceHandler for XML schema namespace"

I guess this is due to the static (MBean-based?) configuration is loaded prior to the JBI/hot-deployment beans. What I urgently need help with is answers to the following questions:

1. Is there any way I can change the order in which the two deployment (static and JBI) are made? Is it even a good idea?

- and / or -

2. (Perhaps better?) Perform all deployment using the JBI/hot-deployment model. Questions that rise then are:

2.1. Where do I put the configuration for these deployments? (For the servicemix-file instances there is folder settings, for the EIP instance there are routing rules.)

2.2. What tools are available for me to create these JBI deployment packages? I've read about the Maven tooling, though I cannot find anywhere to put my by-instance configuration in these packages.

I'm very thankful for any advice I can get!

Regards,

Roger Joelsson

[bsnyder]

1. Is there any way I can change the order in which the two deployment (static and JBI) are made? Is it even a good idea?

We don't recommend or support static deployment because it's not JBI compliant, it's no longer being actively developed and using it in conjunction with JBI compliant SAs can be problematic.

2. (Perhaps better?) Perform all deployment using the JBI/hot-deployment model. Questions that rise then are:

Yes, we recommend JBI deployment.

2.1. Where do I put the configuration for these deployments? (For the servicemix-file instances there is folder settings, for the EIP instance there are routing rules.)

JBI deployment requires the creation of service units (SUs) and service assemblies (SAs), just like you've done with the servicemix-eip component.

2.2. What tools are available for me to create these JBI deployment packages? I've read about the Maven tooling, though I cannot find anywhere to put my by-instance configuration in these packages.

There are Maven archetypes available to create Maven projects for each SU and SA from the command line as well as the FUSE Eclipse Tooling that exposes these same archetypes via the Eclipse New Project Wizards.

Bruce

[roger]

The Maven archtetypes really helped me out, they actually generate the SU's and the SA's, ready to deploy.

Two notes:

1) At first, the deployed components didn't seem to work. This was due to missing servicemix-*-installer.zip files in the hotdeploy folder. After putting them there, everything worked fine.

2) The JBI plugins for Eclipse do not appear in the File/New windows. Perhaps this is due to some mistake from my side?

Regards,

Roger

[bsnyder]

2) The JBI plugins for Eclipse do not appear in the File/New windows. Perhaps this is due to some mistake from my side?

Take a look at the installation instructions for the FUSE Eclipse Tools. These instructions walk you through the installation step-by-step.

Bruce