[jboss-jira] [JBoss JIRA] Updated: (BPEL-200) Redeployment of a changed PAR (with modified .bpel) requires App Server Restart

[Alejandro Guizar (JIRA)]

     [ http://jira.jboss.com/jira/browse/BPEL-200?page=all ]

Alejandro Guizar updated BPEL-200:
----------------------------------

    Fix Version/s: jBPM BPEL 1.1 GA
                       (was: jBPM BPEL 1.2 GA)

Upon deployment, the web service module finds the latest version of the process definition *at that time*. Picking up the latest version of the process definition is not generally possible because the WSDL interfaces might have changed. The WSEE specification assumes the WSDL description to be immutable; therefore, no API exists to modify it at runtime. The safe, clean path to pick up the newly deployed version of the process definition is to redeploy the web service module as well.

> Redeployment of a changed PAR (with modified .bpel) requires App Server Restart
> -------------------------------------------------------------------------------
>
>                 Key: BPEL-200
>                 URL: http://jira.jboss.com/jira/browse/BPEL-200
>             Project: JBoss jBPM BPEL
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>    Affects Versions: jBPM BPEL 1.1 beta 1
>         Environment: JBoss 4.0.4.GA with EJB3 using beta JEMS installer 
>            Reporter: Burr Sutter
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1 GA
>
>
> Simply modifying the .bpel script, running pack-definition and deploy-definition do not reload/restart the process (even though all process instances have terminated).  The only thing I've found that refreshes the BPEL engine properly is to restart the App Server.

-- 
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