• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

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

 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
 
I was born with webbed fish toes. This tiny ad is my only friend:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic