[Mono-devel-list] PATCH: wsdl, wsdl2, DefaultWsdlHelpGenerator.aspx, SoapDocumentationHandler.cs with support to multiples languages (Changed)

Rogerio Pereira rogerio.araujo at gmail.com
Mon Feb 7 12:00:11 EST 2005

> Thanks for the patch. Unfortunately, I have to reject it because of
> several reasons:

Let's go!

> The patch changes the behavior of the wsdl tool, which already provides
> a way of specifying custom language providers. 

I disagree, only vb.net and c# is possible. And this is can be a 1.1
feature. If i'm wrong please tell me how can i specify chrome as
language in -language option.

>I don't think that
> relying on the system.web/compilation/buildproviders section of
> machine.config is a good idea.

Why not? system.codedom/compilers has the same idea! But i agree in
one point, this patch is not apropriate for wsdl2, but for wsdl is
still valid.

>This section is for ASP.NET compilation,
> which is not related at all with wsdl generation. The language aliases
> aren't even the same.

What you say with language aliases not the same? In machine.config has
CS and -l:CS already works.

> Regarding the patches for DefaultWsdlHelpGenerator and
> SoapDocumentationHandler, it is not acceptable to load in memory the
> whole machine.config file at every request.

Sorry, i agree a lot at this point. But in the case of
SoapDocumentationHandler i only can see this one being called when i
click in the "Dowload" link when i view the proxy code.
> .NET 2.0 provides a new system.codedom/compilers section which can be
> used as a general purpose language provider list. This is the way the go
> in the future, and what wsdl2 and the WS doc page should be based on.

Ok! But i think that some code is still apropriate for 1.1 tools and classes.


More information about the Mono-devel-list mailing list