| Summary: | Services' undeployment not reflected in jUDDI console in SOA-P 5.0 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> | ||||||
| Component: | Tooling, jUDDI - within SOA | Assignee: | tcunning | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 5.0.0 ER8 | CC: | kevin.conner, kurt.stam, rbalent | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 5.2.0 GA, 5.2.0.ER4 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-1918 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: |
ER8 build
|
|||||||
| Last Closed: | 2011-11-15 17:13:32 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: | |||||||
| Attachments: |
|
||||||||
Attachment: Added: Screenshot.png Attachment: Added: Screenshot-1.png Candidate for SOA 5.1.0. Not committed. John to talk to Kurt Not sure this is a bug. The service details will still be present in the UDDI repository but the *binding* will be removed when undeployed. This turned out to be a real issue and the tree is now refreshed when the user clicks on parent node in the tree: Fixed in: https://issues.apache.org/jira/browse/JUDDI-524. Added fix into SAO-P 5.2.0.ER4 Reopening. I can still reproduce it in 5.2.0.ER4. And additionally services stay in jUDDI console after server restart too. Hi Robert, can you take a look at the bindings? ESB leaves the service definitions IN, but will unregister the bindings. You will have to click in the tree for the refresh to happen. If Kurt has fixed the refresh issue, then I think at this point this is not really a bug. When an .esb archive is undeployed, the service is not unregistered from jUDDI. All bindings for that service are unregistered, but the service itself is not unregistered. I would expect to see the results you are getting. See Kevin's comment from January. Release Notes Docs Status: Added: Not Required Writer: Added: dlesage |
project_key: SOA To recreate: 1) Startup server, log into jUDDI console 2) Deploy .esb (for example, helloworld quickstart) 3) Refresh browser display, verify 'SimpleListener' service is listed under "Services owned by this business" (see attached screenshot) 4) Undeploy the quickstart 5) Refresh browser display, verify 'SimpleListener' service is still listed under "Services owned by this business" 6) Select 'SimpleListener' service - error dialog ("null") is displayed (see attached screenshot) 7) Close and reopen browser, verify 'SimpleListener' service is still listed under "Services owned by this business" 8) Delete cookie "JSESSIONID", verify 'SimpleListener' service is still listed under "Services owned by this business" 9) The only way that I can see to get the console to accept that the service is not deployed is to restart the server