Bug 779541 (SOA-1918) - Services' undeployment not reflected in jUDDI console in SOA-P 5.0
Summary: Services' undeployment not reflected in jUDDI console in SOA-P 5.0
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-1918
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Tooling, jUDDI - within SOA
Version: 5.0.0 ER8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0 GA,5.2.0.ER4
Assignee: tcunning
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-03 16:42 UTC by Len DiMaggio
Modified: 2011-11-15 17:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
ER8 build
Last Closed: 2011-11-15 17:13:32 UTC
Type: Bug

Attachments (Terms of Use)
Screenshot.png (202.53 KB, image/png)
2010-02-03 16:43 UTC, Len DiMaggio 		no flags Details
Screenshot-1.png (166.36 KB, image/png)
2010-02-03 16:43 UTC, Len DiMaggio 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1918 0 None None None Never

Description Len DiMaggio 2010-02-03 16:42:57 UTC 
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
Comment 1 Len DiMaggio 2010-02-03 16:43:33 UTC 
Attachment: Added: Screenshot.png
Attachment: Added: Screenshot-1.png
Comment 2 Anne-Louise Tangring 2010-09-21 19:38:16 UTC 
Candidate for SOA 5.1.0. Not committed.
Comment 3 Anne-Louise Tangring 2010-12-02 16:32:37 UTC 
John to talk to Kurt
Comment 5 Kevin Conner 2011-01-05 10:48:30 UTC 
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.
Comment 6 Kurt Stam 2011-09-12 17:01:22 UTC 
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.
Comment 7 Douglas Palmer 2011-09-13 10:46:11 UTC 
Added fix into SAO-P 5.2.0.ER4
Comment 8 Robert Balent 2011-09-20 12:31:03 UTC 
Reopening. I can still reproduce it in 5.2.0.ER4.

And additionally services stay in jUDDI console after server restart too.
Comment 9 Kurt Stam 2011-09-20 13:47:41 UTC 
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.
Comment 10 tcunning 2011-09-22 15:18:08 UTC 
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.
Comment 11 David Le Sage 2011-09-27 04:26:36 UTC 
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage
Note You need to log in before you can comment on or make changes to this bug.