You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Daniel Dienhardt <d....@ergomedia.de> on 2007/08/15 18:33:18 UTC
Problems consuming rpc literal service
Hi all,
I have a very strange problem consuming a rpc/literal http soap service.
With version 2.0-incubator I got some complex object, but it had no
content. Maybe this is similar to thread
http://www.nabble.com/WS-client-returning-uninitialized-objects-tf4144602.html#a11788382
Today I tried out 2.0.1-incubator and I got the following exception:
----snip
15.08.2007 17:30:53 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
INFO: Interceptor has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: UNKNOWN_RPC_LIT_PART
---snap
I recorded the Response and built a test. (See the Attachemnt) maybe
someone can help.
if you change the version inside the pom to 2.0-incubator, you'll got no
Message but an empty object.
As a workaround I tried to consume this service with axis 1.4 -- and it
worked fine, but I have trouble using axis and cxf together. So I really
would like to consume this service with cxf.
Thanks in advance for any help
--
Daniel Dienhardt
Re: Problems consuming rpc literal service
Posted by Daniel Dienhardt <d....@ergomedia.de>.
Thanks for your help,
I tried out the trunk, but my test still doesn't work. I built a
workaround using axis 1.4 as client (axis 2.0 didn't do the job) and
providing a service with cxf.
Daniel Kulp schrieb:
> Daniel,
>
> On Friday 17 August 2007, Daniel Dienhardt wrote:
>> afaik Axis 1.3 is used to produce this service, and I managed to
>> consume it with this library. But I will send your reply to the
>> provider of this ws. Can you recommend some tool to check the
>> compliance of SOAP-Messages?
>
> No idea on that one. I think the WS-I working group created some, but
> I really don't know.
>
> I did just commit some changes to the RCPInInterceptor to make it relax a
> little bit on reading and match on the local part instead of the whole
> qname. That MAY allow it to work for you. You'd have to grab trunk
> from SVN and build it, but I'll try and get a new snapshot up sometime
> over the weekend.
>
>
> Dan
>
>
>
>> Daniel
>>
>> Daniel Kulp schrieb:
>>> Daniel,
>>>
>>> That SOAP message is NOT a valid message for RPC/Literal according
>>> to the WSI Basic Profile. Specifically:
>>>
>>> R2735 A MESSAGE described with an rpc-literal binding MUST place
>>> the part accessor elements for parameters and return value in no
>>> namespace.
>>>
>>>
>>> In the message below, the "invokeReturn" element is in the
>>> http://soa.centerra.de/ns/is/kbform/ namespace which is not correct.
>>>
>>>
>>> Thus, this is a bug in whatever is producing this message.
>>>
>>> Dan
>>>
>>> On Thursday 16 August 2007, Daniel Dienhardt wrote:
>>>> Hi,
>>>>
>>>> I did a little more research and figured out how the soap respone
>>>> has to be modified , so that the test works, and the object is
>>>> correctly unmarshalled. To me it seems like a Bug inside the
>>>> RPCInInterceptor
>>>>
>>>> This is the response that causes the exception:
>>>>
>>>> <soapenv:Envelope
>>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>>>> <soapenv:Body>
>>>> <invokeResponse xmlns="http://soa.centerra.de/ns/is/kbform/">
>>>> <invokeReturn>
>>>> <faultCode>-101</faultCode>
>>>> <faultString>
>>>> Error in EDPEditor: Kann Button nicht drücken
>>>> bstart(0); nested exception is
>>>> de.abas.ceks.jedp.CantChangeFieldValException: Kann
>>>> Button nicht drücken bstart(0)
>>>> </faultString>
>>>> <headOutput xsi:nil="true" />
>>>> <tableOutput xsi:nil="true" />
>>>> </invokeReturn>
>>>> </invokeResponse>
>>>> </soapenv:Body>
>>>> </soapenv:Envelope>
>>>>
>>>> If you modify the response to:
>>>>
>>>> ...
>>>> <nsi:invokeResponse
>>>> xmlns:nsi="http://soa.centerra.de/ns/is/kbform/"> ...
>>>> <nsi:invokeResponse>
>>>> ...
>>>>
>>>> The test works fine, and the response is correctly unmarshalled.
>>>>
>>>> Does anyone has a clue, how to fix this, or knows some workaround?
>>>>
>>>> Daniel Dienhardt schrieb:
>>>>> Hi all,
>>>>>
>>>>> I have a very strange problem consuming a rpc/literal http soap
>>>>> service.
>>>>>
>>>>> With version 2.0-incubator I got some complex object, but it had
>>>>> no content. Maybe this is similar to thread
>>>>>
>>>>> http://www.nabble.com/WS-client-returning-uninitialized-objects-tf
>>>>> 41 44602.html#a11788382
>>>>>
>>>>> Today I tried out 2.0.1-incubator and I got the following
>>>>> exception:
>>>>>
>>>>> ----snip
>>>>> 15.08.2007 17:30:53 org.apache.cxf.phase.PhaseInterceptorChain
>>>>> doIntercept INFO: Interceptor has thrown exception, unwinding now
>>>>> org.apache.cxf.interceptor.Fault: UNKNOWN_RPC_LIT_PART
>>>>> ---snap
>>>>>
>>>>> I recorded the Response and built a test. (See the Attachemnt)
>>>>> maybe someone can help.
>>>>>
>>>>> if you change the version inside the pom to 2.0-incubator, you'll
>>>>> got no Message but an empty object.
>>>>>
>>>>> As a workaround I tried to consume this service with axis 1.4 --
>>>>> and it worked fine, but I have trouble using axis and cxf
>>>>> together. So I really would like to consume this service with cxf.
>>>>>
>>>>>
>>>>> Thanks in advance for any help
>
>
>
RE: Problems consuming rpc literal service
Posted by Benson Margulies <bi...@basistech.com>.
I use soapscope, but it's not free.
> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: Friday, August 17, 2007 4:49 PM
> To: cxf-user@incubator.apache.org
> Cc: Daniel Dienhardt
> Subject: Re: Problems consuming rpc literal service
>
>
> Daniel,
>
> On Friday 17 August 2007, Daniel Dienhardt wrote:
> > afaik Axis 1.3 is used to produce this service, and I managed to
> > consume it with this library. But I will send your reply to the
> > provider of this ws. Can you recommend some tool to check the
> > compliance of SOAP-Messages?
>
> No idea on that one. I think the WS-I working group created some,
but
> I really don't know.
>
> I did just commit some changes to the RCPInInterceptor to make it
relax a
> little bit on reading and match on the local part instead of the whole
> qname. That MAY allow it to work for you. You'd have to grab trunk
> from SVN and build it, but I'll try and get a new snapshot up sometime
> over the weekend.
>
>
> Dan
>
>
>
> >
> > Daniel
> >
> > Daniel Kulp schrieb:
> > > Daniel,
> > >
> > > That SOAP message is NOT a valid message for RPC/Literal according
> > > to the WSI Basic Profile. Specifically:
> > >
> > > R2735 A MESSAGE described with an rpc-literal binding MUST place
> > > the part accessor elements for parameters and return value in no
> > > namespace.
> > >
> > >
> > > In the message below, the "invokeReturn" element is in the
> > > http://soa.centerra.de/ns/is/kbform/ namespace which is not
correct.
> > >
> > >
> > > Thus, this is a bug in whatever is producing this message.
> > >
> > > Dan
> > >
> > > On Thursday 16 August 2007, Daniel Dienhardt wrote:
> > >> Hi,
> > >>
> > >> I did a little more research and figured out how the soap respone
> > >> has to be modified , so that the test works, and the object is
> > >> correctly unmarshalled. To me it seems like a Bug inside the
> > >> RPCInInterceptor
> > >>
> > >> This is the response that causes the exception:
> > >>
> > >> <soapenv:Envelope
> > >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> > >> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> > >> <soapenv:Body>
> > >> <invokeResponse
xmlns="http://soa.centerra.de/ns/is/kbform/">
> > >> <invokeReturn>
> > >> <faultCode>-101</faultCode>
> > >> <faultString>
> > >> Error in EDPEditor: Kann Button
nicht
> drücken
> > >> bstart(0); nested exception is
> > >>
> de.abas.ceks.jedp.CantChangeFieldValException: Kann
> > >> Button nicht drücken
bstart(0)
> > >> </faultString>
> > >> <headOutput xsi:nil="true" />
> > >> <tableOutput xsi:nil="true" />
> > >> </invokeReturn>
> > >> </invokeResponse>
> > >> </soapenv:Body>
> > >> </soapenv:Envelope>
> > >>
> > >> If you modify the response to:
> > >>
> > >> ...
> > >> <nsi:invokeResponse
> > >> xmlns:nsi="http://soa.centerra.de/ns/is/kbform/"> ...
> > >> <nsi:invokeResponse>
> > >> ...
> > >>
> > >> The test works fine, and the response is correctly unmarshalled.
> > >>
> > >> Does anyone has a clue, how to fix this, or knows some
workaround?
> > >>
> > >> Daniel Dienhardt schrieb:
> > >>> Hi all,
> > >>>
> > >>> I have a very strange problem consuming a rpc/literal http soap
> > >>> service.
> > >>>
> > >>> With version 2.0-incubator I got some complex object, but it had
> > >>> no content. Maybe this is similar to thread
> > >>>
> > >>>
http://www.nabble.com/WS-client-returning-uninitialized-objects-tf
> > >>>41 44602.html#a11788382
> > >>>
> > >>> Today I tried out 2.0.1-incubator and I got the following
> > >>> exception:
> > >>>
> > >>> ----snip
> > >>> 15.08.2007 17:30:53 org.apache.cxf.phase.PhaseInterceptorChain
> > >>> doIntercept INFO: Interceptor has thrown exception, unwinding
now
> > >>> org.apache.cxf.interceptor.Fault: UNKNOWN_RPC_LIT_PART
> > >>> ---snap
> > >>>
> > >>> I recorded the Response and built a test. (See the Attachemnt)
> > >>> maybe someone can help.
> > >>>
> > >>> if you change the version inside the pom to 2.0-incubator,
you'll
> > >>> got no Message but an empty object.
> > >>>
> > >>> As a workaround I tried to consume this service with axis 1.4 --
> > >>> and it worked fine, but I have trouble using axis and cxf
> > >>> together. So I really would like to consume this service with
cxf.
> > >>>
> > >>>
> > >>> Thanks in advance for any help
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194
> daniel.kulp@iona.com
> http://www.dankulp.com/blog
Re: Problems consuming rpc literal service
Posted by Daniel Kulp <dk...@apache.org>.
Daniel,
On Friday 17 August 2007, Daniel Dienhardt wrote:
> afaik Axis 1.3 is used to produce this service, and I managed to
> consume it with this library. But I will send your reply to the
> provider of this ws. Can you recommend some tool to check the
> compliance of SOAP-Messages?
No idea on that one. I think the WS-I working group created some, but
I really don't know.
I did just commit some changes to the RCPInInterceptor to make it relax a
little bit on reading and match on the local part instead of the whole
qname. That MAY allow it to work for you. You'd have to grab trunk
from SVN and build it, but I'll try and get a new snapshot up sometime
over the weekend.
Dan
>
> Daniel
>
> Daniel Kulp schrieb:
> > Daniel,
> >
> > That SOAP message is NOT a valid message for RPC/Literal according
> > to the WSI Basic Profile. Specifically:
> >
> > R2735 A MESSAGE described with an rpc-literal binding MUST place
> > the part accessor elements for parameters and return value in no
> > namespace.
> >
> >
> > In the message below, the "invokeReturn" element is in the
> > http://soa.centerra.de/ns/is/kbform/ namespace which is not correct.
> >
> >
> > Thus, this is a bug in whatever is producing this message.
> >
> > Dan
> >
> > On Thursday 16 August 2007, Daniel Dienhardt wrote:
> >> Hi,
> >>
> >> I did a little more research and figured out how the soap respone
> >> has to be modified , so that the test works, and the object is
> >> correctly unmarshalled. To me it seems like a Bug inside the
> >> RPCInInterceptor
> >>
> >> This is the response that causes the exception:
> >>
> >> <soapenv:Envelope
> >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> >> <soapenv:Body>
> >> <invokeResponse xmlns="http://soa.centerra.de/ns/is/kbform/">
> >> <invokeReturn>
> >> <faultCode>-101</faultCode>
> >> <faultString>
> >> Error in EDPEditor: Kann Button nicht drücken
> >> bstart(0); nested exception is
> >> de.abas.ceks.jedp.CantChangeFieldValException: Kann
> >> Button nicht drücken bstart(0)
> >> </faultString>
> >> <headOutput xsi:nil="true" />
> >> <tableOutput xsi:nil="true" />
> >> </invokeReturn>
> >> </invokeResponse>
> >> </soapenv:Body>
> >> </soapenv:Envelope>
> >>
> >> If you modify the response to:
> >>
> >> ...
> >> <nsi:invokeResponse
> >> xmlns:nsi="http://soa.centerra.de/ns/is/kbform/"> ...
> >> <nsi:invokeResponse>
> >> ...
> >>
> >> The test works fine, and the response is correctly unmarshalled.
> >>
> >> Does anyone has a clue, how to fix this, or knows some workaround?
> >>
> >> Daniel Dienhardt schrieb:
> >>> Hi all,
> >>>
> >>> I have a very strange problem consuming a rpc/literal http soap
> >>> service.
> >>>
> >>> With version 2.0-incubator I got some complex object, but it had
> >>> no content. Maybe this is similar to thread
> >>>
> >>> http://www.nabble.com/WS-client-returning-uninitialized-objects-tf
> >>>41 44602.html#a11788382
> >>>
> >>> Today I tried out 2.0.1-incubator and I got the following
> >>> exception:
> >>>
> >>> ----snip
> >>> 15.08.2007 17:30:53 org.apache.cxf.phase.PhaseInterceptorChain
> >>> doIntercept INFO: Interceptor has thrown exception, unwinding now
> >>> org.apache.cxf.interceptor.Fault: UNKNOWN_RPC_LIT_PART
> >>> ---snap
> >>>
> >>> I recorded the Response and built a test. (See the Attachemnt)
> >>> maybe someone can help.
> >>>
> >>> if you change the version inside the pom to 2.0-incubator, you'll
> >>> got no Message but an empty object.
> >>>
> >>> As a workaround I tried to consume this service with axis 1.4 --
> >>> and it worked fine, but I have trouble using axis and cxf
> >>> together. So I really would like to consume this service with cxf.
> >>>
> >>>
> >>> Thanks in advance for any help
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog
Re: Problems consuming rpc literal service
Posted by Daniel Dienhardt <d....@ergomedia.de>.
Thanks for your help,
afaik Axis 1.3 is used to produce this service, and I managed to consume
it with this library. But I will send your reply to the provider of this
ws. Can you recommend some tool to check the compliance of SOAP-Messages?
Daniel
Daniel Kulp schrieb:
> Daniel,
>
> That SOAP message is NOT a valid message for RPC/Literal according to the
> WSI Basic Profile. Specifically:
>
> R2735 A MESSAGE described with an rpc-literal binding MUST place the
> part accessor elements for parameters and return value in no namespace.
>
>
> In the message below, the "invokeReturn" element is in the
> http://soa.centerra.de/ns/is/kbform/ namespace which is not correct.
>
>
> Thus, this is a bug in whatever is producing this message.
>
> Dan
>
>
> On Thursday 16 August 2007, Daniel Dienhardt wrote:
>> Hi,
>>
>> I did a little more research and figured out how the soap respone has
>> to be modified , so that the test works, and the object is correctly
>> unmarshalled. To me it seems like a Bug inside the RPCInInterceptor
>>
>> This is the response that causes the exception:
>>
>> <soapenv:Envelope
>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>> <soapenv:Body>
>> <invokeResponse xmlns="http://soa.centerra.de/ns/is/kbform/">
>> <invokeReturn>
>> <faultCode>-101</faultCode>
>> <faultString>
>> Error in EDPEditor: Kann Button nicht drücken
>> bstart(0); nested exception is
>> de.abas.ceks.jedp.CantChangeFieldValException: Kann
>> Button nicht drücken bstart(0)
>> </faultString>
>> <headOutput xsi:nil="true" />
>> <tableOutput xsi:nil="true" />
>> </invokeReturn>
>> </invokeResponse>
>> </soapenv:Body>
>> </soapenv:Envelope>
>>
>> If you modify the response to:
>>
>> ...
>> <nsi:invokeResponse xmlns:nsi="http://soa.centerra.de/ns/is/kbform/">
>> ...
>> <nsi:invokeResponse>
>> ...
>>
>> The test works fine, and the response is correctly unmarshalled.
>>
>> Does anyone has a clue, how to fix this, or knows some workaround?
>>
>> Daniel Dienhardt schrieb:
>>> Hi all,
>>>
>>> I have a very strange problem consuming a rpc/literal http soap
>>> service.
>>>
>>> With version 2.0-incubator I got some complex object, but it had no
>>> content. Maybe this is similar to thread
>>>
>>> http://www.nabble.com/WS-client-returning-uninitialized-objects-tf41
>>> 44602.html#a11788382
>>>
>>> Today I tried out 2.0.1-incubator and I got the following exception:
>>>
>>> ----snip
>>> 15.08.2007 17:30:53 org.apache.cxf.phase.PhaseInterceptorChain
>>> doIntercept INFO: Interceptor has thrown exception, unwinding now
>>> org.apache.cxf.interceptor.Fault: UNKNOWN_RPC_LIT_PART
>>> ---snap
>>>
>>> I recorded the Response and built a test. (See the Attachemnt) maybe
>>> someone can help.
>>>
>>> if you change the version inside the pom to 2.0-incubator, you'll
>>> got no Message but an empty object.
>>>
>>> As a workaround I tried to consume this service with axis 1.4 -- and
>>> it worked fine, but I have trouble using axis and cxf together. So I
>>> really would like to consume this service with cxf.
>>>
>>>
>>> Thanks in advance for any help
>
>
>
Re: Problems consuming rpc literal service
Posted by Daniel Kulp <dk...@apache.org>.
Daniel,
That SOAP message is NOT a valid message for RPC/Literal according to the
WSI Basic Profile. Specifically:
R2735 A MESSAGE described with an rpc-literal binding MUST place the
part accessor elements for parameters and return value in no namespace.
In the message below, the "invokeReturn" element is in the
http://soa.centerra.de/ns/is/kbform/ namespace which is not correct.
Thus, this is a bug in whatever is producing this message.
Dan
On Thursday 16 August 2007, Daniel Dienhardt wrote:
> Hi,
>
> I did a little more research and figured out how the soap respone has
> to be modified , so that the test works, and the object is correctly
> unmarshalled. To me it seems like a Bug inside the RPCInInterceptor
>
> This is the response that causes the exception:
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <invokeResponse xmlns="http://soa.centerra.de/ns/is/kbform/">
> <invokeReturn>
> <faultCode>-101</faultCode>
> <faultString>
> Error in EDPEditor: Kann Button nicht drücken
> bstart(0); nested exception is
> de.abas.ceks.jedp.CantChangeFieldValException: Kann
> Button nicht drücken bstart(0)
> </faultString>
> <headOutput xsi:nil="true" />
> <tableOutput xsi:nil="true" />
> </invokeReturn>
> </invokeResponse>
> </soapenv:Body>
> </soapenv:Envelope>
>
> If you modify the response to:
>
> ...
> <nsi:invokeResponse xmlns:nsi="http://soa.centerra.de/ns/is/kbform/">
> ...
> <nsi:invokeResponse>
> ...
>
> The test works fine, and the response is correctly unmarshalled.
>
> Does anyone has a clue, how to fix this, or knows some workaround?
>
> Daniel Dienhardt schrieb:
> > Hi all,
> >
> > I have a very strange problem consuming a rpc/literal http soap
> > service.
> >
> > With version 2.0-incubator I got some complex object, but it had no
> > content. Maybe this is similar to thread
> >
> > http://www.nabble.com/WS-client-returning-uninitialized-objects-tf41
> >44602.html#a11788382
> >
> > Today I tried out 2.0.1-incubator and I got the following exception:
> >
> > ----snip
> > 15.08.2007 17:30:53 org.apache.cxf.phase.PhaseInterceptorChain
> > doIntercept INFO: Interceptor has thrown exception, unwinding now
> > org.apache.cxf.interceptor.Fault: UNKNOWN_RPC_LIT_PART
> > ---snap
> >
> > I recorded the Response and built a test. (See the Attachemnt) maybe
> > someone can help.
> >
> > if you change the version inside the pom to 2.0-incubator, you'll
> > got no Message but an empty object.
> >
> > As a workaround I tried to consume this service with axis 1.4 -- and
> > it worked fine, but I have trouble using axis and cxf together. So I
> > really would like to consume this service with cxf.
> >
> >
> > Thanks in advance for any help
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog
Re: Problems consuming rpc literal service
Posted by Daniel Dienhardt <d....@ergomedia.de>.
Hi,
I did a little more research and figured out how the soap respone has to
be modified , so that the test works, and the object is correctly
unmarshalled. To me it seems like a Bug inside the RPCInInterceptor
This is the response that causes the exception:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<invokeResponse xmlns="http://soa.centerra.de/ns/is/kbform/">
<invokeReturn>
<faultCode>-101</faultCode>
<faultString>
Error in EDPEditor: Kann Button nicht drücken
bstart(0); nested exception is
de.abas.ceks.jedp.CantChangeFieldValException: Kann
Button nicht drücken bstart(0)
</faultString>
<headOutput xsi:nil="true" />
<tableOutput xsi:nil="true" />
</invokeReturn>
</invokeResponse>
</soapenv:Body>
</soapenv:Envelope>
If you modify the response to:
...
<nsi:invokeResponse xmlns:nsi="http://soa.centerra.de/ns/is/kbform/">
...
<nsi:invokeResponse>
...
The test works fine, and the response is correctly unmarshalled.
Does anyone has a clue, how to fix this, or knows some workaround?
Daniel Dienhardt schrieb:
> Hi all,
>
> I have a very strange problem consuming a rpc/literal http soap service.
>
> With version 2.0-incubator I got some complex object, but it had no
> content. Maybe this is similar to thread
>
> http://www.nabble.com/WS-client-returning-uninitialized-objects-tf4144602.html#a11788382
>
> Today I tried out 2.0.1-incubator and I got the following exception:
>
> ----snip
> 15.08.2007 17:30:53 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
> INFO: Interceptor has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: UNKNOWN_RPC_LIT_PART
> ---snap
>
> I recorded the Response and built a test. (See the Attachemnt) maybe
> someone can help.
>
> if you change the version inside the pom to 2.0-incubator, you'll got no
> Message but an empty object.
>
> As a workaround I tried to consume this service with axis 1.4 -- and it
> worked fine, but I have trouble using axis and cxf together. So I really
> would like to consume this service with cxf.
>
>
> Thanks in advance for any help
>
--
Daniel Dienhardt