[ https://jira.jboss.org/jira/browse/JBPM-1819?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-1819: ------------------------------ Description: std configs should be the default. bindings to jms and ejb-timer service limit the number of deployment environments on which the shipped bytes will work. the result should be that docs are added that describe how a user should deploy jbpm in his web application that gets deployed on tomcat. was:std configs should be the default. bindings to jms and ejb-timer service limit the number of deployment environments on which the shipped bytes will work. -- 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-1819?page=com.atlassian.jira.plug... ] Alejandro Guizar resolved JBPM-1819. ------------------------------------ Resolution: Done IMO the "enterprise" bindings (notice the quotes) should be the default on JBoss since they exploit the available infrastructure and, unlike previous versions, are covered with a continuous build and test suite. For Tomcat and standalone deployments the "standard" bindings are still a must, and we did not cover them properly in 3.3.0.GA. -- 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