Bug 778654 (SOA-1129) - Is this Registry Guide content relevent to the SOA Product
Summary: Is this Registry Guide content relevent to the SOA Product
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1129
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: 4.3 GA,4.2 CP03
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP04
Assignee: Dana Mison
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-14 02:35 UTC by Dana Mison
Modified: 2009-06-10 16:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-10 16:57:43 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778905 0 high CLOSED QE - ESB Registry Guide 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-1129 0 None None None Never

Internal Links: 778905

Description Dana Mison 2009-01-14 02:35:57 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2009-03-17 23:24:53
project_key: SOA

QE Feedback for the Registry Guide asks how relevant the content of Section 5.1 - Troubleshooting is to the SOA Product.  Content also appears in the 4.3 Services Guide document.

"is it also Product related? It seems to belong only to project"

The references to "install/JUDDI-registry directory", which also occur in other places in this document seem to be project-centric.  What is the appropriate SOA directory that this should be referring to?
Comment 2 Dana Mison 2009-05-28 05:00:21 UTC 
created SOA-1337 for 4.3.CP02
Comment 3 Dana Mison 2009-05-28 06:29:27 UTC 
section 2.5 was updated in SOA-

section 3.3 updated

section 5.1 reference replaced with reference to schema-tool
Comment 4 Dana Mison 2009-06-01 03:23:57 UTC 
Link: Added: This issue is related to SOA-1346
Comment 5 Len DiMaggio 2009-06-10 16:57:43 UTC 
Verified fixed in the Registry Guide in 4.2 CP04 CR4
Note You need to log in before you can comment on or make changes to this bug.