Comments on: Using different data types between Java and WCF

By: Mike R

Mike R — Fri, 23 Oct 2009 02:46:33 +0000

One thing you also have to remember is that XMLGregorianCalendar and java.util.Calendar differ in the numeric value they use for January (1 and 0 respectively). The conversion example between the calendars above needs to be changed to reflect this difference.

By: An Phu

An Phu — Wed, 17 Jun 2009 06:23:53 +0000

Have you tried setting EmitDefaultValue=false for the DataMember attribute?

By: Kevin Gao

Kevin Gao — Wed, 03 Jun 2009 05:16:06 +0000

Charlie,

We did run across the same issue in our SCM Anywhere.

You can use the methods of JAXBElement to get and set string values. If you are not comfortable with JAXBElement, you can try avoiding “IsRequired = false” in your DataMember definition by providing default values in your function calls.

Thanks,

Kevin

By: Charlie

Charlie — Wed, 13 May 2009 21:22:36 +0000

Great series of articles on WCF and Java interoperability. This subject is not well addressed anywhere. We are also using a WCF server and were testing out a Java client. We ran into some issues with a string DataMember that is defined in our WCF with “IsRequired = false”. This produced an xsd element with minOccurs=”0″ and nillable=”true”. This caused our Java client to want a JAXBElement instead of just a string.

I was wondering if you ran across this with your system. It would be nice if there was a way to omit the nillable=true in the generated xsd. I have not found any DataMemberAttributes that would result in this.

I am looking forward to more of your articles in this series.

Thanks,
Charlie