Well you need to integrate them into Seam. Seam uses EJB3 interceptors to
intercept all requests to MDB (and SLSB, SFSB) and wrap them in Seam's contexts
etc. If you are just calling the object directly (which I think you are) you'll
need to set up the contexts yourself. You can look at the
Hi Pete,
No, it is not declared as a MDB. It is clear to me, that this is not the usual
way to go. But what about thirdparty libs in general, well yes, that start off
some threads and do callbacks on my code? I know it is not considered good
practice but then again...
@Stateful
|
It may be generally a good practice to do the business logic in a session bean
instead of using JPA directly in your MDB.
However, this is currently a problem when your app is deployed with messages
already in the queue: http://jira.jboss.org/jira/browse/JBSEAM-2286
View the original post :
And more importantly, is it declared as an MDB?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4109782#4109782
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109782
___
jboss-user
Post the code for your message listener impl.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4109780#4109780
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109780
___
jboss-user
