Bug 778981 (SOA-1407)

Link: Added: This issue depends JBESB-2672

Linking to JBESB-2672, which represents the ESB 4.6 WS Proxy stuff I implemented.

Linking to JBESB-2746, which represents the quickstarts which demonstrate the capabilities outlined as "P1" in the PRD: webservice_proxy_basic, webservice_proxy_routed, webservice_proxy_versioning.

Link: Added: This issue depends JBESB-2746

You've probably already incorporated the documentation changes from the Programmer's Guide.

Have a look at the JIRAs & the documentation changes that were made.  I suspect that this content would be in the "out of the box" actions chapter under webservices.

Also see if you can find WebService_Proxy_v3.odt if it exists ;-)

Hello David


I believe that Section 11.9 of the SOA 5.0 Programmers' Guide now contains all of the information that you require.

Do you have a copy of the WebService_Proxy_v3.odt document, to which Darrin refers in the comment above?  Does it contain any information that I need to incorporate into the Programmers' Guide?


Many thanks,


David Le Sage

Please provide me a link to the newest SOA-P 5.0 Programmer's Guide.

I do have a copy of the WebService_Proxy_v3.odt file.  I'll take another look at it and respond.

Kevin requested this to be assigned to him for now.

Latest draft of 5.0 Programmers' Guide.

Attachment: Added: Programmers_Guide.pdf

FYI, I've updated the Programmer's Guide on trunk for ESB 4.7:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/docs/ProgrammersGuide.odt
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/docs/ProgrammersGuide.pdf
One of the doc improvements was describing different WSDL URLs that are now supported, per JBESB-2855.

The title of this issue says - Strategy for... - what I found in the documentation is mostly description of SOAPProxy action.
I am assigning it to Burr to verify that the current level of documentation is sufficient. If so the issue can be closed

There was supposed to be a section/chunk of content that would "compare & contrast" the following tools:
- SOAPProxy
- HTTPRouter
- SOAPClient (WISE)
- SOAPClient (non-WISE)
- SOAPProcessor

So that an end-user can make the best decision about which tool to use.

Darrin, I believe you will need to go back to the ESB team for more input on this task.  

Do we have any information that matches Burr's request ?

There is nothing like that in the Programmer's Guide, so it will have to be written.

Link: Added: This issue is a dependency of JBQA-2865

The initial requested content is done, I'll raise a JBESB JIRA for the "compare & contrast" content that Burr would like.

This is not resolved in the docs for ER8.

What is not resolved apart from the "compare & contrast" content that Burr requested ?

I had added this to the SOAPProxy section of the programmer's guid a while back, when distinguishing SOAPProxy from the others:

- SOAPClient is used to invoke external web services, not mirror them.
- SOAPProducer only executes internally-deployed JBoss WS services.
- HttpRouter requires too much by-hand configuration for easy WS proxying.
- EBWS strips out the SOAP Envelope and only passes along the body.

Of course, that should say "SOAPProcessor" not "SOAPProducer" - oops.

Also, here are more specifics on the benefits of SOAPProxy over HttpRouter:

1) HttpRouter can only talk to one endpoint.  One WSDL can specify multiple soap:address locations.  With the SOAPProxy, you just config the one location of the WSDL, and it can dynamically route the request to the correct soap:address location.

2) To use HttpRouter with SOAP, you have to always configure a MappedHeaderList (usually "Content-Type, Accept, Authorization, SOAPAction").  This is unnecessary with the SOAPProxy.

3) The SOAPProxy allows you to specify a wsdlTransform, which allows you to transform the original WSDL to something else you want the SOAPProxy to expose.  (This handles the "versioning" use case, and also usually means you'll want to use XsltAction or SmooksAction in the action pipeline.)

4) If you are proxying to a BASIC Auth secured web service, the "clientCredentialsRequired" property of the SOAPProxy allows you to specify if the credentials should be passed into the SOAPProxy from the client (the default, in which case the credentials are propagated), or if you want the proxy to be wide-open, but *it* will handle the authentication to the proxied service for you.

5) SOAPProxy is designed to talk to more than just HTTP endpoints, although HTTP is all that is implemented right now.

6) When using the new http-gateway to front the SOAPProxy, the ESB will automatically transform and cache the WSDL and make it available at the well-known location of ${endpoint}?wsdl (or ?WSDL). 

Finally, here's a blog post I did a while back which might also help:
http://jbossesb.blogspot.com/2009/11/proxying-soap-web-services-in-jbossesb.html

This content was added to the upstream ESB Programmers Guide.  It would seem to have been missed when updated the product doc.  I'm looking at this now.

opps, resolved.

#1 & 2 added to the list of reasons not to use HttpRouter

#3 is already described

#4 to the list of advantages to using SOAProxy

#5 added as a note at the end of the section

#4 & #6 added to list of what SOAProxy provides

pushed to redhat.com/docs/en-US/JBoss_SOA_Platform/

Closing - the book was updated in the 5.2 release.