Bug 778653 (SOA-1128)

Summary: incomplete example in ESB Registry Guide
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Dana Mison <dmison>
Component: DocumentationAssignee: Dana Mison <dmison>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.3 GACC: darran.lofthouse, dllamber
Target Milestone: ---   
Target Release: 4.2 CP04   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1128
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-06-10 16:59:30 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:
Attachments:
Description Flags
server.log none

Description Dana Mison 2009-01-14 02:28:42 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2009-03-20 03:49:58
project_key: SOA

QE feedback reported the SOAP example from Chapter 3 Section 5 is missing details required to implement.

"the description is definitely not complete, to use AxisTransport, one must also put axis.jar to classpath - Tom C. has more info 

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

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"

The content is also the same in the corresponding section of the 4.3 Services Guide as well.  Are the details the same ?
Comment 2 Jim Ma 2009-03-20 07:51:08 UTC 
Attachment: Added: server.log
Comment 5 Jim Ma 2009-03-23 05:42:49 UTC 
Link: Added: This issue depends JBESB-2487
Comment 6 Dana Mison 2009-05-28 04:00:58 UTC 
Q: Is it correct to say: you need the axis & commons-discovery jars for this to work, which aren't provided in soa-p so you need to download then from http://ws.apache.org/axis/ ?

Q: I'm not sure what the intent of this suggested passage is: 
"When user configure scout to use AixsTransport , the remote juddi server should be configured. 
Do not configure the local server(the server which runs the jbossesb.sar) to the juddi query and publish url like this : 

     <property name="org.jboss.soa.esb.registry.queryManagerURI" value="http://localhost:8080/juddi/inquiry"/> 
     <property name="org.jboss.soa.esb.registry.lifeCycleManagerURI" value="http://localhost:8080/juddi/publish"/>
"
Comment 7 Dana Mison 2009-06-01 03:23:04 UTC 
Link: Added: This issue is a dependency of SOA-1346
Comment 8 Dana Mison 2009-06-01 03:23:20 UTC 
Link: Removed: This issue is a dependency of SOA-1346
Comment 9 Dana Mison 2009-06-01 03:23:37 UTC 
Link: Added: This issue is related to SOA-1346
Comment 10 tcunning 2009-06-01 19:49:23 UTC 
Q: Is it correct to say: you need the axis & commons-discovery jars for this to work, which aren't provided in soa-p so you need to download then from http://ws.apache.org/axis/ ? 

Yes.   You could even point to the 1.4 version.



Q: I'm not sure what the intent of this suggested passage is:
"When user configure scout to use AixsTransport , the remote juddi server should be configured.
Do not configure the local server(the server which runs the jbossesb.sar) to the juddi query and publish url like this :

     <property name="org.jboss.soa.esb.registry.queryManagerURI" value="http://localhost:8080/juddi/inquiry"/>
     <property name="org.jboss
  .soa.esb.registry.lifeCycleManagerURI" value="http://localhost:8080/juddi/publish"/>
" 

Can you get me a link to the current version of the doc?     I can't find where this exists in "chapter 3, section 5".      If this is in the context of SOA Software integration - like I think it is - then the above note about not using axis inquiry/publish URLs seems confusing and not needed.
Comment 11 Dana Mison 2009-06-02 00:41:05 UTC 
In 4.2 : http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.2.CP03/html/SOA_ESB_Registry_Guide/ch03s05.html

in 4.3 : http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP01/html/Services_Guide/sect-SOA_ESB_Services_Guide-Configuring_Examples-SOAP.html
Comment 12 tcunning 2009-06-02 06:59:05 UTC 
I think adding that you need axis-1.4.jar and commons-discovery-0.2.jar for this to work and giving the location from where they can be downloaded is sufficient.
Comment 13 tcunning 2009-06-02 14:30:01 UTC 
Adding additional notes from the email trail -

It seems like the error in the log results from trying to use SOAP as the transport on the same AS as the registry resides.      This is not a best practice.    In this scenario, you will get errors because of the deployment order - the web deployer will not be ready for requests until full startup, and the ESB is going to look to register endpoints before that.       In this situation - where you are running on the same AS, you want to use LocalTransport.

SOAP is best when you are running your registry on a different AS (like the SOA Software integration or a remote jUDDI).
Comment 14 Dana Mison 2009-06-03 06:14:21 UTC 
Link: Added: This issue is related to SOA-1352
Comment 15 Dana Mison 2009-06-03 06:18:38 UTC 
As Axis is not included or supported in the SOA Platform product I have replaced this sections content with the following:

SOAP

Scout can be configured to use SOAP to communicate with jUDDI using Apache Axis.  This is not currently supported in the JBoss SOA Platform although future versions may add SOAP support.  
 
Additional information regarding this can be found at the Apache Axis website at: http://ws.apache.org/axis/
Comment 16 Len DiMaggio 2009-06-10 16:59:30 UTC 
Verified fixed in section:  2.5. Using Scout and jUDDI

Of the Registry Guide in 4.2 CP04 CR4