But, I !have! to use .NET...its the main part of my project work. I've been
searching and searching...but still i have no idea how to get a C#
application to get talking with an Apache soap webservice. It seems to be
possible because xmethods.com have done it: http://www.xmethods.com/dotnet
...

"Many of the XMethods services now have "adapter" interfaces that allow
seamless binding with MS .NET clients.   The services themselves are built
on a variety of different implementations (Apache, SOAP::Lite, etc) but the
interfaces hide the interoperability issues that currently exist between
DotNet and other SOAP implementations."

Any ideas on how xmethods did this?
Or, is there a simpler way to use a Apache SOAP webservice in an .NET
client?

Thanks.

----- Original Message -----
From: "Abbott, James STASCO-OTO/72" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 14, 2001 11:11 AM
Subject: RE: Apache SOAP webservice & .NET client


> Use the MS SOAP 2.0 Gold Toolkit, which in itself is a fully supported
> Microsoft product. From this you can either read WSDL files to use the
high
> level API, or you can use the low level API which will connect without the
> need for the aforementioned file. I can give you some examples of VB
client
> code if needed. The best option is to get the SOAP server running.
>
> Apache SOAP 2.2
> Xerces 1.4.... and the rest..
>
> -----Original Message-----
> From: Joseph George [mailto:[EMAIL PROTECTED]]
> Sent: 13 June 2001 17:08
> To: [EMAIL PROTECTED]
> Subject: Re: Apache SOAP webservice & .NET client
>
>
> Hi,
> I just installed VS.NET yesterday...and i can't wait for beta2(i need to
sow
> some results to my boss soon!). So is it possible to consume an Apache
SOAP
> webservice from a VS.NET(beta1,c#) client? Is so, how do i go about and do
> it. please give explicit instructions...i'm new to all of this!!
> ----- Original Message -----
> From: "Mark Richman" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, June 13, 2001 3:10 PM
> Subject: Re: Apache SOAP webservice & .NET client
>
>
> > If you wait for VS.NET Beta 2, you can use WSDL instead of SDL. The WSDL
> file can be generated from your class by the IBM WSTK easily.
> >
> > By the way, why don't we have an Apache SOAP WSDL and proxy class
> generator?
> >
> > - Mark
> >
> > On Wed, 13 June 2001, "Joseph George" wrote:
> >
> > >
> > > Hi,
> > > I checked the archives of this list but most of the messages
concerning
> .NET
> > > dealt with an apache soap client and a .NET webservice. I want to know
> how
> > > to make it work the otherway round.
> > >
> > > Suppose i have the following webservice in java:
> > > ----------------------------------------------
> > > public class exampleTry {
> > >     public int multiplyBy2(int i){
> > >         return i*2;
> > >     }
> > > }
> > > ----------------------------------------------
> > >
> > > and i deploy the above using the Apache SOAP admin:
> > > ----------------------------------------------------------
> > > Deployed Service Information
> > > 'urn:try:exampleTry' Service Deployment Descriptor
> > >
> > > ID -- urn:try:exampleTry
> > > Scope -- Request
> > > Provider Type -- java
> > > Provider Class -- exampleTry
> > > Use Static Class -- false
> > > Methods -- multiplyBy2
> > > Type Mappings --
> > > Default Mapping Registry Class --
> > > ----------------------------------------------------------
> > >
> > > The deployed web service is consumed perfectly by this java client:
> > > ----------------------------------------------------------
> > > public class Client{
> > >     public static void main(String[] args) throws Exception{
> > >         URL url=new
URL("http://localhost:8080/soap/servlet/rpcrouter";);
> > >         String urn="urn:try:exampleTry";
> > >         Call call=new Call();
> > >         call.setTargetObjectURI(urn);
> > >         call.setMethodName("multiplyBy2");
> > >         call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);
> > >         Vector param=new Vector();
> > >         param.addElement(new Parameter("i",Integer.class,new
> > > Integer(5),null));
> > >         call.setParams(param);
> > >         try{
> > >             Response response=call.invoke(url,"");
> > >             if(!response.generatedFault()){
> > >                 Parameter result=response.getReturnValue();
> > >                 System.out.println("Result="+result.getValue());
> > >             }
> > >             else{
> > >                 Fault f=response.getFault();
> > >                 System.err.println("Client.java: Fault Occured!\n");
> > >             }
> > >         }
> > >         catch(SOAPException e){
> > >             System.err.println("Client.java: SOAPException caught!");
> > >         }
> > >     }
> > > }
> > > ----------------------------------------------------------
> > >
> > > But now, suppose i want to use a .NET client(beta1, C#) ...how do i go
> about
> > > it? I guess i'll have to make an SDL doc describing my webservice.
Could
> > > someone post the SDL file describing the webservice above...and then
> what?
> > > Add a webreference by locating this SDL file in .NET?
> > > Could someone who got this to work please post the step-by-step
> > > instructions.
> > >
> > > Thanks.
> > > -Joseph.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, email: [EMAIL PROTECTED]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to