Comments on: Connecting JBoss CXF Web Service with a WCF Client

By: robob

robob — Sat, 25 Apr 2009 08:07:35 +0000

The problem is not related to the arrays but a mistake in the deserialization of the SOAP message for the missing attribute in the ‘System.Xml.Serialization.XmlArrayAttribute’.

I have to say that WCF mapping of a WSDL exported from JBossWS is not very good and probably we are pioneers in this field. What do you think about the error? Have you had the time to see the post I updateed?

By: robob

robob — Thu, 23 Apr 2009 21:19:00 +0000

Here is the post in the MSDN Forum where I explain the problem with all the details. The exception is very strange and it seems depending only from the client side (I think).

http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/0a48d50d-64d1-43b1-be05-d1b15643223f/

I think to do an example with a sample WS client and WS in JBoss where the problem is replicated and sharing it with everbody.

The problem I have is too strange! And I’m beginning to think it is a my mistake.

I have to admit that I am a newbie in WCF and JBOSSWS too

By: bryankearney

bryankearney — Wed, 22 Apr 2009 17:00:56 +0000

I did with an array of objects. I ended up having to create a concrete subclass to hold the array of objects. I would dig into the JAXB stuff to see if there are any annotations which improve the marshalling.

By: robob

robob — Wed, 22 Apr 2009 15:56:15 +0000

Have you ever had problems with webmethod returning a string array (string[]) or int array (int[])?

I have just implemented a WCF client to a JBossWS and only the webmethods returning the string[] and int[] don’t work. The exception in C# is an “ArgumentException”.

Very strange because another webmethod return my bean array and all works fine!