Regarding the readme: "When upgrading an existing installation be sure to update all the configuration files in server/<server name>/deploy/jboss-messaging.sar with the newer versions and replace jboss-messaging.jar in server/<server name>/lib and on the client classpath. You will also need to drop all tables and indexes in the database."
Sounds like overkill to me? What about productions systems with lots of messages in queue, how do you upgrade them. Seems to me that there is no need to drop all the tables. Looks like one new table was added, and three indices droped from 1.4.0 SP3 to 1.4.2 GA. It's no biggie to upgrade the DB by hand, keeping persisted messages in queue. Would it be possible to include som DDL scripts for the JBM database in the distribution? Would be nice not having to search for them in xx-persistence-service.xml by hand. cheers /Stig View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206225#4206225 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206225 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
