[jbpm-issues] [JBoss JIRA] Resolved: (JBPM-960) JmsMessageServiceFactoryImpl does not ookup the connectionFactory and destinationName

[Alejandro Guizar (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBPM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alejandro Guizar resolved JBPM-960.
-----------------------------------

    Fix Version/s: JBossBPM-3.3.0
       Resolution: Done


Taken the corrections that correspond to JBPM-960 from the patch attached to jBPM-1619. Thanks, Martin.

> JmsMessageServiceFactoryImpl does not ookup the connectionFactory and destinationName
> -------------------------------------------------------------------------------------
>
>                 Key: JBPM-960
>                 URL: https://jira.jboss.org/jira/browse/JBPM-960
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jPDL 3.2.0
>            Reporter: Jeff DeLong
>            Assignee: Alejandro Guizar
>            Priority: Minor
>             Fix For: JBossBPM-3.3.0
>
>
> This is related to Case Number 00015224.
> JmsMessageServiceFactoryImpl does not appear to lookup the connectionFactory and destinationName from jbpm.cfg.xml anymore, but just uses these values:
>   String connectionFactoryJndiName = "java:/JmsXA";
>   String destinationJndiName = "queue/JbpmJobQueue";
> These mayl not be valid outside of JBoss AS. 
> This could be an issue for deployment on WLS or WAS.

-- 
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