Bug 825304 - Status is not correct after deploying the BPEL project
Summary: Status is not correct after deploying the BPEL project
Keywords:
Status: ASSIGNED
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Tooling
Version: 5.3.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: FUTURE
Assignee: Default User
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-25 15:32 UTC by Len DiMaggio
Modified: 2013-10-09 11:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-08 18:59:26 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
JBoss Issue Tracker JBIDE-11928 Critical Reopened Status is not correct after deploying the BPEL project 2013-01-21 12:11:17 UTC

Description Len DiMaggio 2012-05-25 15:32:51 UTC
Description of problem:

Link to: JBIDE-11928

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


How reproducible:


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


Expected results:


Additional info:

Comment 1 JBoss JIRA Server 2012-06-01 23:34:18 UTC
Robert (Bob) Brodt <bbrodt@redhat.com> updated the status of jira JBIDE-11928 to Resolved

Comment 2 JBoss JIRA Server 2012-06-01 23:34:18 UTC
Robert (Bob) Brodt <bbrodt@redhat.com> made a comment on jira JBIDE-11928

Fixed. I reverted my previous change, so behavior should be the same as before.

Comment 6 JBoss JIRA Server 2012-06-08 19:00:53 UTC
Len DiMaggio <ldimaggi@redhat.com> made a comment on jira JBIDE-11928

3) How do we want BPEL processes to behave when changed (auto republish?) in JBDS: https://issues.jboss.org/browse/JBIDE-9789
We won't block the release for it. Leave as is. Documentation is needed to say this is done intentionally.

Comment 7 JBoss JIRA Server 2012-06-08 19:02:54 UTC
Len DiMaggio <ldimaggi@redhat.com> updated the status of jira JBIDE-11928 to Closed

Comment 8 JBoss JIRA Server 2012-06-11 12:13:08 UTC
Andrej Podhradsky <apodhrad@redhat.com> updated the status of jira JBIDE-11928 to Reopened

Comment 9 JBoss JIRA Server 2012-06-11 12:13:08 UTC
Andrej Podhradsky <apodhrad@redhat.com> made a comment on jira JBIDE-11928

Where is this fixed? I tried JBDS 5 CR1 with SOA Tooling Beta3 and also nightly builds but the problem is still there.

Comment 10 JBoss JIRA Server 2012-06-11 17:52:39 UTC
Len DiMaggio <ldimaggi@redhat.com> made a comment on jira JBIDE-11928

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

Comment 11 JBoss JIRA Server 2012-06-22 08:31:46 UTC
Andrej Podhradsky <apodhrad@redhat.com> made a comment on jira JBIDE-11928

Bob wrote: "I reverted my previous change, so behavior should be the same as before."

But this behaviour is still in SOA Tooling CR1, but the behaviour of JBIDE-9789 has changed to the behavior from JBDS 4 (ok, we can leave as is).

Now, what does "Leave as is" mean in this case? Should be documented that after deploying the bpel project, the status is set to 'Republish'?
I think the statuses should be like in JBDS 4 (JBIDE-9789 behaves also like in JBDS 4).

Comment 12 JBoss JIRA Server 2012-06-22 08:42:29 UTC
Andrej Podhradsky <apodhrad@redhat.com> made a comment on jira JBIDE-11928

Eclipse help says:
Synchronized 	Both copies of the application files on the server and in the workbench are matching.
Republished 	The copy of the application files on the workbench has changed and does not match the copy on the server. The server needs to be updated.

I think it is a good idea to follow this.

Comment 13 JBoss JIRA Server 2012-06-22 08:43:01 UTC
Andrej Podhradsky <apodhrad@redhat.com> made a comment on jira JBIDE-11928

Eclipse help says:
[Synchronized] 	Both copies of the application files on the server and in the workbench are matching.
[Republished] 	The copy of the application files on the workbench has changed and does not match the copy on the server. The server needs to be updated.

I think it is a good idea to follow this.

Comment 14 JBoss JIRA Server 2012-06-22 08:44:24 UTC
Andrej Podhradsky <apodhrad@redhat.com> made a comment on jira JBIDE-11928

Eclipse help says:
[Synchronized] 	Both copies of the application files on the server and in the workbench are matching.
[Republished] 	The copy of the application files on the workbench has changed and does not match the copy on the server. The server needs to be updated (in our case we should do 'full publish').

I think it is a good idea to follow this.

Comment 15 Len DiMaggio 2012-07-18 14:29:32 UTC
Re-opening this bz - after 5.3 GA we should discuss if we want this solution for the long-term.

Comment 16 Len DiMaggio 2012-07-18 19:26:28 UTC
This is NOT a blocker for the 5.3 release. Can someone nack the blocker flag?


Note You need to log in before you can comment on or make changes to this bug.