> Whth .NET WS I have serialized an ADO.NET Recordset in an XML Stream like
> this:
[quoted text clipped - 30 lines]
>
> I have seen JAXB, but it wants two file: an XSD Schema and a XML file....
If that's what JAXB wants, then why not give it to JAXB?
Why would you expect Java or anything else to understand this XML format?
Does JAXB know about the 'urn:schemas-microsoft-com:rowset' namespace? If
not, then how will it be able to interpret an rs:data element?
You should think this through, starting with the WSDL file and its
associated schemas, and then, maybe finally deciding how to serialize your
ADO.NET Recordset. That's the final thing you should be doing, not the
first.
John
roboB - 24 Sep 2006 10:24 GMT
Ok, Jhon, pehaps I was not so very clear.
Some question more spicifically:
1) Why Does Microsoft persist an ADO.NET recordset in this mode if this is
not so very useful to deserialize in Java environment? WS are made to do
interoperability more accessible...
2) How Do you think it is more convenient to serialize and deserialize
ADO.NET recordset in Java?
Thanks to you
> > Whth .NET WS I have serialized an ADO.NET Recordset in an XML Stream like
> > this:
[quoted text clipped - 43 lines]
>
> John
John Saunders - 24 Sep 2006 19:10 GMT
> Ok, Jhon, pehaps I was not so very clear.
>
[quoted text clipped - 3 lines]
> not so very useful to deserialize in Java environment? WS are made to do
> interoperability more accessible...
Why would Java be an overwhelming consideration for Microsoft?
> 2) How Do you think it is more convenient to serialize and deserialize
> ADO.NET recordset in Java?
Why do you want Java or any other platform to have to understand what a
DataSet is? Pretend that DataSets don't exist and that you still have to
send the same data. Then separate the data to be sent from the platform
sending it.
John