<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: JMS tasks from jboss-4.0.5</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>-----Original Message-----<BR>
From: Ovidiu Feodorov<BR>
Sent: Fri 9/15/2006 3:39 PM<BR>
To: Adrian Brock<BR>
Cc: Dimitris Andreadis; Weston Price; Ovidiu Feodorov; Tim Fox; JBoss.org development list; Richard Achmatowicz<BR>
Subject: Re: JMS tasks from jboss-4.0.5<BR>
<BR>
>Adrian Brock wrote:<BR>
>><BR>
>> Ideally, JBoss Messaging and JBossMQ should be sharing a testsuite<BR>
>> using the JBossAdmin abstraction I wrote when I integerated the<BR>
>> JORAM testsuite.<BR>
>><BR>
>> <BR>
> That's still the plan and it was Rajdeep's perpetual task, until he<BR>
> disappeared from the radar:<BR>
> <A HREF="http://jira.jboss.org/jira/browse/JBMESSAGING-185">http://jira.jboss.org/jira/browse/JBMESSAGING-185</A><BR>
<BR>
> Richard Achmatowicz is currently working on Messaging test integration,<BR>
> this task would naturally fit there.<BR>
<BR>
> Related discussion thread:<BR>
> <A HREF="http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968806#3968806">http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968806#3968806</A><BR>
<BR>
> Richard, what is the status?<BR>
<BR>
With reference to the related discussion thread:<BR>
1. Due to the TCK-related changes to the testsuite, Messaging is now being brought into /thirdparty<BR>
during the JBAS build. I have therefore put on hold making changes to allow testsuite to<BR>
indepdendently pull in libraries from the repository.<BR>
<BR>
2. release-admin.xml creates a scoped deployment, and it appears that this is what we need (for the<BR>
present) in order to execute Messaging within JBAS. Thus, in order to finish off the changes described<BR>
in the related discussion thread, I just need to get release-admin into repository and use it to construct<BR>
the Messaging configuration. I'll put that as top priority for Monday.<BR>
<BR>
3. Once I have one JMS test executing against Messaging, the next step is to identify which of the<BR>
existing JBossMQ tests (in src/main/org/jboss/test/jbossmq) are pure-JMS and which are JBossMQ-specific<BR>
(i.e. which test implementation dependent features of JBossMQ). These pure-JMS tests will then also be<BR>
used to test Messaging. Ovidiu was going to deal with creating any additional Messaging-specific test cases,<BR>
if required.<BR>
<BR>
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<BR>
tests would all be located in the jbossmq directory.<BR>
<BR>
A directory arrangement which would make sense would be to have pure JMS tests in a dirctory called jms,<BR>
JBossMQ-specific JMS tests in a directory called jbossmq and Messaging-specific JMS tests in jbossmessaging.<BR>
That would make sharing easy. But from my understanding that isn't the present state of affairs.<BR>
<BR>
I can't remember off hand the purpose of the (very few) tests in the 'existing' directory<BR>
src/main/org/jboss/test/jms, but they will play a part as well.<BR>
<BR>
My initial approach would be to live with separate copies of the shared JMS tests (based in the JBossAdmin)<BR>
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.<BR>
<BR>
Comments? Suggestions?<BR>
<BR>
> Cheers,<BR>
> Ovidiu<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>