9:24 p.m.
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
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:05 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2978) Tomcat support in jBPM3
[
https://jira.jboss.org/browse/JBPM-2978?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar updated JBPM-2978:
-----------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
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
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
5:05 p.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2978) Tomcat support in jBPM3
[
https://jira.jboss.org/browse/JBPM-2978?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar resolved JBPM-2978.
------------------------------------
Resolution: Done
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
5:05 p.m.
New subject: [JBoss JIRA] Work logged: (JBPM-2978) Tomcat support in jBPM3
[
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
6:05 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2978) Tomcat support in jBPM3
[
https://jira.jboss.org/browse/JBPM-2978?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar updated JBPM-2978:
-----------------------------------
Description:
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. This work quickly took good
shape, so I will commit it under this JIRA ticket.
was:
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.
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. This work quickly took good
shape, so 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
6:16 p.m.
New subject: [JBoss JIRA] Reopened: (JBPM-2978) Tomcat support in jBPM3
[
https://jira.jboss.org/browse/JBPM-2978?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar reopened JBPM-2978:
------------------------------------
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. This work quickly took good
shape, so 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
6:48 p.m.
New subject: [JBoss JIRA] Work logged: (JBPM-2978) Tomcat support in jBPM3
[
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 7:47 PM
Start Date: 17/Nov/10 7:46 PM
Worklog Time Spent: 44 minutes
Work Description: Build jbpm-tomcat module against Tomcat 5.5 and JDK 1.4
Issue Time Tracking
-------------------
Time Spent: 2 hours, 1 minute (was: 1 hour, 17 minutes)
Worklog Id: (was: 12423490)
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: 2 hours, 1 minute
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. This work quickly took good
shape, so 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
6:48 p.m.
New subject: [JBoss JIRA] Work started: (JBPM-2978) Tomcat support in jBPM3
[
https://jira.jboss.org/browse/JBPM-2978?page=com.atlassian.jira.plugin.sy...
]
Work on JBPM-2978 started by Alejandro Guizar.
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: 2 hours, 1 minute
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. This work quickly took good
shape, so 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
11:08 p.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2978) Tomcat support in jBPM3
[
https://jira.jboss.org/browse/JBPM-2978?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar resolved JBPM-2978.
------------------------------------
Resolution: Done
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: 5 hours, 1 minute
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. This work quickly took good
shape, so 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
11:08 p.m.
New subject: [JBoss JIRA] Work logged: (JBPM-2978) Tomcat support in jBPM3
[
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: 18/Nov/10 12:07 AM
Start Date: 18/Nov/10 12:05 AM
Worklog Time Spent: 3 hours
Work Description: Rewrite jBPM3 on Tomcat guide:
http://community.jboss.org/wiki/jBPM3onTomcat
Issue Time Tracking
-------------------
Time Spent: 5 hours, 1 minute (was: 2 hours, 1 minute)
Worklog Id: (was: 12423495)
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: 5 hours, 1 minute
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. This work quickly took good
shape, so 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
9:07 p.m.
New subject: [JBoss JIRA] Work logged: (JBPM-2978) Tomcat support in jBPM3
[
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: 25/Nov/10 10:06 PM
Start Date: 25/Nov/10 10:04 PM
Worklog Time Spent: 15 minutes
Work Description: Move mapped JNDI names from jboss-web.xml to web.xml in the
jsf-console-jee5 module.
Issue Time Tracking
-------------------
Time Spent: 5 hours, 16 minutes (was: 5 hours, 1 minute)
Worklog Id: (was: 12423525)
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: 5 hours, 16 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. This work quickly took good
shape, so 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
5061
days inactive
5075
days old
10 comments
1 participants
participants (1)
-
Alejandro Guizar (JIRA)