[jbossws-dev] [Design of JBoss Web Services] - Re: Exception propagation for one way messaqges

thomas.diesler@jboss.com do-not-reply at jboss.com
Tue Oct 2 04:54:04 EDT 2007


Jason sais:

anonymous wrote : 
  | >> When I generate the interface and server stub code the corresponding web 
  | >> methods are tagged with an @OneWay annotation. My question regarding the 
  | >> spec is very simple: what is meant to happen if the implementation of 
  | >> such a one way method throws a SoapFaultException, a ProtocolException 
  | >> or some other Exception? Is the JaxWS implementation supposed to throw a 
  | >> corresponding exception in the client context? The sections of the spec 
  | >> I cited in my original post do not make the answer clear.
  | 

No, it can not, it violates the WS-I BP 1.0 which JAX-WS conforms to:

http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16651160

"R2714 - For one-way operations, an INSTANCE MUST NOT return a HTTP 
response that contains a SOAP envelope. Specifically, the HTTP response 
entity-body must be empty."

That said, you can still present a different WSDL to a consumer than the 
semantic one in operation. Just removing @OneWay should do the trick If 
a XTS endpoint returns SOAP responses, then it really is a two-way endpoint.

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

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



More information about the jbossws-dev mailing list