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

[Andrej Podhradsky (JIRA)]

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

Andrej Podhradsky commented on JBIDE-9789:
------------------------------------------

Let me make it clear:

JBDS 4: The behavior follows the behaviour described at [1], e.g. when some changes are detected (after save), the status is changed to 'Republish', nothing else happens.
JBDS 5 - before this fix: When changes are saved, the status is changed to 'Republish' and immediately changed to 'Synchronized', but nothing happens - changes are not copied to the server. 'Full Publish' doesn't work, so the only way is to remove and add the bpel project from/to the server.
JBDS 5 - now: When the bpel project is added to the server, the status is immediately changed to 'Republish', see more at [JBIDE-11928]. After saving some changes, the status is changed to 'Synchronized' and changes take effect on the server (this is good, but the question is if this is a correct behaviour).

So, there are two ways:

a) Changes autimatically take effect on the server after each save. This is now, only the statuses should be fixed [JBIDE-11928].

b) After changes are saved, only the status will be changed as described at [1] (JBDS4 behaviour) and some action, e.g. 'Full Publish', should be done to copy changes to the server.  

[1] http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.wst.server.ui.doc.user%2Ftopics%2Ftdecor.html

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