[jboss-dev-forums] [Design of JBoss Transaction Services] - bundling JTS into AS 5.0

So I'm mulling over how best to include JTS into AS 5.0. Right now it's a separate download and manual install, which sucks. We should ship the necessary .jar and config files in the AS and either have a server with it already installed (e.g. 'default', 'all', 'all-jts') or at least provide scripting for as much of the install as possible (e.g. 'ant -f install-jts-to-server-all.xml') There are a few complications: the .jar files and config files for JTA and JTS don't cohabit well. Having both on the classpath is asking for trouble, so we can't simply dump them both into 'all' and use the transaction-beans.xml to switch between them. Installing the JTS requires first uninstalling the JTA. Right now I'm leaning towards editing the JBossAS build process so it pulls the JTS .jars and config file from the maven repo and puts them in docs/examples/jts along with an ant script that will copy 'all' to 'all-jts', ripping out the JTA and putting in the JTS in the process. There may be some bits of that process that will be tricky to automate fully as it requires editing existing xml files, but it should be possible to automate most of it. This approach makes for a smaller AS distribution footprint than providing a full server subdir with the jts in, as the cost of being less convenient for customers who do need the JTS. Any further thoughts from the JBossAS side of the house before I start in on this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171225#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...