Bug 948215
Summary: | Seam2.3 javax.naming.NameNotFoundException trying to call EJB Seam components from quartz asynchronous methods | ||
---|---|---|---|
Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Marek Schmidt <maschmid> |
Component: | Seam | Assignee: | Marek Novotny <mnovotny> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Marek Schmidt <maschmid> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.2.0 | CC: | kpiwko, ppenicka, snagarwa |
Target Milestone: | --- | ||
Target Release: | 2.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
Calling EJB Seam components from non-EJB threads (for example asynchronous Quartz threads) does not work due to a different implementation of the JNDI pattern specification in Java EE 6. As a consequence, the javax.naming.NameNotFoundException exception is generated while looking for EJB components from a non-EJB thread. The workaround for this issue is actually the correct method of accessing EJB components: accessing EJB components from non-EJB threads by global JNDI and not by application JNDI.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-22 13:20:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marek Schmidt
2013-04-04 10:33:29 UTC
This also affects Seam2.2 applications migrated to EAP6. Updated Doc Text. Doc text edited and inserted into the 2.2.0 release notes book. Docs stage URL: https://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Web_Framework_Kit/2.2/html-single/2.2.0_Release_Notes/index.html Build: JBoss_Web_Framework_Kit-2.2.0_Release_Notes-2.2-en-US-0-26 Verified content in RN. |