Bug 825304
| Summary: | Status is not correct after deploying the BPEL project | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | Tooling | Assignee: | Nobody <nobody> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.3.0 GA | CC: | soa-p-jira |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | FUTURE | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-08 18:59:26 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-05-25 15:32:51 UTC
Robert (Bob) Brodt <bbrodt> updated the status of jira JBIDE-11928 to Resolved Robert (Bob) Brodt <bbrodt> made a comment on jira JBIDE-11928 Fixed. I reverted my previous change, so behavior should be the same as before. Len DiMaggio <ldimaggi> 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. Len DiMaggio <ldimaggi> updated the status of jira JBIDE-11928 to Closed Andrej Podhradsky <apodhrad> updated the status of jira JBIDE-11928 to Reopened Andrej Podhradsky <apodhrad> 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. Len DiMaggio <ldimaggi> 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. " Andrej Podhradsky <apodhrad> 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). Andrej Podhradsky <apodhrad> 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. Andrej Podhradsky <apodhrad> 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. Andrej Podhradsky <apodhrad> 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. Re-opening this bz - after 5.3 GA we should discuss if we want this solution for the long-term. This is NOT a blocker for the 5.3 release. Can someone nack the blocker flag? |