On Fri, 2006-09-15 at 06:09 -0500, Dimitris Andreadis wrote: I'm going to spend a couple of days on JBossMQ before 4.0.5 is released. Below is a summary. Most of it should be catered for by Weston's changes to the ServerSessionPool. Weston is working on this, he knows how to fix the final part, which is really a JCA issue. I doubt this will get done. I don't have time to rewrite these crappy tests for this release. Ideally, JBoss Messaging and JBossMQ should be sharing a testsuite using the JBossAdmin abstraction I wrote when I integerated the JORAM testsuite. I will do this. This isn't very important, but I will probably do it as part of the related fix that was only partially fixed in 4.0.5RC1 (JBAS-3628) I will do this. Weston is working on this. This won't get done, it is a feature request that keeps getting bumped. We should probably remove it from the schedule. This won't get done. The original contributor of this code looks to have orphaned it. This should be removed from the schedule of fixes since the real "fix" is JBAS-2841 I'll apply my suggested fix since the user's suggested patch is wrong. Weston is working on this. This won't get done. It is a none issue that just leads to a minor inefficency at session.close() The fix is fairly complicated in comparison, it involves wrapping/unwrapping the destination objects to keep track of their state. In fact, it is already fixed by the new resource adapter stuff I did in the jca prototype project. -- xxxxxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxx

This is all done execpt for JBAS-3183 On Fri, 2006-09-15 at 15:23 +0200, Adrian Brock wrote: -- xxxxxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxx

-----Original Message----- From: Ovidiu Feodorov Sent: Fri 9/15/2006 3:39 PM To: Adrian Brock Cc: Dimitris Andreadis; Weston Price; Ovidiu Feodorov; Tim Fox; JBoss.org development list; Richard Achmatowicz Subject: Re: JMS tasks from jboss-4.0.5 With reference to the related discussion thread: 1. Due to the TCK-related changes to the testsuite, Messaging is now being brought into /thirdparty during the JBAS build. I have therefore put on hold making changes to allow testsuite to indepdendently pull in libraries from the repository. 2. release-admin.xml creates a scoped deployment, and it appears that this is what we need (for the present) in order to execute Messaging within JBAS. Thus, in order to finish off the changes described in the related discussion thread, I just need to get release-admin into repository and use it to construct the Messaging configuration. I'll put that as top priority for Monday. 3. Once I have one JMS test executing against Messaging, the next step is to identify which of the existing JBossMQ tests (in src/main/org/jboss/test/jbossmq) are pure-JMS and which are JBossMQ-specific (i.e. which test implementation dependent features of JBossMQ). These pure-JMS tests will then also be used to test Messaging. Ovidiu was going to deal with creating any additional Messaging-specific test cases, if required. At the moment, the idea was to create a separate src/main/org/jboss/test/jbossmessaging directory which would hold all Messaging-related JMS tests, shared or not, in order not to interfere with the existing JBossMQ tests in the directory src/main/org/jboss/test/jbossmq. But then sharing the test cases isn't so clean - the shared tests would all be located in the jbossmq directory. A directory arrangement which would make sense would be to have pure JMS tests in a dirctory called jms, JBossMQ-specific JMS tests in a directory called jbossmq and Messaging-specific JMS tests in jbossmessaging. That would make sharing easy. But from my understanding that isn't the present state of affairs. I can't remember off hand the purpose of the (very few) tests in the 'existing' directory src/main/org/jboss/test/jms, but they will play a part as well. My initial approach would be to live with separate copies of the shared JMS tests (based in the JBossAdmin) abstraction, in both the jbossmq and messaging directories until things stabilized, and then adjust the contents of the directories shortly afterward to allow use of a single copy of each test, perhaps using trhe directory naming mentioned above. Comments? Suggestions?