[
https://jira.jboss.org/jira/browse/JBESB-3304?page=com.atlassian.jira.plu...
]
David Ward closed JBESB-3304.
-----------------------------
Resolution: Done
The Programmer's Guide and javadoc were updated, as well as removing
possibly-confusing XML comments of the unrecommended wsdl scheme from the quickstarts.
$ svn commit
Sending product/docs/ProgrammersGuide.odt
Sending product/docs/ProgrammersGuide.pdf
Sending product/samples/quickstarts/webservice_proxy_basic/jboss-esb.xml
Sending product/samples/quickstarts/webservice_proxy_basic/readme.txt
Sending product/samples/quickstarts/webservice_proxy_routed/jboss-esb.xml
Sending
product/samples/quickstarts/webservice_proxy_security/jboss-esb-template.xml
Sending product/samples/quickstarts/webservice_proxy_versioning/jboss-esb.xml
Sending
product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/proxy/SOAPProxy.java
Transmitting file data ........
Committed revision 32772.
Add better description of SOAPProxy wsdl property URI schemes
-------------------------------------------------------------
Key: JBESB-3304
URL:
https://jira.jboss.org/jira/browse/JBESB-3304
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Documentation, Web Services
Affects Versions: 4.7 CP1
Reporter: David Ward
Assignee: David Ward
Fix For: 4.7 CP2
The documentation here:
http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/5.0.0/html/Programmer...
lists examples for the http://, https://, file://, classpath:// and internal:// schemes,
but should give detail on when you would use which scheme. The internal:// scheme is the
one that could be most confusing to readers.
Additionally, there is a typo on the classpath:// example.
classpath://META-INF/HelloWorldWS.wsdl should instead be
classpath:///META-INF/HelloWorldWS.wsdl (with 3 slashes). The "classpath://"
prefix is chopped off during parsing, and 1 more slash is needed for absolute classpath
resource loading, otherwise relative classpath resource loading is employed. This is NOT
a bug - it was intended to work that way - but the documentation should be updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira