You should not have to change any code to deploy twice, editing the deployment descriptors is enough, also datasources can be shared between applications.
There's no way around changing JNDI names though, if you want to only keep one copy in development you need to write yourself a script that changes the JNDI context as part of the build for each application.
I am deploying two different applications that have the same EJB name and Servlet name. The only different is that I they connect to two different DB. I have two different db-sevice.xml for each application. This work when I run then individually. But when I try to deploy both I got a error saying that the EJB is not unique eventhough I have deployed separetly in two different folders in the server/default/deploy.
Any idea or tips how I can accompish this?
By the way I just got a copy of the JMX Manahing J2EE with java Mang. Extension and JBOSS adminstration and development books and I don't see any information in how settup partitions? Any Idea where I can find information.
Thanks in advance.
Just like above:
Change the JNDI names before deploying. If you are using comp/env namespace in your code, you will never have to change something when deploying under different JNDi names. Use the jboss.xml and the resource tags for mapping the global (or java:) namespace to the comp/env namespace.
One difference: use two datasources and map the one for the first app, the second to the second app... that's all.
... or just use two servers... ;-) (not really...)