[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...
]
Pavol Srna commented on JBIDE-9789:
-----------------------------------
I opened this jira, because I thought that this behaviour is not correct. For example look
at the seam project. When you make a change in a seam project all the changes are
automatically deployed after save. And I liked the idea that all the JBossTools projects
act the same. But no problem if we keep the same behaviour as JBDS4.
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