[jboss-dev-forums] [Design of JBoss ESB] - Re: SOAPProxy Enhancements

[ammppp]

One other request related to this area - and I think HttpRouter already supports it (so SoapProxy probably does as well), though I don't think it is documented.

In some cases, SoapProxy may be used within the ESB action chain for more than just serving as THE internal endpoint for the ESB service.

For example, consider a case in order for the ESB to transform the incoming client request to the request needed by the endpoint WS, the ESB needs to get additional information from a different auxiliary web service (maybe to get defaults, maybe to check authorization, maybe to check system load, maybe something else).  In this case, the client sends request to the ESB, the ESB invokes a check authorization web service or get defaults web service, augments the original client's message and forwards to the internal WS endpoint.

In this case, it would be nice if the SoapProxy could send a message and store back a response in some ESB location other than the default message body because the default message body is storing the main ESB service message that is going to be augmented.

One could write some custom actions to move ESB message parameters around before/after invoking the auxiliary web service, but would be nice if the SoapProxy could just specify that message to be sent is coming from a different location than the default message body and the auxillery SoapProxy response could be stored in a different location than the default message body.  Probably wouldn't want the HTTP parameters and such to be set on the ESB message default locations either since it's not the "real" service being invoked.

Hope that makes sense.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245611#4245611

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245611