The current state of JMS is reflected on the module page fairly well. I'm currently in the process of doing general housekeeping: updating versions, logging, making sure tests pass in JBoss AS 6 Final thanks to help from John Ament. I've run into a few issues trying to test with HornetQ destinations which seems more like a HornetQ bug than a configuration issue at this point but all tests that were working in JBoss AS 6 M4 are once again working on the final release. All of this work has yet to be merged into the official seam-jms branch.<div>
<br></div><div>Here's a quick rundown of what is left to be implemented:</div><div>- Ingress routing: JMS -> CDI Events</div><div>- Implement routing of events as described in JSR-299's spec draft dated 20090520: <span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">where we generate proxies for relevant interfaces with:</span></div>
<div><div style="border-collapse: collapse; font-family: arial, sans-serif; ">@Observes</div><div style="border-collapse: collapse; font-family: arial, sans-serif; ">interface JMSMapping </div><div style="border-collapse: collapse; font-family: arial, sans-serif; ">
{</div><div style="border-collapse: collapse; font-family: arial, sans-serif; "> void myMapping(@Observes @SomeQualifier SomeType type, @MyTopic Topic topic);</div><div style="border-collapse: collapse; font-family: arial, sans-serif; ">
}</div><div style="border-collapse: collapse; font-family: arial, sans-serif; "><span class="Apple-style-span" style="border-collapse: separate; font-family: arial; ">- Flesh out EventBridge so that routes can be managed dynamically at run time (at least the API nailed down for Beta. Would be great to have it complete).</span></div>
<div style="border-collapse: collapse; font-family: arial, sans-serif; "><span class="Apple-style-span" style="border-collapse: separate; font-family: arial; "><br></span></div><div style="border-collapse: collapse; font-family: arial, sans-serif; ">
Help will be required as I haven't had any time in the past months to work on this and have only very limited time currently.</div><div style="border-collapse: collapse; font-family: arial, sans-serif; "><br></div><div style="border-collapse: collapse; font-family: arial, sans-serif; ">
Best Regards,</div><div style="border-collapse: collapse; font-family: arial, sans-serif; ">Jordan Ganoff</div><div><br><br><div class="gmail_quote">On Tue, Jan 4, 2011 at 9:19 AM, Jason Porter <span dir="ltr"><<a href="http://lightguard.jp">lightguard.jp</a>@<a href="http://gmail.com">gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div></div><div class="h5">On Tue, Jan 4, 2011 at 04:07, Shane Bryzak <<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>> wrote:<br>
> I hope everyone had a restful end of year break. Now that we're into<br>
> the new year I'd like to make it a top priority to prepare a beta<br>
> release for Seam 3. To do this, we're first going to need at least a<br>
> beta release for every single Seam module - the good news though for<br>
> module leads, is if your module is already at Beta1 or higher, you don't<br>
> need to do anything ;-)<br>
><br>
> What I'd like to do is start off with a simple status check from each of<br>
> the module leads for each of the modules that are still in alpha. To<br>
> the best of my knowledge this includes the following modules:<br>
><br>
> Seam Catch (Alpha3)<br>
> Seam International (Alpha 3)<br>
> Seam JMS (Alpha 1)<br>
> Seam REST (Alpha 2)<br>
> Seam Security (Alpha2)<br>
> Seam Servlet (Alpha 2)<br>
><br>
> If your module is in the above list, can you please describe what is<br>
> still required to be done to get your module to a beta release, and<br>
> roughly how long you think it will take. I'll start with the security<br>
> module:<br>
><br>
> Currently the security module is in good shape, however I'm expecting to<br>
> make some further changes to the authenticator API to allow better<br>
> integration between the external authentication module and the core<br>
> security beans, such as Identity. I estimate that this work will take<br>
> approximately 2 weeks (so should be roughly completed by the 18th of<br>
> Jan) after which I'll release beta 1.<br>
><br>
> Once we have an update from all module leads then we can start setting<br>
> target release dates. Ideally I would like to get the beta released<br>
> before the end of this month, ideally around the 21st.<br>
><br>
> Thanks,<br>
> Shane<br>
><br>
><br>
><br>
><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>
<br>
<br>
</div></div>For Catch I have some API changes that are waiting a release, and one<br>
feature that will a small bit of new API. After that it's good for a<br>
beta. I had hoped to get that done in December, but holidays and<br>
other family related things stopped that from happening. I could<br>
easily do an Alpha 4 with what I have and push the new feature off to<br>
the beta. Dan also did another release (or will be soon) of Solder<br>
which will have some things that I'll need (currently it's in Catch,<br>
but will be pulled up into Solder).<br>
<br>
--<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>
<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>
<div><div></div><div class="h5"><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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Jordan Ganoff<br>
</div></div>