Hi:

I have a simple orchestration. I have published the orchestration as a web
service.
The orchestartion receives a simple XML request like this.

Request
element1 : string
element2 : string

Both element1 and element2 are distinguished fields.

After receiving the request in the orchestration I am calling a .net
assembly.
I am passing both element1 and element2 to a method in the assembly.

The very first thing I do in the method is publish the length of the
element1 and element2
to the event log.

If there are trailing blank spaces in element1 and element2 they are
trimmed.
I have verified using the orchestration debugger that it receives a
documentation where the trailing
blank spaces still exist. I suspect that the XSLT that BizTalk uses to
extract the distinguished fields
is removing the blanks spaces.

I have tried updating the XSD for Request to add a restriction  and adding
min and max length but it does not seem to make any difference.

Has anyone else seen this behavior. Does anyone have any suggestion for me.


Thanks

Raj

[ Post a follow-up to this message ]

Rajinder Singh wrote:

> Hi:
>
> I have a simple orchestration. I have published the orchestration as a web
> service.
> The orchestartion receives a simple XML request like this.
>
> Request
>     element1 : string
>     element2 : string
>
> Both element1 and element2 are distinguished fields.
>
> After receiving the request in the orchestration I am calling a .net
> assembly.
> I am passing both element1 and element2 to a method in the assembly.
>
> The very first thing I do in the method is publish the length of the
> element1 and element2
> to the event log.
>
> If there are trailing blank spaces in element1 and element2 they are
> trimmed.
> I have verified using the orchestration debugger that it receives a
> documentation where the trailing
> blank spaces still exist. I suspect that the XSLT that BizTalk uses to
> extract the distinguished fields
> is removing the blanks spaces.
>
> I have tried updating the XSD for Request to add a restriction  and adding
> min and max length but it does not seem to make any difference.
>
> Has anyone else seen this behavior. Does anyone have any suggestion for me
.
>
Yes, i've seen this behavior. I'am pretty sure this is because you
defined the elements as strings. In that case trailing blanks are removed.

I 'am not yet sure wheather this is correct or not, but it may have
sthg. to do with the xml schema spec:

http://www.w3.org/TR/xmlschema-2/#rf-whiteSpace


Johann
>
> Thanks
>
> Raj
>
>
>
>

[ Post a follow-up to this message ]

Thanks for your response. I used the whitespace element of the XML Schema
spec
and the white spaces are still being trimmed.

The interesting part is that if the very first thing in my orchestration is
a message contruct shape
the white spaces are preserved. I have no idea why this is happening.

Raj

"Johann Höchtl" <mine@echt.org> wrote in message
news:eTDR7eXgEHA.704@TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Rajinder Singh wrote:
> 
web[vbcol=seagreen] 
adding[vbcol=seagreen] 
me.[vbcol=seagreen] 
> Yes, i've seen this behavior. I'am pretty sure this is because you
> defined the elements as strings. In that case trailing blanks are removed.
>
> I 'am not yet sure wheather this is correct or not, but it may have
> sthg. to do with the xml schema spec:
>
> http://www.w3.org/TR/xmlschema-2/#rf-whiteSpace
>
>
> Johann 

[ Post a follow-up to this message ]

Hey Rajinder,

I've got the same problem so if you got a solution please post it over here.

Tx,

Danny.

"Rajinder Singh" wrote:

> Hi:
>
> I have a simple orchestration. I have published the orchestration as a web
> service.
> The orchestartion receives a simple XML request like this.
>
> Request
>     element1 : string
>     element2 : string
>
> Both element1 and element2 are distinguished fields.
>
> After receiving the request in the orchestration I am calling a .net
> assembly.
> I am passing both element1 and element2 to a method in the assembly.
>
> The very first thing I do in the method is publish the length of the
> element1 and element2
> to the event log.
>
> If there are trailing blank spaces in element1 and element2 they are
> trimmed.
> I have verified using the orchestration debugger that it receives a
> documentation where the trailing
> blank spaces still exist. I suspect that the XSLT that BizTalk uses to
> extract the distinguished fields
> is removing the blanks spaces.
>
> I have tried updating the XSD for Request to add a restriction  and adding
> min and max length but it does not seem to make any difference.
>
> Has anyone else seen this behavior. Does anyone have any suggestion for me
.
>
>
> Thanks
>
> Raj
>
>
>
>
>

[ Post a follow-up to this message ]