cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From liucong <liucon...@gmail.com>
Subject Re: How to implement the SOAP Fault for JMS Transport?
Date Tue, 09 Jun 2009 02:15:19 GMT
Hi,

Willem Jiang 写道:
> Hi,
>
> I think you mean how to throw the fault from the JMS transport.
> Basically , if you throw the fault from a CXF interceptor, CXF's
> interceptors chain will take care of it and build the fault message and
> throw it out.
>
> If you want to check the Content type , you could write an interceptor
> and load it with your soap jms transport. But I think  you could take
> the soap binding (SoapBindingFactory) as an example, and put this kind
> of checking as a work of soap jms binding.
>
>   
SoapBindingFactory gets the binding information according to the
bindingid, for example, http://schemas.xmlsoap.org/wsdl/soap/. SOAP/JMS
may not provide a SOAP JMS binding id or something like that. I think we
should not add bindingid, too.
> Just my 2 cents,
>
> Willem
>
>
> liucong wrote:
>   
>> Hi all,
>>
>> When I implement the SOAP Over JMS Specification, I don’t know how to
>> implement SOAP fault for it.
>>
>> I use the org.apache.cxf.interceptor.Fault to record the Fault
>> information. For example, I create a Fault instance for SOAP fault
>> subcode contentTypeMismatch
>> (http://www.w3.org/TR/2008/WD-soapjms-20080723/#binding-faults). If I
>> check the fault the cxf-rt-transports-jms module, I don’t know how to
>> deal with the fault which is checked out.
>>
>> If I added an Interceptor for JMS transport, I can use the interceptor
>> to deal with the fault. Is It right?
>>
>> If it is Ok, how is the interceptor added to the interceptors according
>> to whether the jms transport is used or not?
>>
>> Are there any materials for interceptors, phases, and phase order?
>>
>> Thank you very much!
>>
>> Best regards,
>>
>> Liu
>>
>>
>>     
>
>
>   


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message