[jboss-dev-forums] [Design of JBoss Transaction Services] - Re: jta/jts jar/config file change

[jhalliday]

I'm inclined to make two further changes in respect of the .jar files and config files we ship. To facilitate clean embedding, I would like to:

- bundle the default config file into the .jar and change the existing search algorithm to look for it there as a last resort before giving up. This will allow the system to run without needing the etc dir (or other dir containing the config file) on the classpath, whilst being unobtrusive for existing installations.

- bundle the contents of ext/jbossts-common.jar into the jta/jts jar files directly. The splitting out of the common code made sense when it was consumed by other apps, but with JBossTS as the only user we may as well streamline things.

With those changes it should become possible to use the system just by including a single .jar on the classpath, along with any 3rd party .jars from ext depending on the functionality required.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232708#4232708

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232708