Deserialize Business Object

[Redowl]

Hi,

I am having an issue deserializing a business object from a SQL stored
procedure. I have created the class using the XSD tool and the resulting
XMLDATA schema but when I try to create the object I get an error message
<[Object] xmlns=''was not expected.

As the XML being returned is an XML fragment due to not having a single root
element I have previously got around this issue by adding another table to
the database which acts purely as the root element. However, I would like to
do this properly rather than this bodge.

Very grateful for any advice. I am using SQL 2000 and version 1.1 of the
framework.

[John Saunders]

"Redowl" <Re****@discussions.microsoft.comwrote in message
news:59**********************************@microsof t.com...

Hi,

I am having an issue deserializing a business object from a SQL stored
procedure. I have created the class using the XSD tool and the resulting
XMLDATA schema but when I try to create the object I get an error message
<[Object] xmlns=''was not expected.

As the XML being returned is an XML fragment due to not having a single
root
element I have previously got around this issue by adding another table to
the database which acts purely as the root element. However, I would like
to
do this properly rather than this bodge.

Very grateful for any advice. I am using SQL 2000 and version 1.1 of the
framework.

I'd need more detail from you to give a good answer. Therefore, here's a bad
answer:

Rather than add another table to the database, I'd suggest you add a root
node to your XML. Create a new XmlDocument, add the root element to it, then
add your fragment as a child node of the root element. That should do it.

John

[Redowl]

John,

Thanks for the response. What I am trying to do is return a business object
which I then use with XSLT to produce HTML. I am using an XMLReader in
conjunction with the SqlCommand object like so:

' Load data into Reader
Dim XMLR As System.Xml.XmlReader = sqlcom.ExecuteXmlReader

' Create an XmlSerializer
Dim Serializer As New XmlSerializer(GetType(Employee))

' Deserialize the data into the Projects instance
Dim Employee As Employee = CType(Serializer.Deserialize(XMLR),
Employee )

' Close reader
XMLR.Close()

Return Employee

The stored procedure associated with the SqlCommand object is returning data
using FOR XML. The Employee class has been created using XSD.exe.

Hopefully this has helped?
"John Saunders" wrote:

"Redowl" <Re****@discussions.microsoft.comwrote in message
news:59**********************************@microsof t.com...

Hi,

I am having an issue deserializing a business object from a SQL stored
procedure. I have created the class using the XSD tool and the resulting
XMLDATA schema but when I try to create the object I get an error message
<[Object] xmlns=''was not expected.

As the XML being returned is an XML fragment due to not having a single
root
element I have previously got around this issue by adding another table to
the database which acts purely as the root element. However, I would like
to
do this properly rather than this bodge.

Very grateful for any advice. I am using SQL 2000 and version 1.1 of the
framework.

I'd need more detail from you to give a good answer. Therefore, here's a bad
answer:

Rather than add another table to the database, I'd suggest you add a root
node to your XML. Create a new XmlDocument, add the root element to it, then
add your fragment as a child node of the root element. That should do it.

John

[John Saunders]

"Redowl" <Re****@discussions.microsoft.comwrote in message
news:38**********************************@microsof t.com...

John,

Thanks for the response. What I am trying to do is return a business
object
which I then use with XSLT to produce HTML. I am using an XMLReader in
conjunction with the SqlCommand object like so:

' Load data into Reader
Dim XMLR As System.Xml.XmlReader = sqlcom.ExecuteXmlReader

' Create an XmlSerializer
Dim Serializer As New XmlSerializer(GetType(Employee))

' Deserialize the data into the Projects instance
Dim Employee As Employee = CType(Serializer.Deserialize(XMLR),
Employee )

' Close reader
XMLR.Close()

Return Employee

The stored procedure associated with the SqlCommand object is returning
data
using FOR XML. The Employee class has been created using XSD.exe.

Hopefully this has helped?

It has helped, but you still haven't said;

1) What code you execute
2) What exception is thrown
3) What XML you're using

Also, are you returning only one Employee? If so, then I don't see why you
need another root. Why can't you treat Employee as the root, which is what
the XML Serializer will do?

John

[Redowl]

John,

The code executed is that below, "the exception is <employee xmlns=""not
expected" and no I am returning mutliple Employees each of whom have elements
within them. Thanks

"John Saunders" wrote:

"Redowl" <Re****@discussions.microsoft.comwrote in message
news:38**********************************@microsof t.com...

John,

Thanks for the response. What I am trying to do is return a business
object
which I then use with XSLT to produce HTML. I am using an XMLReader in
conjunction with the SqlCommand object like so:

' Load data into Reader
Dim XMLR As System.Xml.XmlReader = sqlcom.ExecuteXmlReader

' Create an XmlSerializer
Dim Serializer As New XmlSerializer(GetType(Employee))

' Deserialize the data into the Projects instance
Dim Employee As Employee = CType(Serializer.Deserialize(XMLR),
Employee )

' Close reader
XMLR.Close()

Return Employee

The stored procedure associated with the SqlCommand object is returning
data
using FOR XML. The Employee class has been created using XSD.exe.

Hopefully this has helped?

It has helped, but you still haven't said;

1) What code you execute
2) What exception is thrown
3) What XML you're using

Also, are you returning only one Employee? If so, then I don't see why you
need another root. Why can't you treat Employee as the root, which is what
the XML Serializer will do?

John

[John Saunders]

"Redowl" <Re****@discussions.microsoft.comwrote in message
news:FD**********************************@microsof t.com...

John,

The code executed is that below, "the exception is <employee xmlns=""not
expected" and no I am returning mutliple Employees each of whom have
elements
within them. Thanks

I bet this would work if there were only one Employee. Try this using a
query which will return only one, and see what happens. If it works, then
the exception will have been about the second <employeeelement.

In that case, you should next try using a serializer initialized for an
array of Employee. It's possible that will work.

If not, I think you'll have to use the override features of the serializer
to specify that you're dealing with an array Employee. I haven't done this
before, but in code I'd do something like this;

[XmlArray("employees")]
[XmlArrayItem("employee")]

You'd also have to get all the <employeeelements wrapped in an <employees>
element.

John

[Redowl]

John,

Thanks for taking the time to respond, will try using the XmlArray. Thanks.

"John Saunders" wrote:

"Redowl" <Re****@discussions.microsoft.comwrote in message
news:FD**********************************@microsof t.com...

John,

The code executed is that below, "the exception is <employee xmlns=""not
expected" and no I am returning mutliple Employees each of whom have
elements
within them. Thanks

I bet this would work if there were only one Employee. Try this using a
query which will return only one, and see what happens. If it works, then
the exception will have been about the second <employeeelement.

In that case, you should next try using a serializer initialized for an
array of Employee. It's possible that will work.

If not, I think you'll have to use the override features of the serializer
to specify that you're dealing with an array Employee. I haven't done this
before, but in code I'd do something like this;

[XmlArray("employees")]
[XmlArrayItem("employee")]

You'd also have to get all the <employeeelements wrapped in an <employees>
element.

John