Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 827495

Summary:	Changes to the BPEL process are not deployed automatically after save
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Len DiMaggio <ldimaggi>
Component:	Tooling	Assignee:	Default User <jbpapp-maint>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.3.0 GA	CC:	dlesage, dpalmer, sdorfiel, soa-p-jira
Target Milestone:	CR1
Target Release:	5.3.0 GA
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	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".	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-21 13:45:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Len DiMaggio 2012-06-01 15:42:36 UTC

Description of problem:

Link to: https://issues.jboss.org/browse/JBIDE-9789

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Suz 2012-06-12 05:24:28 UTC

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

Comment 3 JBoss JIRA Server 2012-06-21 13:43:23 UTC

Len DiMaggio <ldimaggi> made a comment on jira JBIDE-9789

The consensus with PGM and PM was to: "Leave as is. Documentation is needed to say this is done intentionally. "

Comment 4 JBoss JIRA Server 2012-06-22 07:42:43 UTC

Andrej Podhradsky <apodhrad> made a comment on jira JBIDE-9789

Situation in SOA Tooling CR1:
Now, the behaviour is like in JBDS 4. After saving some changes only the status is changed to 'Republish'. The changes take affect after doing 'full publish'.

Comment 5 JBoss JIRA Server 2012-06-22 07:48:50 UTC

Andrej Podhradsky <apodhrad> updated the status of jira JBIDE-9789 to Closed

Comment 6 JBoss JIRA Server 2012-06-22 07:48:50 UTC

Andrej Podhradsky <apodhrad> made a comment on jira JBIDE-9789

We can close this issue as it has been resolved. But note that status should be fixed (JBIDE-11928).