Here's my first stab at designing such a thing: 1. Create a JBoss server on the database side. Create a queue and MDB. Have the JMS messages in the queue go into your database, not HSQLDB.
Currently, you need an JDBC XA datasource (e.g. Oracle, DB/2) to do 2-phase commit. Other DBs would work, but you may not have 100% transaction integrity. 2. You can deploy Tomcat or JBoss on the webserver side. Either way, it needs to be same version. Connect to the queue on the back-end. Use a temporary queue to get your ack. message back. 3. Fire away. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3850812#3850812 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3850812 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
