[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2290) Default config should use the db based implementations for messaging and scheduler service
[
https://jira.jboss.org/jira/browse/JBPM-2290?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-2290:
----------------------------------------
Martin, the configuration file unpacked by the installer to the JBoss deploy directory is
configured with the JMS/Entity factories in order to be able to test these factories. Plus
they are arguably a better choice for EJB containers.
These above considerations apply to the standalone version. The SOA installer can be built
with a different configuration by introducing a Maven profile. Would this alternative
accommodate your intent?
Default config should use the db based implementations for messaging
and scheduler service
------------------------------------------------------------------------------------------
Key: JBPM-2290
URL: https://jira.jboss.org/jira/browse/JBPM-2290
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Console
Affects Versions: jBPM 3.2.5.SP5
Reporter: Martin Putz
Fix For: SOA 4.3 CP02
The default configuration in the jbpm-jpdl-3.2.5SP5 package defines the usage of the
JmsMessageServiceFactory for the 'message' service and
EntitySchedulerServiceFactory for the 'scheduler' service in
/deploy/server/default/deploy/jbpm/jbpm-service.sar/jbpm.cfg.xml.
The default configuration should use the db based implementations for these services
instead, as it used to be in previous versions.
--
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