This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
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?