[JBoss JIRA] Created: (JBIDE-9789) Changes to the BPEL process are not deployed automatically after save.
4:52 a.m.
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, JBossAS/Servers
Affects Versions: 3.3.0.M3
Environment: JBDS 5.0.0.M3, SOA-5.2.ER4
Reporter: Pavol Srna
Assignee: Robert (Bob) Brodt
Fix For: 3.3.0.M4
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:15 a.m.
New subject: [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...
]
Rob Stryker updated JBIDE-9789:
-------------------------------
Fix Version/s: 3.3.0.Beta1
(was: 3.3.0.M4)
Hey Bob:
Since this is in your area, there's not much I understand about it currently. M4 is
being locked, so pushing this to beta1, but I hope you can replicate it and figure out
what's going wrong. I'll be glad to help in any way that I can. If you cannot
replicate in whatever target environment we have for next release, feel free to close it.
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, JBossAS/Servers
Affects Versions: 3.3.0.M3
Environment: JBDS 5.0.0.M3, SOA-5.2.ER4
Reporter: Pavol Srna
Assignee: Robert (Bob) Brodt
Fix For: 3.3.0.Beta1
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
6:42 a.m.
New subject: [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...
]
Max Rydahl Andersen updated JBIDE-9789:
---------------------------------------
Component/s: (was: JBossAS/Servers)
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: Robert (Bob) Brodt
Fix For: 3.3.0.Beta1
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
7:42 a.m.
New subject: [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...
]
Max Rydahl Andersen updated JBIDE-9789:
---------------------------------------
Fix Version/s: 3.3.0.Beta1
(was: 3.3.0.M5)
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: Robert (Bob) Brodt
Fix For: 3.3.0.Beta1
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
7:42 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on JBIDE-9789:
--------------------------------------------
no movement so punting to next
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: Robert (Bob) Brodt
Fix For: 3.3.0.Beta1
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
8:06 a.m.
New subject: [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...
]
Max Rydahl Andersen updated JBIDE-9789:
---------------------------------------
Fix Version/s: 3.3.0.Beta1-soa
(was: 3.3.0.Beta1)
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: Robert (Bob) Brodt
Fix For: 3.3.0.Beta1-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
3:26 a.m.
New subject: [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...
]
Douglas Palmer updated JBIDE-9789:
----------------------------------
Fix Version/s: 3.3.0.Beta2-SOA
(was: 3.3.0.Beta1-SOA)
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: Robert (Bob) Brodt
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
4:42 p.m.
New subject: [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:
-------------------------------------------
Created https://bugs.eclipse.org/bugs/show_bug.cgi?id=379613
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: Robert (Bob) Brodt
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
4:54 p.m.
New subject: [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:
-------------------------------------------
Fixed for apache/ode 1.3.5 in build 1.0.0.v20120515-2145-H172-CI available from the bpel
update site:
http://download.eclipse.org/bpel/site/
Still investigating jboss/riftsaw (probably caused by the same problem, since riftsaw is
based on ode)
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: Robert (Bob) Brodt
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
8:34 a.m.
New subject: [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 resolved JBIDE-9789.
---------------------------------------
Resolution: Done
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: Robert (Bob) Brodt
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
8:34 a.m.
New subject: [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:
-------------------------------------------
Fixed in trunk. When a single resource is changed, the WST Server class tries to do an
incremental publish (makes sense), which was simply ignored in the JBT BPEL publisher.
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: Robert (Bob) Brodt
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
9:45 a.m.
New subject: [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...
]
Len DiMaggio updated JBIDE-9789:
--------------------------------
Priority: Critical (was: Major)
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: Robert (Bob) Brodt
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
1:53 a.m.
New subject: [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...
]
Andrej Podhradsky commented on JBIDE-9789:
------------------------------------------
Now, after each save the project is redeployed. Is this really a correct behaviour?
Because in JBDS 4 (JBT 3.2) after each save the project wasn't automatically
redeployed, only the status was changed to '[Started, Republish]'. And the project
was redeployed after doing '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: Robert (Bob) Brodt
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
8:55 a.m.
New subject: [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:
-------------------------------------------
I don't know Andrej, ask Pavol. Apparently that's why this JIRA was opened in the
first place...
Please decide what the correct behavior should be, because this JIRA conflicts with
https://issues.jboss.org/browse/JBIDE-11928
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: Robert (Bob) Brodt
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
8:54 a.m.
New subject: [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...
]
Len DiMaggio commented on JBIDE-9789:
-------------------------------------
Pavol,
In the absence of a new defined requirement, why not keep the same behavior as JBDS4?
in JBDS 4: a change resulted in only the status set to 'Republish' and redeploying
is called by 'Full Publish' or 'Incremental 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.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
11:05 a.m.
New subject: [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
6:42 a.m.
New subject: [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...
]
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
10:17 a.m.
New subject: [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
4:02 a.m.
New subject: [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...
]
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....
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
4:08 a.m.
New subject: [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...
]
Andrej Podhradsky edited comment on JBIDE-9789 at 5/31/12 5:07 AM:
-------------------------------------------------------------------
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/topic/org.eclipse.wst.server.ui.doc.user/t...
was (Author: apodhrad):
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....
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
10:41 a.m.
New subject: [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...
]
Len DiMaggio updated JBIDE-9789:
--------------------------------
Fix Version/s: 3.3.0.CR1-SOA
(was: 3.3.0.Beta2-SOA)
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
2:10 a.m.
New subject: [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...
]
RH Bugzilla Integration updated JBIDE-9789:
-------------------------------------------
Bugzilla Update: Perform
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
2:10 a.m.
New subject: [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...
]
RH Bugzilla Integration updated JBIDE-9789:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=827495
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
10:29 a.m.
New subject: [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...
]
RH Bugzilla Integration commented on JBIDE-9789:
------------------------------------------------
Anne-Louise Tangring <atangrin(a)redhat.com> made a private comment on [bug
827495|https://bugzilla.redhat.com/show_bug.cgi?id=827495]
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
12:25 a.m.
New subject: [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...
]
RH Bugzilla Integration commented on JBIDE-9789:
------------------------------------------------
Suz <sdorfiel(a)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
1:23 p.m.
New subject: [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...
]
RH Bugzilla Integration commented on JBIDE-9789:
------------------------------------------------
Len DiMaggio <ldimaggi(a)redhat.com> changed the Status of [bug
827495|https://bugzilla.redhat.com/show_bug.cgi?id=827495] from NEW to MODIFIED
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
8:46 a.m.
New subject: [JBoss JIRA] (JBIDE-9789) Changes to the BPEL process are not deployed automatically after save.
2:43 a.m.
New subject: [JBoss JIRA] (JBIDE-9789) Changes to the BPEL process are not deployed automatically after save.
2:49 a.m.
New subject: [JBoss JIRA] (JBIDE-9789) Changes to the BPEL process are not deployed automatically after save.
4514
days inactive
4782
days old
jbosstools-issues@lists.jboss.org
28 comments
10 participants
participants (10)
-
Andrej Podhradsky (JIRA) -
Douglas Palmer (JIRA)
-
Len DiMaggio (JIRA)
-
Max Rydahl Andersen (Commented) (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Max Rydahl Andersen (Updated) (JIRA)
-
Pavol Srna (JIRA)
-
RH Bugzilla Integration (JIRA)
-
Rob Stryker (Updated) (JIRA)
-
Robert (Bob) Brodt (JIRA)