Bug 778575 (SOA-1047)

Summary: Cleanup ESB Registry Guide
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Dana Mison <dmison>
Component: DocumentationAssignee: Jiri Pechanec <jpechane>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 CP02   
Target Milestone: ---   
Target Release: 4.2 CP03   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1047
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-14 08:01:56 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dana Mison 2008-11-21 03:56:13 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2008-12-16 11:41:12
project_key: SOA

11 code samples to update
trim 3 screenshots

Comment 1 Dana Mison 2008-12-02 07:13:26 UTC
updated

Comment 2 Len DiMaggio 2008-12-16 16:41:12 UTC
Assigning to QE for review



Comment 3 Jiri Pechanec 2009-01-06 07:56:57 UTC
What is JBoss Enterprise SOA Platform Edition 1.4 on page 2?
Page 3 - not sure if this is correct: It may be updated dynamically when services first start-up, or
statically by an external administrator.
Page 6 - Is still Systinet in business? http://en.wikipedia.org/wiki/Mercury_Interactive
Page 6 - SystinetRegistryImplentation should be SystinetRegistryImplementation
Page 7 - Strange formating of tables and table names
Page 7 - There is no directory product/install/jUDDI-registry with juddi sql scripts, same for page 10, files are in ${deploydir}/jbossesb.sar/juddi-sql and warfile is in ${deploydir}/jbossesb.sar
Page 14 - the description is definitely not complete, to use AxisTransoprt, one must also put axis.jar to classpath - Tom C. has more info
Chapter 4 - JBDS also provides UDDI browser - should not we promote it here?
Section 5.1 - is it also Product related? It seems to belong only to project

Comment 4 Jiri Pechanec 2009-01-06 07:57:49 UTC
Address on title page
1801 Varsity Drive
Raleigh, NC 27606-2072USAPhone: +1 919 754 3700
Phone: 888 733 4281
Fax: +1 919 754 3701
PO Box 13588Research Triangle Park, NC 27709USA
- see missing spaces

Comment 5 Dana Mison 2009-01-09 04:46:30 UTC
1 - the 1.4 refers to the book edition

2 - need confirmation on its behaviour

3 - I don't think this really matters, although it would be nice to have more current examples if that is the case

4 - FIXED: corrected typo

5- FIXED: the 3 tables want to be a single table with settings on one axis & transport type on the other, but the content is way to wide to fit it on a page :-(  I changed the formatting a little to try to make it clearer.

6 - Need more information.  "The product/install/jUDDI-registry directory contains db create scripts for you favorite database. "jbossesb.sar/juddi-sql doesn't contain database creation scripts, it has import scripts.  jboss-as/server/production/deploy/jbossesb.sar/lib/juddi-2.0rc5.aop.jar seems to have creation scripts.  Are users expected to unpack the jar to get at the files?

7 - where does axis.jar come from ?  I need more information

8 - FIXED: added a comment about JBDS included a UDDI browser.  Also updated some of the language as was done for the corresponding content  in the 4.3 Services Guide

9 - need confirmation if this should be removed

10 - spacing in address has been fixed in book template


Comment 6 Jiri Pechanec 2009-01-13 07:41:43 UTC
1 - OK 

2 - Has to be answered by the dev team 

3 - OK 

4 - VERIFIED 

5- VERIFIED 

6 - You are right the user must use files from both JAR file (unpack it) and fro the directory. Moreover please look at the SQL files. Table nasmes are prefixed with ${prefix} string. So if the files are used manually this sting must be either removed or replaced with value of paramter juddi.tablePrefix fro esb.juddi.xml file

7 - Look at https://jira.jboss.org/jira/browse/JBQA-1587?focusedCommentId=12420807#action_12420807 Just note, the step to replace scout libraries is no longer needed 

8 - VERIFIED 

9 - Has to be answered by the dev team 

10 - VERIFIED

Comment 7 Dana Mison 2009-01-14 07:09:06 UTC
I have created 4 new JIRAs for the outstanding items to have then resolved in future releases.
SOA-1127
SOA-1128
SOA-1129
SOA-1132

Comment 8 Jiri Pechanec 2009-01-14 08:01:56 UTC
Verified and agree