WSDL generation of types

[Henrik Gøttig]

Hi all

Feeling a bit frustrated here. Maybe I did not find the correct info
yet, that's why I am asking you.

I have "developed" a .NET 2.0 WebService and generated (using wsdl.exe)
the WSDL for it.
The types I am returning from webmethod calls has a superclass
(BaseBusinessOb ject). So MyBusinessObjec t inherits from BaseBusinessObj ects.
That gives me two schemas in the <types> section of my wsdl. One for the
superclass and one for the "real" business object.

Can I setup wsdl.exe somehow to generate the types in my wsdl to a
specific namespace, that is *not* the same as the namespacing I am
generating the WebService proxies to.
That way I can encourage type sharing between webmethods where it is
appropriate.
I have read somewhere that there is a way to "hook" in the schemaimport
process, but that is really a last resort....
Anyone has an idea, may be alternative..bu t anything..

Thanx in advance

Regards

Henrik

[Marvin Smit]

Hi,

Are you looking for the [XmlElement(Name space="")] attribute on your
dataclasses?

Hope this helps,

Marvin Smit.
'

On Mon, 10 Oct 2005 09:43:17 +0200, Henrik Gøttig <hg@websolver.d k>
wrote:

Hi all

Feeling a bit frustrated here. Maybe I did not find the correct info
yet, that's why I am asking you.

I have "developed" a .NET 2.0 WebService and generated (using wsdl.exe)
the WSDL for it.
The types I am returning from webmethod calls has a superclass
(BaseBusinessO bject). So MyBusinessObjec t inherits from BaseBusinessObj ects.
That gives me two schemas in the <types> section of my wsdl. One for the
superclass and one for the "real" business object.

Can I setup wsdl.exe somehow to generate the types in my wsdl to a
specific namespace, that is *not* the same as the namespacing I am
generating the WebService proxies to.
That way I can encourage type sharing between webmethods where it is
appropriate.
I have read somewhere that there is a way to "hook" in the schemaimport
process, but that is really a last resort....
Anyone has an idea, may be alternative..bu t anything..

Thanx in advance

Regards

Henrik

[Henrik Gøttig]

Hi Marvin

Thanx for taking yuor time to answer.

I have already done what you suggests, but it only applies to the XML
namespace.

What I want, is to get wsdl.exe to generate the dataclasses to a
specific CLR namespace (eg. MyCompany.MyPro duct.Data) and the proxies to
another (eg. MyCompany.MyPro duct.Web.Servic es).

One way I could think of is to use extern XML schemas for the
dataclasses and then include them in the types element of my WSDL.
Then run this as a two step process:
1) Generate classes using xsd.exe in the correct CLR namespace.
2) Generate proxies using wsdl.exe in the correct CLR namespace.

But option step 2 still generates the dataclasses of the included
schemas...so I will end up having the dataclasses doubled up anyway.
Just in two different CLR namespaces, but still in the same XML namespace.

Regards

Henrik

Marvin Smit wrote:

Hi,

Are you looking for the [XmlElement(Name space="")] attribute on your
dataclasses?

Hope this helps,

Marvin Smit.

[Marvin Smit]

Hi,

ehh.. yeah. Thats a general problem with the WSDL tool. I think the
option you provide at the bottom of this post is the way to go. The
only issue being; You're modifying stuff from generated files (WSDL
will recreate this problem each time you generate).

I know its not the answer you hoped for, but my advise in class is
always to say: "The toolkit is a means to a goal, not the goal itself.
If it doesn't do what you want, drop the toolkit!"

Eassier said than done looking at the alternatives :S

Marvin Smit.

ps; Last thing i thought of, in combination with your solution below;
Did you try the "/namespace" option for WSDL.EXE?
On Wed, 12 Oct 2005 16:00:35 +0200, Henrik Gøttig <hg@websolver.d k>
wrote:

Hi Marvin

Thanx for taking yuor time to answer.

I have already done what you suggests, but it only applies to the XML
namespace.

What I want, is to get wsdl.exe to generate the dataclasses to a
specific CLR namespace (eg. MyCompany.MyPro duct.Data) and the proxies to
another (eg. MyCompany.MyPro duct.Web.Servic es).

One way I could think of is to use extern XML schemas for the
dataclasses and then include them in the types element of my WSDL.
Then run this as a two step process:
1) Generate classes using xsd.exe in the correct CLR namespace.
2) Generate proxies using wsdl.exe in the correct CLR namespace.

But option step 2 still generates the dataclasses of the included
schemas...so I will end up having the dataclasses doubled up anyway.
Just in two different CLR namespaces, but still in the same XML namespace.

Regards

Henrik

Marvin Smit wrote:

Hi,

Are you looking for the [XmlElement(Name space="")] attribute on your
dataclasses?

Hope this helps,

Marvin Smit.

[Henrik Gøttig]

Hi Marvin

Yup, I already use the /namespace switch of the wsdl.exe tool.
And it generates to the correct CLR namespace - both data and proxi
classes. It would be nice though if one could split those

Regards

Henrik

Marvin Smit wrote:

Hi,

ehh.. yeah. Thats a general problem with the WSDL tool. I think the
option you provide at the bottom of this post is the way to go. The
only issue being; You're modifying stuff from generated files (WSDL
will recreate this problem each time you generate).

I know its not the answer you hoped for, but my advise in class is
always to say: "The toolkit is a means to a goal, not the goal itself.
If it doesn't do what you want, drop the toolkit!"

Eassier said than done looking at the alternatives :S

Marvin Smit.

ps; Last thing i thought of, in combination with your solution below;
Did you try the "/namespace" option for WSDL.EXE?
On Wed, 12 Oct 2005 16:00:35 +0200, Henrik Gøttig <hg@websolver.d k>
wrote:

Hi Marvin

Thanx for taking yuor time to answer.

I have already done what you suggests, but it only applies to the XML
namespace.

What I want, is to get wsdl.exe to generate the dataclasses to a
specific CLR namespace (eg. MyCompany.MyPro duct.Data) and the proxies to
another (eg. MyCompany.MyPro duct.Web.Servic es).

One way I could think of is to use extern XML schemas for the
dataclasses and then include them in the types element of my WSDL.
Then run this as a two step process:
1) Generate classes using xsd.exe in the correct CLR namespace.
2) Generate proxies using wsdl.exe in the correct CLR namespace.

But option step 2 still generates the dataclasses of the included
schemas...s o I will end up having the dataclasses doubled up anyway.
Just in two different CLR namespaces, but still in the same XML namespace.

Regards

Henrik

Marvin Smit wrote:

Hi,

Are you looking for the [XmlElement(Name space="")] attribute on your
dataclasse s?

Hope this helps,

Marvin Smit.