Hi All,
I'm currently working on a project using web services. An architect has made a decision to use
EJB bindings to enhance performance between certain components. However, this means we are unable to access the
SOAP message (because there is no SOAP message involved using with an rmi call!) and obviously the jax-rpc handler will not be invoked either.
Unfortunately, there is a requirement that we need to audit the SOAP requests as they come in. So there is a suggestion to build a SOAP envelope and pass it to the EJB as a parameter. I'd rather avoid this because it is messy, requires parsing of the SOAP envelope in the bean, and negates the point of using web services.
In order to convince the architect that the decision is a bad one I need to be able to show that there is no performance benefit of using EJB bindings as opposed to a JAX-RPC call.
Can anyone point me documentation or if anyone has any experience of performance differences then please let me know as soon as possible!
Thanks and Regards,
Tom