By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
431,985 Members | 1,712 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 431,985 IT Pros & Developers. It's quick & easy.

Remoting - influence WSDL generation

P: n/a
Hi there,

I have a very general question about .NET remoting using SOAP: is there any
way to influence WSDL generation (like setting a different target-namespace,
or which classes (e.g. custom return types) are added to WSDL)? The
background is that I would like to (ab-) use .NET remoting for offering
"webservices", which are consumed by java applications (AXIS is used for
generating client-proxy-classes) via SOAP. It works in general, but the
usage would be more handy when some modifications within the generated WSDL
would be possible.

The reasons for favoring.NET remoting over ASP.NET webservices are:
* no IIS necessary
* ease of integration into the application and offering several services can
be managed by the application at runtime.
* no applications from "ouside" of the department access the "service", so I
have control about the accessing java-applications. Also no special security
issues are necessary.
As I read, this solution is in general not recommended by microsoft. I would
be glad if someone could tell me possible problems in which I could run into
when choosing .NET remoting for my project.


Mar 19 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.