Bug 779491 (SOA-1875) - jUDDI browser displays two Businesses instead of one.
Summary: jUDDI browser displays two Businesses instead of one.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1875
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation, jUDDI - within SOA
Version: 5.0.0 ER7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.0.0 GA
Assignee: David Le Sage
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-25 11:55 UTC by Marek Baluch
Modified: 2010-02-15 19:17 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-15 19:17:51 UTC
Type: Bug

Attachments (Terms of Use)
two_businesses.png (155.72 KB, image/png)
2010-01-25 11:56 UTC, Marek Baluch 		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-1875 0 None None None Never

Description Marek Baluch 2010-01-25 11:55:54 UTC 
Date of First Response: 2010-01-25 10:04:38
project_key: SOA

jUDDI browser displays two Businesses instead of one. This is the case when a new BusinessEntity with two names is published. See attached image.

Steps to reproduce:
(1) save Joe Publisher TModel
(2) save Joe Publisher Business.

- The files above are included as resources for jUDDI integration tests in trunk.
Comment 1 Marek Baluch 2010-01-25 11:56:17 UTC 
Attachment: Added: two_businesses.png
Comment 3 David Le Sage 2010-02-12 04:24:50 UTC 
I have added the following draft text to the Release Notes:


https://jira.jboss.org/jira/browse/SOA-1875

    When a new BusinessEntity with two names is published, the jUDDI Browser will display two
    businesses instead of one. This is because the user interface treats business names as strings
    and does not check them for uniqueness: the keys are the only unique identifiers.
Note You need to log in before you can comment on or make changes to this bug.