[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1619) Wrong JNDI lookup to java:comp/env space in non-EJB enterprise components
[
https://jira.jboss.org/jira/browse/JBPM-1619?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-1619:
----------------------------------------
I reviewed the patch and applied the fixes for JBPM-960.
Conversely, I don't think that reverting to global JNDI names after switching to local
environment references in 3.2.3 is a good idea. See the arguments in JBPM-960 and
JBPM-1046. Please keep me informed on any issue you encounter while deploying the
application to the EAP.
Wrong JNDI lookup to java:comp/env space in non-EJB enterprise
components
-------------------------------------------------------------------------
Key: JBPM-1619
URL: https://jira.jboss.org/jira/browse/JBPM-1619
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jPDL 3.2.3
Reporter: Martin Putz
Assignee: Alejandro Guizar
Attachments: JBPM-1619.patch
The following components of the enterprise archive attempt to make a lookup from their
local JNDI environment at java:comp/env:
- org.jbpm.msg.jms.JmsMessageServiceFactoryImpl
- org.jbpm.scheduler.ejbtimer.EjbSchedulerServiceFactory
- org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory
As these components are no EJB's, they have no local JNDI environment. The lookup
should use the In-VM space by default (eg. java:/JmsXA), and it should be possible to
override the lookup locations through jbpm.cfg.xml (see JBPM-960).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira