if you are using ejb3, hibernate... the only way to get it working is running the installer....
Thanks for the answer. We do not actually need any of the features that are available only via the installer. Does this mean we should stick to the zip file?
Some background information on the question: The problem is that we have two projects that have started off with the two different ways of installation in their development workspaces. Unfortunately, the customization procedures developed for one installation method does not work on the other one without nontrivial changes.
To avoid this issue for future work, we would like to know what the recommended and future-proof installation method is.
There is now a GA version of the installer available that allows you to setup ha-jms etc including ejb3 and hibernate. Our product uses its own installer, so the way we work is that we place run the jboss installer once (using the installer by the way). Then roll those files into our installation so everyone gets the same files.
My recommendation for your team would be to have 1 person install jboss and set it up. Zip that whole freaking thing and tell everyone to use that zip file.
Kinda related question: is it possible to add one's services to the jems installer?