Possible ways of distributing the conversational esb actions

[jeff.yuchang]

Hi All,

I am thinking that how to assembly the conversation based esb actions runtime and samples, so that users can easily download the zip file, instead of checking out source code and build from scratch.

Right now, the source code folder structure is:

- runtime/jbossesb: it contains the source code of conversational ESB actions. it will produce the jbossesb-cdl.jar
- assembly/jbossesb: it contains the hibernate.cfg.xml, deployment.xml, mbean for creating a cdl database configuration and so on. It will produce the jbossesb-cdl.esb, which will include the jbossesb-cdl.jar.

- samples/jbossesb: it contains some example of demonstrating that how to build applications based on conversational esb actions.

So, one approach would be:
In the jbossesb-cdl.zip, it has:
-jbossesb-cdl.zip
|----jbossesb-cdl.esb (exploded version or not?)
|----jbossesb-cdl.jar
|----samples
|----README.txt

Another approach would be zipped file like:
-jbossesb-cdl.zip
|----jbossesb-cdl.esb (exploded version)
|----samples
|----README.txt

In this way, users can get the jbossesb-cdl.jar in the jbossesb-cdl.esb/lib.

So, there are couples of questions from me:

1) exploded version of esb is better or not, personally, I'd prefer exploded, so it will be easily for users to take a look at the detail configuration, like jBPM.esb, jbrule.esb etc.

2) Do we need to have show the jbossesb-cdl.jar explicity in the zip file, samples are using the jbossesb-cdl.jar as reference library?

3) Currently, I am using Maven for building/deploying samples, do you think it might be better for us to use ANT for building example??

Any thoughts??

Thanks
Jeff

[jeff.yuchang]

Forgot to say, that it will also include the doc folder in the zip file. so it will be like:

--samples/
--doc/
--README.txt
...

Thanks
Jeff

[objectiser]

In terms of the jbossesb-cdl.jar, I think it should just be contained within an exploded jbossesb-cdl.esb folder, and referenced in that location when building the samples (similar to jbossesb trailblazer etc).

Once deployed I assume the sample .esb distributions would have a dependency on the jbossesb-cdl.esb?

Just one thing - do we need a better name for the .esb and .jar that reflects the three aspects: 1) overlord (being the project), 2) cdl or some sort of conversation related acronym, as the sub-project, and finally 3) the specific platform (e.g. jbossesb in this case)? For example, overlord-cdl-jbossesb.esb?

[jeff.yuchang]

"objectiser" wrote:
In terms of the jbossesb-cdl.jar, I think it should just be contained within an exploded jbossesb-cdl.esb folder, and referenced in that location when building the samples (similar to jbossesb trailblazer etc).

Once deployed I assume the sample .esb distributions would have a dependency on the jbossesb-cdl.esb?

Yes, all sample esb artifacts are dependent on jbossesb-cdl.esb.

"objectiser" wrote:

Just one thing - do we need a better name for the .esb and .jar that reflects the three aspects: 1) overlord (being the project), 2) cdl or some sort of conversation related acronym, as the sub-project, and finally 3) the specific platform (e.g. jbossesb in this case)? For example, overlord-cdl-jbossesb.esb?

hmm... overlord-cdl-jbossesb.esb sounds good to me.