[jbosstools-issues] [JBoss JIRA] (JBIDE-9789) Changes to the BPEL process are not deployed automatically after save.

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-9789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700640#comment-12700640 ] 

RH Bugzilla Integration commented on JBIDE-9789:
------------------------------------------------

Suz <sdorfiel at redhat.com> made a comment on [bug 827495|https://bugzilla.redhat.com/show_bug.cgi?id=827495]


    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
If you make a changes to a BPEL process, they will not deploy automatically after saving. This kind of incremental publishing is ignored by BPEL because it results in multiple deployments being triggered at once. Redeploying the process should result in a "full publish".
                
> Changes to the BPEL process are not deployed automatically after save.
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-9789
>                 URL: https://issues.jboss.org/browse/JBIDE-9789
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: BPEL
>    Affects Versions: 3.3.0.M3
>         Environment: JBDS 5.0.0.M3, SOA-5.2.ER4
>            Reporter: Pavol Srna
>            Assignee: Andrej Podhradsky
>            Priority: Critical
>             Fix For: 3.3.0.CR1-SOA
>
>
> 1) Precondition: Say_Hello example project is imported in workspace and deployed to the SOA runtime. Test output with web service explorer.
> 2) Make changes to the process: Change the assign activity, for example change the concat function body to assign another message to the ReplySayHelloVar variable.
> 3) Save the process.
> 4) Server act as it is republishing, but it is not! Changes are not deployed. You can test with web service explorer again. The only scenario that works is to remove and re-add the project to the server runtime via "Add and Remove..." dialog.
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira