Open glassfishrobot opened 9 years ago
Reported by gray
@AdamLindenthal said: Hi Gray,
thanks for creating the issue. I am moving it to backlog, so that we can plan it for one of the future sprints.
Regards, Adam
sparksis said: Hi Adam,
Is there an ETA on when this could be revisited? As is glassfish 4.1 does not support JAX-RS with @Stateless EJBs in web archives.
Thanks,
lberteau said: Hi everyone,
If it may help, I have noticed that I have this issue within 32 bits environnements. The same code works fine within a 64 bits JDK.
Don't have a clue about the reasons, but that's what I observed.
Regards, Laurent
marvinemilbrach said: posssible workaround: replace @Stateless with: @javax.enterprise.context.RequestScoped @javax.enterprise.context.ApplicationScoped @javax.enterprise.context.ConversationScoped // NOT tested @javax.enterprise.context.SessionScoped // NOT tested
@AdamLindenthal said: https://github.com/jersey/jersey/pull/162
This issue was imported from java.net JIRA JERSEY-2690
When declare EJB to be JAX-RS endpoint inside war module that included in EAR like this:
Name of the war module is "op-client" I got following exception in the logs:
Note that lookup is complains about "someothermodule" not "op-client". Earlier in the logs though there is following message:
Which means that bean was successfully discovered and registered and should be available for lookup. Evaluating expression with proper name for lookup at breakpoint in EjbComponentProvider confirms that. Digging deeper into the problem I've found that patch that was made to fix this issue (325a2f214e093859d41d81f9f06652c169a03aa4) introduced following code in registerEjbInterceptor method of EjbComponentProvider:
Note jarName.endsWith(".jar") part. This check for file extension basically prevents all beans that live inside "*.war" being discovered when doing cycle in lookupSimpleForm method:
because now we never see war file in provider.libNames collection. This breaks my and not only my (https://java.net/jira/browse/GLASSFISH-21114) application and should be fixed.
Environment
Glassfish 4.1 (jersey module version 2.10.4)
Affected Versions
[2.10, 2.13]