[jbosstools-issues] [JBoss JIRA] (JBIDE-9789) Changes to the BPEL process are not deployed automatically after save.
[
https://issues.jboss.org/browse/JBIDE-9789?page=com.atlassian.jira.plugin...
]
Robert (Bob) Brodt commented on JBIDE-9789:
-------------------------------------------
OK, I'm still not sure what the desired behavior should be. For riftsaw, as soon as
you publish a change (i.e. "copy files from project to server"), the changes are
automatically detected and picked up by the riftsaw bpel engine. So, it's not possible
to separate publish from deploy.
So...what do you want me to do here guys? Should I change it back to the way it was
(don't copy anything to the server until user actually clicks the "publish"
button)?
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