[seam-dev] Seam JMS Alpha 2 Incoming...

[Jordan Ganoff]

Hi Martin,

1) Let's start with something small that shows off what's implemented to
date. A small web app that uses Seam JMS to define a route between a CDI
event and a JMS destination. Other features exist but they mostly augment
the existing CDI functionality to allow the injection of JMS-related
resources (Connection, Session, Destination Producers, and Consumers) "out
of the box". It might be difficult to create a practical small example but
if we use Seam JMS to bridge event -> JMS -> event in place of doing a
direct call that could at least show its potential. One thing to note:
Ingress routing (firing events when we receive messages from JMS) is not
complete so you'll need to implement your own functionality to fire events
when JMS messages are received. You'll probably want to declare an MDB or
create your own MessageListener and simply fire the event. Once the ingress
routing is complete you can remove all that code and just define a
bidirectional route.

Have a look at the test cases for examples. Right now that's what I've been
relying on to show off the features.

2) The sooner the better; however, we have some work to do around the
ingress routing as stated above. We're shooting to have ingress routing
complete by the end of this coming week. Whenever you can finish the example
should be good - it's way better than what we have now (nothing)!

Thanks,
Jordan

On Fri, Feb 4, 2011 at 6:30 AM, Martin Gencur <mgencur at redhat.com> wrote:

> Hi Jordan,
> I would like to create an example for the JMS module. There are a few
> things I want to know:
>
> 1) do you have any special requirements? (which kind of application,
> what GUI, which features to incorporate, how big should the app be)
> 2) when is it supposed to be finished?
>
>
> Thanks
>
>
> Martin
>
>
>
> On Fri, 2011-02-04 at 12:36 +1000, Shane Bryzak wrote:
> > Great to hear, thanks Jordan.  Do you think we could skip the alpha 2
> > release and go straight to beta?  If the module is mostly feature
> > complete, that would be preferable, and that way we can include it in
> > the Seam 3 beta 2 release in a week from now.
> >
> > Shane
> >
> > On 04/02/11 11:33, Jordan Ganoff wrote:
> > > Shane, Dan, et al,
> > >
> > >
> > > The list of issues slated for Seam JMS Alpha 2 [1] are nearly
> > > completion. I'd like to be able to release Alpha 2 early next week
> > > and, provided the API is complete at that point, release a beta
> > > shortly after. I'll need help pushing out the release so I don't end
> > > up spending hours on it so here's your fair warning! ;)
> > >
> > >
> > > Again, anyone interested in helping out is more than welcome. We
> > > could use some help in nearly all areas but specifically creating an
> > > example or two. I plan on updating the doc before any release is
> > > made.
> > >
> > >
> > > Best Regards,
> > > Jordan
> > >
> > >
> > > [1]: https://issues.jboss.org/browse/SEAMJMS/fixforversion/12315281
> > >
> > > --
> > > Jordan Ganoff
> > >
> >
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/seam-dev
>
> --
> Martin Gencur
> Seam QA Associate
>
>


-- 
Jordan Ganoff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110206/7f9f81d2/attachment.html