The only concern I have with this is the multiple jar and getting it setup correctly from a user&#39;s point of view. If this is clearly and neatly laid out in the docs, then it shouldn&#39;t be a problem. Sorry for the tardiness of this email.<br>

<br><div class="gmail_quote">On Tue, Sep 20, 2011 at 19:57, John D. Ament <span dir="ltr">&lt;<a href="mailto:john.d.ament@gmail.com">john.d.ament@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

Gents,<br><br>I&#39;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&#39;ve noticed is that because of the caveats of using JMS In SE vs. EE, it didn&#39;t just work to run weld ee embedded and within a container tests by themselves.  It also became clear that in general this wouldn&#39;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&#39;t have worked quite right.<br>


<br>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.<br>


<br>Does anyone have any concerns with this approach?<br><font color="#888888"><br>John<br>
</font><br>_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Jason Porter<br><a href="http://lightguard-jp.blogspot.com" target="_blank">http://lightguard-jp.blogspot.com</a><br><a href="http://twitter.com/lightguardjp" target="_blank">http://twitter.com/lightguardjp</a><br>

<br>Software Engineer<br>Open Source Advocate<br>Author of Seam Catch - Next Generation Java Exception Handling<br><br>PGP key id: 926CCFF5<br>PGP key available at: <a href="http://keyserver.net" target="_blank">keyserver.net</a>, <a href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>