What kind of EntityManager is it? @PersistenceContext, or @In?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949204#3949204
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949204
__
It's seam managed, @In(create = true) and it works like a charm as long as the
method being called isn't part of the super-class/interface.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949205#3949205
Reply to the post :
http://www.jboss.com/index.html?modu
It does seem to have fixed the problem. I'm surprised no one has run across
that before.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949228#3949228
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949228
__
I can hazard a guess. Seam injects at the Seam component level. Your abstract
class isn't a Seam component because you can't have abstract Seam components.
Your Seam component can extend an abstract class, and the Seam annotations on
this class are properly recognized. However, once you make
OK, well let me know if it is fixed by the latest EJB3 release.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949208#3949208
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949208
_
I appreciate your feedback but not only have I tried it that way, I haven't
tried it any other way. I'm actually injecting the component into a field of
the local interface type, so just calling the method proves that it's available
as part of the SFSB. I've also checked the logs to make sure
