This is not something that can be done so far.

I have done this with Nukes. What I did was the following:

1) Download the Nukes source from CVS.
2) Do a find and replace on the word nukes to nukes1 for the entire source tree and make the find and replace case sensitive. Do the same thing to rename Nukes to Nukes1. Rename all the directories with nukes to nukes1. For your second instance you would rename nukes to nukes2. Compile the source.
3) Create databases for each Nukes and call them nukes1, nukes2, etc.
4) Deploy the files to the server deploy directory. The nukes directory will be nukes1, nukes2, etc.

It has been awhile since I did this, there may have been a few other gotchas I had to fix to get it working. This was such an ugly way to get two version of Nukes running in one server that in the end I just created seperate jboss servers for each Nukes I wanted to run. It does take a lot more memory to have a seperate jboss server for each Nukes.

Danny

Hi,

i try the method you described to deploy more than one nukes instance.
But i have some problems with Proxy creations...
Do you remember more precisely the other things to do to make it work ?

Thanks

The version of Nukes I did this with was the 1.0 version. There may be new problems in the newer release. I don't recall having any proxy problems. You don't want to have any JNDI naming conflicts and nukes is the one word you can do a search and replace on to resolve the naming conflicts. This also gives distinct database names, class names, etc. for each version of Nukes.
The better way to do this is create a second instance of JBoss on the server with different port numbers. This is simpler and will work without any problems.