I'm trying to figure out a problem I'm having with consuming a web service
from within an orchestration, and while digging deeper, I realized that,
when I add a web reference into my BizTalk project, a "Reference.xsd" file
is not generated.  The .map, .odx, .disco, .wsdl, and .html files are
generated, but not the .xsd file.
(I figured this particular post is more "general" than my orchestration
problem, so I posted here.)

Then, I tried web service after web service and realized, that on SOME of my
web services, a Reference.xsd file would be generated, while others would
not.

I still haven't determined what the pattern is (why some but not others?),
but while I'm looking into it, I thought I'd ask if anyone else has run into
this problem.

Does anyone have any ideas about this?
What causes one web service reference to generate a "Reference.xsd" while
others do not?

Thanks,
Dan

[ Post a follow-up to this message ]

Dan,

I haven't checked this, actually... but are by any chance the webservices
that don't generate the Reference.xsd RPC/encoded services?

--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
"Dan Tharp" <dtharp@NOSPAMPLEASEgdtr.com> wrote in message
news:OjxBUgjYFHA.3356@TK2MSFTNGP15.phx.gbl...
> I'm trying to figure out a problem I'm having with consuming a web service
> from within an orchestration, and while digging deeper, I realized that,
> when I add a web reference into my BizTalk project, a "Reference.xsd" file
> is not generated.  The .map, .odx, .disco, .wsdl, and .html files are
> generated, but not the .xsd file.
> (I figured this particular post is more "general" than my orchestration
> problem, so I posted here.)
>
> Then, I tried web service after web service and realized, that on SOME of
> my web services, a Reference.xsd file would be generated, while others
> would not.
>
> I still haven't determined what the pattern is (why some but not others?),
> but while I'm looking into it, I thought I'd ask if anyone else has run
> into this problem.
>
> Does anyone have any ideas about this?
> What causes one web service reference to generate a "Reference.xsd" while
> others do not?
>
> Thanks,
> Dan
>
>

[ Post a follow-up to this message ]

An XSD file will only be generated if the web service has non-primitive inpu
t
parameters or returns a non-primitive value.  That means if your web service
only uses simple datatypes like strings and integers, an XSD is not required
,
but if it uses complext types like classes, etc, then the XSD will be
generated.  The thing to watch out for is that if you have already reference
d
a primitive type web service in the BizTalk project and later update it to
use a complex type, VS.NET does not automatically create the XSD file for
you, even if you select "Update Web Reference".  You need to remove the web
reference and add it back again.

ck.

"Dan Tharp" wrote:

> I'm trying to figure out a problem I'm having with consuming a web service
> from within an orchestration, and while digging deeper, I realized that,
> when I add a web reference into my BizTalk project, a "Reference.xsd" file
> is not generated.  The .map, .odx, .disco, .wsdl, and .html files are
> generated, but not the .xsd file.
> (I figured this particular post is more "general" than my orchestration
> problem, so I posted here.)
>
> Then, I tried web service after web service and realized, that on SOME of 
my
> web services, a Reference.xsd file would be generated, while others would
> not.
>
> I still haven't determined what the pattern is (why some but not others?),
> but while I'm looking into it, I thought I'd ask if anyone else has run in
to
> this problem.
>
> Does anyone have any ideas about this?
> What causes one web service reference to generate a "Reference.xsd" while
> others do not?
>
> Thanks,
> Dan
>
>
>

[ Post a follow-up to this message ]

Ah.....that fits.
I have around 20 web services, most of which do NOT cause the generation of
Reference.xsd when added as web references into my BizTalk project.
In fact, only 3 DO generate Reference.xsd.
Those 3 have non-primatite parameters/return values, while the ones that do
not generate Reference.xsd all have string/integer parameters/return values.
Interesting...
So, this isn't necessarily a problem then?

Thanks for the info!
Dan

"Phua Chiu Kiang" <ckphua@pc.jaring.my.(donotspam)> wrote in message
news:5B395913-6D0D-4EFF-94CB-29959363B286@microsoft.com...[vbcol=seagreen]
> An XSD file will only be generated if the web service has non-primitive
> input
> parameters or returns a non-primitive value.  That means if your web
> service
> only uses simple datatypes like strings and integers, an XSD is not
> required,
> but if it uses complext types like classes, etc, then the XSD will be
> generated.  The thing to watch out for is that if you have already
> referenced
> a primitive type web service in the BizTalk project and later update it to
> use a complex type, VS.NET does not automatically create the XSD file for
> you, even if you select "Update Web Reference".  You need to remove the
> web
> reference and add it back again.
>
> ck.
>
> "Dan Tharp" wrote:
> 

[ Post a follow-up to this message ]