[
http://jira.jboss.com/jira/browse/BPEL-239?page=all ]
Alejandro Guizar resolved BPEL-239.
-----------------------------------
Resolution: Done
Introduced a GenericArchiveParser that examines the contents of the process archive and
invokes either the jPDL parser chain or the BPEL parser chain as appropriate. This sovles
the problem for now. However, the ability to detect the type of a process archive and
delegate to a specific parser chain should be pushed up to the jBPM core.
detect and deal with jpdl deployments
-------------------------------------
Key: BPEL-239
URL:
http://jira.jboss.com/jira/browse/BPEL-239
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1.GA
Because BPEL overrides the default archive parser chain, normal jPDL deployment is no
longer possible. To handle this situation, follow these steps:
1. Detect jPDL deployments: look for a "processdefinition.xml" entry.
2. If the process archive contains a jPDL process,
then: call the jPDL handler chain
otherwise: call the BPEL handler chain
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira