jQuery in Action, 2nd edition*
The moose likes Web Services and the fly likes Should I use xsd:gDay, xsd:gMonth, xsd:gYear OR just simple xsd:string Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "Should I use xsd:gDay, xsd:gMonth, xsd:gYear OR just simple xsd:string" Watch "Should I use xsd:gDay, xsd:gMonth, xsd:gYear OR just simple xsd:string" New topic
Author

Should I use xsd:gDay, xsd:gMonth, xsd:gYear OR just simple xsd:string

grace smith
Greenhorn

Joined: Jun 14, 2005
Posts: 23
hello,

I have some elements need to define for the day, month, year. In the WSDL, if I define the day as
<element name="dobDay" nillable="true" type="xsd:gDay"/>
then the soap binding will bind it to vendor specific Java Object - I am using websphere 5.1, so it mapped to com.ibm.ws.webservices.engine.types.Day type in the SEI function parameter.

I am wondering if my client is not using websphere, then using this WSDL, they could generate a different kind soap binding object for the xsd:gDay and does not match my service SEI. and then could couse the webservice access failed.

what should I do? avoid to use the xsd:gDay type and directly define it as
xsd:string and restrict it to the right format and also define application exception fault for the format validation?

can someone help me?
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Should I use xsd:gDay, xsd:gMonth, xsd:gYear OR just simple xsd:string