Bug 780425 (SOA-2857)

Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Complexity: High
Help Desk Ticket Reference: https://access.redhat.com/issue-tracker/1106943
project_key: SOA

Chapter 6.1.5 lists the jars and config files to use the ServiceInvoker in a remote client:

http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/5.0.1/html/Programmers_Guide/chap-SOA_ESB_Programmers_Guide-Example.html#sect-SOA_ESB_Programmers_Guide-Configuration_for_a_Remote_Service_Invoker

However, these instructions could be improved as they are
1. incorrect - some jar files have different version numbers, others are missing
2. unclear - where are the jars/configs? what should be in the xml files?

For #1, the following listed jars have a wrong version number in SOA-P 5.0.1:
juddi-core-3.0.0.aop.jar => juddi-core-3.0.1.jar
juddi-ws-3.0.0.jar  => missing in SOA-P 5.0.1
stax-api-1.0.1.jar => stax-api-1.0.2.jar
scout-1.2.aop.jar => scout-1.2.1.jar
wstx-asl-3.2.0.jar => wstx.jar
jboss-aop-jdk50.jar => missing in SOA-P 5.0.1

For #2, it would be nice to group them according to where they could be found:
- $SOA_HOME/jboss-as/client/
- $SOA_HOME/jboss-as/common/lib/
- $SOA_HOME/jboss-as/server/$SOA_CONF/deployers/esb.deployer/lib/
- etc.

In addition, a note should be added that the listed *.xml files could be taken from the quickstarts directory.