[seam-dev] Seam JMS and AS7

[John D. Ament]

Well, if you're looking for specific problems I am seeing, the big show
stopper I have is HORNETQ-741 & AS7-1271, where object messages are
violating classloaders.  I created the HORNETQ one after speaking to stuart
a little about it and noted that there was some type of API to be used to
fix it.  I haven't verified it yet, but I believe the maven plugin for
jboss:hard-deploy will place files in the wrong location.  I haven't created
an issue for it yet, but since datasources and JMS queues are place in to
profileName.xml you can no longer deploy these artifacts with your
application, which is a huge paradigm shift (JBoss would now be the only
full app server to not allow this); all deployment instructions now have to
be rewritten.

I also seem to be getting told by a lot of people that I just need to switch
to the "everything" release to enable JMS.  This is not the case.  JMS by
default is disabled in the "everything" download.  Requires some manual
changes to standalone.xml to turn it on.  I'm not sure about others, but
shouldn't JMS (and other base services) be on by default in the full EE
container.  Granted, it's not certified (and seeing my first note it seems
like it can't be) but in preparation for being certified, do a little prep
work...

- John

On Thu, Jul 14, 2011 at 5:44 AM, Pete Muir <pmuir at redhat.com> wrote:

> There will be a bug fix release for AS 7.0 in the not-too-distant-future.
> Ping Shane or me with any issues that you need addressed and we can get them
> bumped up the priority list.
>
> On 14 Jul 2011, at 00:41, John D. Ament wrote:
>
> > Hey all
> >
> > So I was testing Seam JMS on AS7 last night.  Now today I saw that the
> default example container is going to be AS7..  I have an issue with that.
>  Specifically, JMS doesn't work correctly on AS7 in general. The web profile
> deployment does not include hornetq.  The preview release has hornetq, but
> there are a few issues with it.  Specifically, the classloader architecture
> does not work correctly with ObjectMessages.  This is pretty crucial for the
> behavior of Seam JMS (specifically, the CDI events as JMS Messages feature).
>  I already have an issue open, but no update yet.
> >
> > John
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110718/b94d1a43/attachment.html