[seam-dev] Seam JMS module refactoring/restructuring

[Jozef Hartinger]

John,

I must have missed this e-mail before and I actually did some changes to 
the JMS testsuite yesterday in order for out CI builds to run smoothly 
again (I added JBoss AS 7 profile and isolated unit from integration 
tests). Feel free to rollback these changes if they conflict with what 
you've been working on.

On 09/21/2011 03:57 AM, John D. Ament wrote:
> Gents,
>
> I've been working diligently (whenever I have time) to get the seam 
> JMS module up and running on the new test suite format.  One thing 
> I've noticed is that because of the caveats of using JMS In SE vs. EE, 
> it didn't just work to run weld ee embedded and within a container 
> tests by themselves.  It also became clear that in general this 
> wouldn't work outside of a container because of differences in how to 
> start open mq vs. hornetq vs. activemq.  Even working in a remote JNDI 
> provider (similar to how weblogic JMS works) it wouldn't have worked 
> quite right.
>
> Soemthing I started a while ago (maybe 4-5 weeks) was to separate 
> various impls to different modules.  I want to go ahead and move 
> forward with this approach.  This would provide the main api and impl 
> (across all impls) as well as a domain specific impl (e.g. 
> seam-jms-ee-impl) that contains functionality for EE environments.  As 
> a result, when running the test suite, you are verifying the api, 
> impl, the domain specific impl and the test suite for that specific 
> combination.
>
> Does anyone have any concerns with this approach?
>
> John
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev