[jbpm-issues] [JBoss JIRA] Resolved: (JBPM-1726) JMS destinations service
[
https://jira.jboss.org/jira/browse/JBPM-1726?page=com.atlassian.jira.plug...
]
Alejandro Guizar resolved JBPM-1726.
------------------------------------
Resolution: Done
The required destinations are described in jbpm-destinations-service.xml. I specified the
JBossMQ queue class because it is the only option in JBoss 4.2 and it is supported for
backwards compatibility in JBoss 5.0.
Additionally, I added a JMS destinations pack to the installer definition.
JMS destinations service
------------------------
Key: JBPM-1726
URL: https://jira.jboss.org/jira/browse/JBPM-1726
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Engine, Installer
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.3.0 CR1
JBoss 5.0 does not create missing* JMS destinations automatically as JBoss 4.2 does. In
any case JBoss 4.2 issues a warning which may be uncomfortable for users. Hence a default
jBPM destinations descriptor must be provided and offered as an option in the installer.
(*) that is, referenced in jboss.xml or jboss-web.xml but not bound to JNDI
--
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