You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Kurt <no...@hestonsystems.com> on 2010/11/23 06:08:05 UTC
upgrade from 2.2.6 to 2.2.11 breaks .NET client
I was unable to find a post regarding the issue, so I thought I'd give a
heads-up.
I recently upgraded from 2.2.6 to 2.2.11 and my C# client stopped
working. Objects received from my JAXP service weren't being
de-serialized anymore. The XML looked fine, but the .NET libs were
choking on something. I could send data but any object I tried to fetch
returned null on the C# side of things. Reverting to 2.2.6 fixed the
problem.
Hope this helps someone.
Re: upgrade from 2.2.6 to 2.2.11 breaks .NET client
Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday 24 November 2010 2:41:23 am Kurt wrote:
> Daniel,
>
> The debug facilities Redmond provides with C# Express leave something to
> be desired. Is there a quick way to get a CXF client to dump the XML
> source to file?
You can just add -Dorg.apache.cxf.logging.enabled=true to the command line jvm
args to turn on basic logging. It would log to the console by default, but
that may be enough.
Dan
>
> On 11/23/2010 05:20 AM, Daniel Kulp wrote:
> > On Tuesday 23 November 2010 12:08:05 am Kurt wrote:
> >> I was unable to find a post regarding the issue, so I thought I'd give a
> >> heads-up.
> >>
> >> I recently upgraded from 2.2.6 to 2.2.11 and my C# client stopped
> >> working. Objects received from my JAXP service weren't being
> >> de-serialized anymore. The XML looked fine, but the .NET libs were
> >> choking on something. I could send data but any object I tried to fetch
> >> returned null on the C# side of things. Reverting to 2.2.6 fixed the
> >> problem.
> >>
> >> Hope this helps someone.
> >
> > Not really. Is there any way you can capture the soap messages for both
> > 2.2.6 and 2.2.11 and do a full compare. Without at least that, I'm not
> > sure even where to start looking as to what would be the cause.
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: upgrade from 2.2.6 to 2.2.11 breaks .NET client
Posted by Kurt Heston <kh...@hestonsystems.com>.
JMeter is probably a good candidate then. I'll give it a shot.
On 11/23/2010 11:50 PM, Freeman Fang wrote:
> Hi,
> Just a quick note, you can put some tool like tcpmon between your cxf
> client and C# server, from which you can dump the on-wire message.
>
> Freeman
> On 2010-11-24, at 下午3:41, Kurt wrote:
>
>> Daniel,
>>
>> The debug facilities Redmond provides with C# Express leave something
>> to be desired. Is there a quick way to get a CXF client to dump the
>> XML source to file?
>>
>> On 11/23/2010 05:20 AM, Daniel Kulp wrote:
>>> On Tuesday 23 November 2010 12:08:05 am Kurt wrote:
>>>
>>>> I was unable to find a post regarding the issue, so I thought I'd
>>>> give a
>>>> heads-up.
>>>>
>>>> I recently upgraded from 2.2.6 to 2.2.11 and my C# client stopped
>>>> working. Objects received from my JAXP service weren't being
>>>> de-serialized anymore. The XML looked fine, but the .NET libs were
>>>> choking on something. I could send data but any object I tried to
>>>> fetch
>>>> returned null on the C# side of things. Reverting to 2.2.6 fixed the
>>>> problem.
>>>>
>>>> Hope this helps someone.
>>>>
>>> Not really. Is there any way you can capture the soap messages for
>>> both
>>> 2.2.6 and 2.2.11 and do a full compare. Without at least that, I'm
>>> not sure
>>> even where to start looking as to what would be the cause.
>>>
>>>
>
>
Re: upgrade from 2.2.6 to 2.2.11 breaks .NET client
Posted by Kurt <no...@hestonsystems.com>.
JMeter is probably a good candidate then. I'll give it a shot.
On 11/23/2010 11:50 PM, Freeman Fang wrote:
> Hi,
> Just a quick note, you can put some tool like tcpmon between your cxf
> client and C# server, from which you can dump the on-wire message.
>
> Freeman
> On 2010-11-24, at 下午3:41, Kurt wrote:
>
>> Daniel,
>>
>> The debug facilities Redmond provides with C# Express leave something
>> to be desired. Is there a quick way to get a CXF client to dump the
>> XML source to file?
>>
>> On 11/23/2010 05:20 AM, Daniel Kulp wrote:
>>> On Tuesday 23 November 2010 12:08:05 am Kurt wrote:
>>>
>>>> I was unable to find a post regarding the issue, so I thought I'd
>>>> give a
>>>> heads-up.
>>>>
>>>> I recently upgraded from 2.2.6 to 2.2.11 and my C# client stopped
>>>> working. Objects received from my JAXP service weren't being
>>>> de-serialized anymore. The XML looked fine, but the .NET libs were
>>>> choking on something. I could send data but any object I tried to
>>>> fetch
>>>> returned null on the C# side of things. Reverting to 2.2.6 fixed the
>>>> problem.
>>>>
>>>> Hope this helps someone.
>>>>
>>> Not really. Is there any way you can capture the soap messages for
>>> both
>>> 2.2.6 and 2.2.11 and do a full compare. Without at least that, I'm
>>> not sure
>>> even where to start looking as to what would be the cause.
>>>
>>>
>
>
Re: upgrade from 2.2.6 to 2.2.11 breaks .NET client
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
Just a quick note, you can put some tool like tcpmon between your cxf
client and C# server, from which you can dump the on-wire message.
Freeman
On 2010-11-24, at 下午3:41, Kurt wrote:
> Daniel,
>
> The debug facilities Redmond provides with C# Express leave
> something to be desired. Is there a quick way to get a CXF client
> to dump the XML source to file?
>
> On 11/23/2010 05:20 AM, Daniel Kulp wrote:
>> On Tuesday 23 November 2010 12:08:05 am Kurt wrote:
>>
>>> I was unable to find a post regarding the issue, so I thought I'd
>>> give a
>>> heads-up.
>>>
>>> I recently upgraded from 2.2.6 to 2.2.11 and my C# client stopped
>>> working. Objects received from my JAXP service weren't being
>>> de-serialized anymore. The XML looked fine, but the .NET libs were
>>> choking on something. I could send data but any object I tried to
>>> fetch
>>> returned null on the C# side of things. Reverting to 2.2.6 fixed
>>> the
>>> problem.
>>>
>>> Hope this helps someone.
>>>
>> Not really. Is there any way you can capture the soap messages
>> for both
>> 2.2.6 and 2.2.11 and do a full compare. Without at least that,
>> I'm not sure
>> even where to start looking as to what would be the cause.
>>
>>
--
Freeman Fang
------------------------
FuseSource: http://fusesource.com
blog: http://freemanfang.blogspot.com
twitter: http://twitter.com/freemanfang
Apache Servicemix:http://servicemix.apache.org
Apache Cxf: http://cxf.apache.org
Apache Karaf: http://karaf.apache.org
Apache Felix: http://felix.apache.org
Re: upgrade from 2.2.6 to 2.2.11 breaks .NET client
Posted by Kurt <no...@hestonsystems.com>.
Daniel,
The debug facilities Redmond provides with C# Express leave something to
be desired. Is there a quick way to get a CXF client to dump the XML
source to file?
On 11/23/2010 05:20 AM, Daniel Kulp wrote:
> On Tuesday 23 November 2010 12:08:05 am Kurt wrote:
>
>> I was unable to find a post regarding the issue, so I thought I'd give a
>> heads-up.
>>
>> I recently upgraded from 2.2.6 to 2.2.11 and my C# client stopped
>> working. Objects received from my JAXP service weren't being
>> de-serialized anymore. The XML looked fine, but the .NET libs were
>> choking on something. I could send data but any object I tried to fetch
>> returned null on the C# side of things. Reverting to 2.2.6 fixed the
>> problem.
>>
>> Hope this helps someone.
>>
> Not really. Is there any way you can capture the soap messages for both
> 2.2.6 and 2.2.11 and do a full compare. Without at least that, I'm not sure
> even where to start looking as to what would be the cause.
>
>
Re: upgrade from 2.2.6 to 2.2.11 breaks .NET client
Posted by Daniel Kulp <dk...@apache.org>.
On Tuesday 23 November 2010 12:08:05 am Kurt wrote:
> I was unable to find a post regarding the issue, so I thought I'd give a
> heads-up.
>
> I recently upgraded from 2.2.6 to 2.2.11 and my C# client stopped
> working. Objects received from my JAXP service weren't being
> de-serialized anymore. The XML looked fine, but the .NET libs were
> choking on something. I could send data but any object I tried to fetch
> returned null on the C# side of things. Reverting to 2.2.6 fixed the
> problem.
>
> Hope this helps someone.
Not really. Is there any way you can capture the soap messages for both
2.2.6 and 2.2.11 and do a full compare. Without at least that, I'm not sure
even where to start looking as to what would be the cause.
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog