[
https://jira.jboss.org/browse/JBPM-2978?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar logged work on JBPM-2978:
------------------------------------------
Author: Alejandro Guizar
Created on: 17/Nov/10 6:03 PM
Start Date: 17/Nov/10 6:01 PM
Worklog Time Spent: 1 hour, 17 minutes
Work Description: Offer Tomcat 5.5 option from installer, in addition to Tomcat 6.0
Issue Time Tracking
-------------------
Time Spent: 1 hour, 17 minutes
Worklog Id: (was: 12423489)
Tomcat support in jBPM3
-----------------------
Key: JBPM-2978
URL:
https://jira.jboss.org/browse/JBPM-2978
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Time Spent: 1 hour, 17 minutes
Remaining Estimate: 0 minutes
A recent question in the user forum got me to write a guide for deploying jBPM3 to
Tomcat:
http://community.jboss.org/wiki/jBPM3onTomcat . I noticed there were several
issues that complicated the deployment path, notably:
* The standard DataSourceRealm cannot accommodate the jBPM3 identity model. A custom
Realm is required.
* Tomcat lacks many dependencies taken for granted in JBoss AS, such as JSF and
Hibernate.
* Since Tomcat is not an EJB container, the jbpm-enterprise.jar module is inapplicable.
The job executor has to be started through a servlet context listener.
The difficulties associated to describing and explaining such drastic changes led me to
start a Maven overlay that dealt with the above issues neatly. By the time I noticed, this
work had already taken good shape, so rather than just discarding the work I will commit
it under this JIRA ticket.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira