I have a strange problem. I added a Web Reference to a web service. Then
added messages for one of its operation's request and response. Then I
created a transformation in which I transform the response into another
schema. This is all fine.

But when I try to use the transform in a Transform shape, the transform
configuration dialog box doesn't show the web reference messages. It shows
only the messages that were created explicitly.

Any help will be appreciated.

Thank you.

P

[ Post a follow-up to this message ]

The web reference messages you refer to are types not messages.
You still have to explicitly add a message of that type to the
orchestration.

Greg

"Prash" <Prash@msn.com> wrote in message
news:uBEOhXLaGHA.3740@TK2MSFTNGP03.phx.gbl...
>I have a strange problem. I added a Web Reference to a web service. Then
>added messages for one of its operation's request and response. Then I
>created a transformation in which I transform the response into another
>schema. This is all fine.
>
> But when I try to use the transform in a Transform shape, the transform
> configuration dialog box doesn't show the web reference messages. It shows
> only the messages that were created explicitly.
>
> Any help will be appreciated.
>
> Thank you.
>
> P
>

[ Post a follow-up to this message ]

Actually I did define those types as messages. See the picture below.


Here FileInput and FileOutput refer to schema defined using XSD files. Initi
alizeOrderWSInput and InitializeOrderWSOutput refer to the web service reque
st and response respectively.

In my email I said only explicitly created messages show up. I should have s
aid only the messages that refer to a schema file show up. As shown in the d
iagram above, I did create messages pointing to the types.

The transformation configuration dialog box looks like the following. Here t
he drop down doesn't show the messages that refer to web service.


Funny part is that another project which refers to a different web service, 
doesn't have this problem.

Thanks.

"Greg Forsythe" <greg.forsythe@gmail.com> wrote in message news:OWFNRsTaGHA.4544@TK2MSFTNGP0
2.phx.gbl...
> The web reference messages you refer to are types not messages.
> You still have to explicitly add a message of that type to the 
> orchestration.
> 
> Greg
> 
> "Prash" <Prash@msn.com> wrote in message 
> news:uBEOhXLaGHA.3740@TK2MSFTNGP03.phx.gbl... 
> 
>

Attachment:
This has been downloaded 0 time(s).

[ Post a follow-up to this message ]

Prash,
I have just struck the same problem.
The Add Web Reference does not add the necessary schemas to the
reference.xsd.

In my case it was because the .Net web service was passing a class that was
declared as [XmlType(Anonymous=true)]
By changing this to [XmlRoot(Namespace="urn:mynamespace")] the problem w
as
solved.

Greg


"Prash" <Prash@msn.com> wrote in message
news:OsWOoaYaGHA.4780@TK2MSFTNGP02.phx.gbl...
Actually I did define those types as messages. See the picture below.


Here FileInput and FileOutput refer to schema defined using XSD files.
InitializeOrderWSInput and InitializeOrderWSOutput refer to the web service
request and response respectively.

In my email I said only explicitly created messages show up. I should have
said only the messages that refer to a schema file show up. As shown in the
diagram above, I did create messages pointing to the types.

The transformation configuration dialog box looks like the following. Here
the drop down doesn't show the messages that refer to web service.


Funny part is that another project which refers to a different web service,
doesn't have this problem.

Thanks.

"Greg Forsythe" <greg.forsythe@gmail.com> wrote in message
news:OWFNRsTaGHA.4544@TK2MSFTNGP02.phx.gbl...
> The web reference messages you refer to are types not messages.
> You still have to explicitly add a message of that type to the
> orchestration.
>
> Greg
>
> "Prash" <Prash@msn.com> wrote in message
> news:uBEOhXLaGHA.3740@TK2MSFTNGP03.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Greg,

Thanks for the input. Sorry I wasn't monitoring this post.

Where can I look for the class that .Net web service is sending? Could that
be in the WSDL? Or is it a system wide setting? If it is a system wide
setting, then this won't help my cause because I can use another web
service.

Thank you
"Greg Forsythe" <greg.forsythe@gmail.com> wrote in message
news:Ov%23WdxybGHA.3348@TK2MSFTNGP03.phx.gbl...
> Prash,
> I have just struck the same problem.
> The Add Web Reference does not add the necessary schemas to the
> reference.xsd.
>
> In my case it was because the .Net web service was passing a class that
> was declared as [XmlType(Anonymous=true)]
> By changing this to [XmlRoot(Namespace="urn:mynamespace")] the problem
 was
> solved.
>
> Greg
>
>
> "Prash" <Prash@msn.com> wrote in message
> news:OsWOoaYaGHA.4780@TK2MSFTNGP02.phx.gbl...
> Actually I did define those types as messages. See the picture below.
>
>
> Here FileInput and FileOutput refer to schema defined using XSD files.
> InitializeOrderWSInput and InitializeOrderWSOutput refer to the web
> service request and response respectively.
>
> In my email I said only explicitly created messages show up. I should have
> said only the messages that refer to a schema file show up. As shown in
> the diagram above, I did create messages pointing to the types.
>
> The transformation configuration dialog box looks like the following. Here
> the drop down doesn't show the messages that refer to web service.
>
>
> Funny part is that another project which refers to a different web
> service, doesn't have this problem.
>
> Thanks.
>
> "Greg Forsythe" <greg.forsythe@gmail.com> wrote in message
> news:OWFNRsTaGHA.4544@TK2MSFTNGP02.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Check the reference.xsd that is created when the Web Reference is added.
This file contains the schema/s that are generated from the WSDL.

The class that I mentioned in the previous post was declared at the remote
web service. When this class is used in a web service the .Net Framework
creates a schema  based on the XmlSerialization attributes used on the
class. This schema is published in the WSDL. Because the class had the
XmlType Anonymous = true, Biztalk was unable to understand the WSDL and
create the appropriate schema at the Biztalk end

Greg


"Prash" <Prash@msn.com> wrote in message
news:eScMzOwcGHA.3888@TK2MSFTNGP02.phx.gbl...
> Greg,
>
> Thanks for the input. Sorry I wasn't monitoring this post.
>
> Where can I look for the class that .Net web service is sending? Could
> that be in the WSDL? Or is it a system wide setting? If it is a system
> wide setting, then this won't help my cause because I can use another web
> service.
>
> Thank you
> "Greg Forsythe" <greg.forsythe@gmail.com> wrote in message
> news:Ov%23WdxybGHA.3348@TK2MSFTNGP03.phx.gbl... 
>
>

[ Post a follow-up to this message ]