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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-9789:
--------------------------------------------

Pavol/Len - you guys seem to be mixing up terms here ;)

There is *publish* and there is *deploy*

Publish is "copy files from project over to the server"

Deploy is "actually having the files picked up and deploy on the server".

Wether Publish happens or not is set on the server adapter in its server editor under "Publishing". If this one says it is publishing on change then it should be publishing on every change.

Wether Deploy happens or not is dependent on the server, runtime and its version and capabilities.

i.e. html and xhtml content is automatically deployed/recognized by all our servers by default, but class changes are not.

For BPEL I believe the same situation occurs, publishing files to the server does not mean it should automatically publish if the server runtime does not support it.

Thus it is not true that when you save a change in Seam it will be automatically deployed -only parts of it will be.

Thus it sounds like the behavior was correct in JBDS4.

The reason for ignoring incremental publish was done afaik because it otherwise triggered alot of deployments which was not wanted by BPEL users.

                
> 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