Hi,
Forward this mail to the dev mail list.
liucong wrote:
> Hi,
> I have added a simple interceptor in the SOAP binding. If the
> transport uri is http://www.w3.org/2008/07/soap/bindings/JMS/, the jms
> interceptor will be added. But I have some question for that:
> 1. I feel a little wei
On Tue June 16 2009 10:12:54 pm liucong wrote:
> Hi,
> I have added a simple interceptor in the SOAP binding. If the
> transport uri is http://www.w3.org/2008/07/soap/bindings/JMS/, the jms
> interceptor will be added. But I have some question for that:
> 1. I feel a little weird to add a t
Hi,
I have added a simple interceptor in the SOAP binding. If the
transport uri is http://www.w3.org/2008/07/soap/bindings/JMS/, the jms
interceptor will be added. But I have some question for that:
1. I feel a little weird to add a transport-related interceptor here.
2. Program Proble
On Wed June 10 2009 4:38:37 am liucong wrote:
> So, the JMS transport just copy JMS message properties to somewhere(For
> example, Message.PROTOCOL_HEADERS map). Then the SOAP binding add some
> extra interceptors (How to add these interceptors?) to deal with these
> properties (check the propertie
So, the JMS transport just copy JMS message properties to somewhere(For
example, Message.PROTOCOL_HEADERS map). Then the SOAP binding add some
extra interceptors (How to add these interceptors?) to deal with these
properties (check the properties, throw some SOAP Faults, and so on).
Does it wo
Ideally, to me, this type of fault mapping needs to be in the SOAP binding,
not the JMS transport.The JMS transport needs to be somewhat independent
of soap so that it's usable for things like XML over JMS and possibly even
some resty things.
Basically, the SOAP binding should examine it's
I just want to find a way without any configuration, and soap jms
transport can use it out of box.
Willem
liucong wrote:
> 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
>>
Hi ,
You can leverage the Features[1] to install the interceptors which you
need for soap/jms, and you can find some basic CXF Architecture document
[2] here.
[1]http://cwiki.apache.org/confluence/display/CXF20DOC/Features
[2]http://cwiki.apache.org/CXF20DOC/cxf-architecture.html
Willem
liucong
Hi,
Willem Jiang Writes:
> 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
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 , yo
Hi,
In the cxf-rt-transports-jms module,
org.apahce.cxf.transport.jms.JMSDestination.onMessage receive the JMS
message and create a CXF message.
If there is something wrong with the JMS message. I can't throw the
Fault here.
I should throw the Fault in the process of Message processing.
how to deal
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 loa
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-so
13 matches
Mail list logo