-
15. Re: Session bean injection
I guess it could be this:
{quote}
3.4.7.2 Stateless Session Beans
All business object references of the same interface type for the same stateless session bean have the same object identity, which is assigned by the container.
{quote}
-
16. Re: Session bean injection
There was a WELD message about unsatisfied deps so one would think that beans.xml is found.
-
17. Re: Session bean injection
That might be because it can't resolve a reference to the remote interface.
-
18. Re: Session bean injection
Ah. "Remote interfaces are not included in the set of bean types". Therefore there won't be one with @New, either.
-
19. Re: Session bean injection
In summary, we expect the following should work:
{code:java}
@Inject @New
Instance<GeneralSessionLocal> generalSessionInstance;
{code}
-
-
-
22. Re: Session bean injection
One option could be dropping in a fresh weld implementation module and hold your breath, hoping the SPI hasn't changed.
-
23. Re: Session bean injection
when I do it with out the Instance -
@Inject
GeneralSessionLocal bs;
I get:
WELD-001443 Pseudo scoped bean has circular dependencies. Dependency path [Session bean [class com.windriver.dsm.labmanagement.ejb.session.GeneralSessionBean with qualifiers [@Any @Default]; local interfaces are [GeneralSessionLocal], Session bean [class com.windriver.dsm.labmanagement.ejb.session.GeneralSessionBean with qualifiers [@Any @Default]; local interfaces are [GeneralSessionLocal]]
-
-
25. Re: Session bean injection
I have no Idea what canged, but now somehow this works (I am pretty sure I tried it before with out the new annotaion):
@Inject
Instance<GeneralSessionLocal> generalSessionInstance;
and generalSessionInstance.get() returns an instance with no problem .
-