Databases
StackOverflow2013
Postsdbo
PO.NET web service reference generated classes not working with dateTime type
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO.NET web service reference generated classes not working with dateTime type
    primarykey
    data
    text
    <p>I've written a JAX-WS webservice in Java by generating a WSDL and classes from an XML schema.</p> <p>I am adding the service as a web reference in visual studio, to use with a C#.NET client application.</p> <p>The original XML schema uses a couple of date/time types: xs:date and xs:dateTime for some of the elements.</p> <p>My problem is that my 'dateTime' type is not working correctly. It is converted to a .NET DateTime object (correctly) in the generated classes (produced by XMLSerializer in Visual Studio 2010), and then I can create my own DateTime object and set the DateTime on one of these classes. However when sending the request back to the server, the client application is sending a null value instead of the DateTime object I set it to. So I guess it is not serializing correctly.</p> <p>I do not have the same problem with the 'date' type, which serializes/deserializes fine.</p> <p>I noticed something which could be the problem, but not sure:</p> <p>The dateTime object in the generated class looks like this: [System.Xml.Serialization.XmlElementAttribute(Order=10)] public System.DateTime MyDateTime { ... }</p> <p>whereas the date object in the generated class looks like this: [System.Xml.Serialization.XmlElementAttribute(DataType="date", Order=12)] public System.DateTime MyDate { ... }</p> <p>So, there is some additional info in the date object - DataType="date", but there is no DateType for the dateTime object. Could this be the problem? If so, why is it not generating the classes correctly?</p> <p>Thanks for any help</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKirk Broadhurst
    1. USJosh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PO.NET web service reference generated classes not working with dateTime type
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO.NET web service reference generated classes not working with dateTime type
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO.NET web service reference generated classes not working with dateTime type
      1. USbart
      1. VTBountyStart
    1. CONote: the dateTime problem is only a one-way thing. The problem occurs when the client (.NET) application sends a request object with a dateTime element to the server, and the server receives a null value. The other way seems to be fine (if the server sends a response object with a dateTime element, the client receives the response with the DateTime object with the correct date/time info)
      singulars
      1. PO.NET web service reference generated classes not working with dateTime type
      1. USJosh
    2. COPlease make absolutely 100% sure that you are actually setting a valid DateTime VALUE into the request. Next, please validate your outgoing request to the server by running Fiddler on your client system and checking the request. Please come back with your findings.
      singulars
      1. PO.NET web service reference generated classes not working with dateTime type
      1. USkroonwijk
    3. COI had similar problem. In my case dateTime member was skipped in xml that was sent to the server. It was connected with the fact that wsdl contained minOccurs="0". As a result Visual's generated client contains flags that this field is 'specified'. I must have added: fieldNameSpedified = true; for each such field. It might be also your case.
      singulars
      1. PO.NET web service reference generated classes not working with dateTime type
      1. USbart
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload