Passing XML in a string parameter

[Ryan Champlin]

We have a parameter to a webmethod that is defined as a
string. We expect to pass XML in this string. What we've
found out is that the .Net web serivce seems to expect the
string to be in an htmlencoded format. By this I mean all
the characters such as "<", ">", "=" etc.. need to be
escaped such as &lt; and &gt; etc.. Why is it that .Net
seems to expect this? I'm assuming this is part of the
spec. somewhere that strings need to be encoded (I'm
guessing for de-serialization reasons when using a
parser). If anyone can point me to that in a spec
somewhere that would be helpful so I can explain why this
is happening.

Everything works fine when we make sure we pass this
string htmlencoded.

Thanks
Ryan

[Ryan Champlin]

I think I may have found the answer but could someone
verify that i am correct on this. From what I can tell
the SOAP spec. says that a type of string follows the XML
Schema specification for a string type. The string type
for an XML Schema says that this string contain contain
child elements thus the charaters that typically make up
element tags (such as < or >) are not allowed or basically
need to be converted to their escaped equivalent.

Ryan

>-----Original Message-----
>
>We have a parameter to a webmethod that is defined as a
>string. We expect to pass XML in this string. What

we've

>found out is that the .Net web serivce seems to expect

the

>string to be in an htmlencoded format. By this I mean

all

>the characters such as "<", ">", "=" etc.. need to be
>escaped such as < and > etc.. Why is it that .Net
>seems to expect this? I'm assuming this is part of the
>spec. somewhere that strings need to be encoded (I'm
>guessing for de-serialization reasons when using a
>parser). If anyone can point me to that in a spec
>somewhere that would be helpful so I can explain why this
>is happening.
>
>Everything works fine when we make sure we pass this
>string htmlencoded.
>
>Thanks
>Ryan
>.
>

[Jan Tielens]

That's right, otherwise you'd end up with invalid xml.

--
Greetz

Jan Tielens
________________________________
Read my weblog: [url]http://weblogs.asp.net/jan[/url]


"Ryan Champlin" <anonymous@discussions.microsoft.com> wrote in message
news:09c801c3d9e0$19edea70$a501280a@phx.gbl...

> I think I may have found the answer but could someone
> verify that i am correct on this. From what I can tell
> the SOAP spec. says that a type of string follows the XML
> Schema specification for a string type. The string type
> for an XML Schema says that this string contain contain
> child elements thus the charaters that typically make up
> element tags (such as < or >) are not allowed or basically
> need to be converted to their escaped equivalent.
>
> Ryan

> >-----Original Message-----
> >
> >We have a parameter to a webmethod that is defined as a
> >string. We expect to pass XML in this string. What

> we've

> >found out is that the .Net web serivce seems to expect

> the

> >string to be in an htmlencoded format. By this I mean

> all

> >the characters such as "<", ">", "=" etc.. need to be
> >escaped such as < and > etc.. Why is it that .Net
> >seems to expect this? I'm assuming this is part of the
> >spec. somewhere that strings need to be encoded (I'm
> >guessing for de-serialization reasons when using a
> >parser). If anyone can point me to that in a spec
> >somewhere that would be helpful so I can explain why this
> >is happening.
> >
> >Everything works fine when we make sure we pass this
> >string htmlencoded.
> >
> >Thanks
> >Ryan
> >.
> >