[ https://jira.jboss.org/jira/browse/JBPM-2290?page=com.atlassian.jira.plug... ] Martin Putz commented on JBPM-2290: ----------------------------------- I'm afraid I don't quite get the argument about being 'able to test these factories'. If the distribution (jBPM 3.2.5.SP5 on the support portal is the zip distribution, not the installer!) defaults to providing a configuration with the JMS/Entity factories, this is what the basic user will start with, unless he is adept in configuring jBPM and change to the DB based factories. A couple of points why I think the DB based factories are better used as default (in order of importance): 1. No failover support for EJB2 based timers in a cluster (see JBCLUSTER-153) 2. Additional configuration steps to change the DB for EJB timers and JMS needed, so that these components do not use the unsupported hsqldb. 3. Better QA coverage eg. the JMS/Entity factories are not QA'd as part of SOA-P (see SOA-1310) 4. That's what it used to be in earlier jBPM version. What do you mean by the 'SOA installer'? Right now we've got the SOA-P on one hand, which has jBPM already bundled with a given configuration. On the other hand, customers who are not using the SOA-P need to install jBPM on EAP, and for this the best starting point I see is the 'deploy/server' directory in the zip distribution, which is what I have been referring to throughout this ticket. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2290?page=com.atlassian.jira.plug... ] Alejandro Guizar commented on JBPM-2290: ---------------------------------------- I don't know how the zip distro is built. That is outside the jBPM codebase. Like I said, my considerations applied to the community/standalone package. No argument against the DB factories being the default in SOA-P, in particular since the platform does not support EJBs in its default configuration. I will let someone who knows about the zip distro handle this. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2290?page=com.atlassian.jira.plug... ] Alejandro Guizar updated JBPM-2290: ----------------------------------- Fix Version/s: jBPM 3.2.x (was: jBPM 3.2.8) -- 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