Bug 780345 (SOA-2753) - Location of juddi-ds.xml incorrect in documentation
Summary: Location of juddi-ds.xml incorrect in documentation
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2753
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation
Version: 5.0.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 5.2.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: 2011-01-06 22:32 UTC by Jeff McDermott
Modified: 2011-11-14 17:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-14 17:49:38 UTC
Type: Bug


Attachments (Terms of Use)


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

Description Jeff McDermott 2011-01-06 22:32:03 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
project_key: SOA

http://docs.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html-single/ESB_Administration_Guide/index.html#Switching_Databases

Under the section "1.6.1.  Switching Databases Manually " the location of the juddi-ds.xml is incorrect. the file resides at the following location (deploy\jbossesb-registry.sar\juddi-ds.xml)

Comment 1 Kevin Conner 2011-01-07 09:58:30 UTC
This has been fixed through JBESB-3460, current text is 

"Replace the contents of deploy/jbossesb-registry.sar/juddi-ds.xml with the same configuration as that created in the previous step (change the database name if need be.)"

Comment 2 Kevin Conner 2011-01-07 09:59:31 UTC
I should add that JBESB-3460 is already included in SOA 5.1

Comment 3 tcunning 2011-07-29 18:07:40 UTC
David - this has been fixed on the ESB side - is there anything that needs to be done on the platform documentation side to pick this change up?

Comment 4 David Le Sage 2011-09-02 06:01:11 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.