[Mono-list] C# SOAP implementation - AXIS

[Jonathan Stowe]

On Thu, 2004-04-01 at 05:57, Mahen Perera wrote:

> Thanx for the reply. Yes, I am aware about the current developments in
> MONO in the classes under System.Web.Services namespace and the
> existing Web Services architecture based around ASP.NET and building
> on its support for XML and SOAP serialization in the .NET framework. 
> 
> As u have already mentioned, the existing ASP.net web services
> architecture is tightly integrated to .NET and cannot run without IIS.
> AXIS, on the other hand is an Open Souce effort and will run on the
> Apache Web server. What i am proposing is to have another SOAP
> implementation (in C#) as an add-on to MONO, which follows the AXIS
> architecture. 
> 

As Ales points out the IIS connection is not absolute, infact I am
pretty certain that you could get Apache to serve .NET web services by
setting a handler for .asmx files that uses the ASP.NET runtime
component (check out the script map on IIS for more details on this). 
Infact mono, via the mod_mono apache module and/or xsp, can server
ASP.NET web services through Apache already as Jonathan Pryor notes.

> In developing AXIS C#, we hope to use the WSDL parser in
> System.Web.Services namespace and the XML Pull parser in System.Xml
> namespace (already implemented in MONO). Since we are following AXIS,
> we will have a server.wsdd file to configure the AXIS engine and
> follow similar architectural principles (such as having "handlers"
> to as a means of adding external components offline, in to the main
> AXIS message flow). Further to this, as I mentioned earlier, current
> AXIS users will find it easy to switch to the AXIS C#. 
> 

Personally I'm still not convinced,  there is a difference between Java
and C# in the respect that with C# you have the services provided by the
.NET framework, which includes, as we have already agreed, an
architecture for Web Services, with Java (or indeed C++) you have no
such implicit support for these things, so you need something like Axis.

Now if it was me who was looking to create an alternate web services
architecture for the .NET framework I would certainly start by looking
to reuse as much of the System.Web.Services classes as I possibly could
in order that I didn't end up creating something that behaved contrary
to the expectations raised by the rest of the platform: a cursory glance
at the code in System.Web.Services.Protocols would suggest that some of
these classes could be extended to provide something more like Axis.  I
think by starting with the parser you are only going to make more work
for yourself.


> Hope this will answer your Q. 
> 
> Hoping for positive replies
> 
> Mahen
> 
> PS: I would like to know whether the support for creating and managing
> Application Domains
> 
> is implemeted in MONO.  
> 
>  
> 
> >From: Jonathan Stowe 
> 
> 
> >To: Mahen Perera 
> >CC: Mono-List 
> >Subject: Re: [Mono-list] C# SOAP implementation - AXIS 
> >Date: Tue, 30 Mar 2004 09:22:39 +0100 
> > 
> >On Tue, 2004-03-30 at 06:32, Mahen Perera wrote: 
> > > Hi all! 
> > > 
> > > We are a team involved in developing an implementation of  SOAP
> using C#, in 
> > > the .NET framework. We are still in the early stages. 
> > > 
> > 
> >I'm probably missing some subtlety here but the .NET framework
> already 
> >implements SOAP, I'm not quite sure what there is to implement here. 
> > 
> > > We would like to contribute towards MONO with this regard.
> Therefore we are 
> > > interested in finding out what are the plans with regard to having
> a SOAP 
> > > implementation in MONO. 
> > > 
> > 
> >Mono has an implementation of the System.Web.Services classes and it 
> >appears from 
> > 
> >   http://www.go-mono.com/class-status-System.Web.Services.html 
> > 
> >that this is largely complete.  Again I might be misunderstanding
> what 
> >you are planning on doing. 
> > 
> > > We hope to follow the APACHE AXIS architecture in developing our
> SOAP 
> > > engine. This will enable users who are familiar with AXIS
> Java/AXIS C++ to 
> > > swich over to our SOAP implementation with ease. Further to this,
> there will 
> > > be many other advantages provided by AXIS. 
> > > 
> > 
> >THe .NET Framework has its own Web Services architecture based around
> >ASP.NET and building on its support for XML and SOAP serialization,
> it 
> >is a fairly different approach to that taken by Axis but as I see it 
> >this is largely due to to it's degree of integration and dependency
> on 
> >the framework as a whole. 
> > 
> >/J\ 
> > > We like to know ur ideas! 
> > > 
> > > Hoping for a positive reply... 
> > > 
> > > Mahen 
> > > 
> > > _________________________________________________________________ 
> > > Help STOP SPAM with the new MSN 8 and get 2 months FREE* 
> > > http://join.msn.com/?page=features/junkmail 
> > > 
> > > _______________________________________________ 
> > > Mono-list maillist  -  Mono-list@lists.ximian.com 
> > > http://lists.ximian.com/mailman/listinfo/mono-list 
> > 
> >_______________________________________________ 
> >Mono-list maillist  -  Mono-list@lists.ximian.com 
> >http://lists.ximian.com/mailman/listinfo/mono-list 
> 
> ______________________________________________________________________
> MSN 8 helps ELIMINATE E-MAIL VIRUSES. Get 2 months FREE*.
> _______________________________________________ Mono-list maillist -
> Mono-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list