Bug 779441 (SOA-1826)

Summary: Documentation references uddi.xml for JUDDI transports
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: tcunning
Component: DocumentationAssignee: Dana Mison <dmison>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER6   
Target Milestone: ---   
Target Release: 5.0.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1826
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-17 15:17:21 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:

Description tcunning 2010-01-13 20:11:43 UTC 
Date of First Response: 2010-01-14 04:12:12
project_key: SOA

In the ESB Services guide, the documentation mentions that you can change JUDDI transports by altering server/<config>/deploy/jbossesb.sar/META-INF/uddi.xml.        This file doesn't exist anymore - I believe that it has been replaced by server/<config>/jbossesb.sar/esb.juddi.client.xml.
Comment 1 tcunning 2010-01-13 20:13:13 UTC 
This is in Section 1.2.5 - additionally this section mentions that RMI is the default transfer.      I don't believe that's correct anymore either.
Comment 2 Kevin Conner 2010-01-14 09:12:12 UTC 
This is correct, uddi.xml has never been used in the ESB integration.  The esb.juddi.client.xml is pre-processed by us, to allow for variable substitution in the same way as the v2 integration.

The same holds for juddiv3.properties, which was replaced by esb.juddi.xml for the same reason.

The default transport is also our own InVM transport rather than  jUDDI specific one.
Comment 3 Kevin Conner 2010-01-14 09:43:31 UTC 
Link: Added: This issue related JBESB-3119
Comment 4 Len DiMaggio 2010-01-22 01:38:40 UTC 
Link: Added: This issue related SOA-1657
Comment 5 Dana Mison 2010-02-15 07:24:51 UTC 
updated in "Configuring the Registry" and "Registry Configuration Examples"