Created a JIRA issue: http://jira.jboss.com/jira/browse/JBSEAM-2286
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108241#4108241
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108241
___
We are seeing this aswell. This particular problem also has one big
implication: Since seam uses its own entity manager, and this affects caching
etc, we have decided to use the seam managed entity manager in all DAO:s.
Therefore, it is critical that seam is initialized before any component of t
Is there a problem with the way I use it or should I create a JIRA issue?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106553#4106553
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106553
_
Thanks for the quick response! Here are the sources (I had to 'censor' it for
obvious reasons):
MDB:
@MessageDriven(name = "Processor", activationConfig = {
| @ActivationConfigProperty(propertyName = "destinationType",
propertyValue = "javax.jms.Queue"),
| @Activation
Post your MDB and SLSB
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105961#4105961
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105961
___
jboss-user mailing list
jboss-us
