RE: WSDL

Anne Thomas Manes Thu, 13 Jun 2002 13:31:37 -0700

My apologies. I did not understand your question. Let me verify that I understand it now. There is a service that's currently running on a Windows system that you would now like to implement using Apache SOAP and deploy on a Unix machine. Once you've completed this effort the Windows-based service will no longer be involved, and we don't care about it any longer.

If that's the case, then you need to obtain the WSDL file that describes the Windows service. (It doesn't matter if it's .NET or MS SOAP. And you don't need the WSML file.) Feed the WSDL file into a Java-based WSDL compiler, such as the WSDL2Java utility available with Apache Axis. This will generate a skeleton. Fill in your own application logic. Deploy the service.

Anne

-----Original Message-----
From: Martin Gainty [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 13, 2002 4:27 PM
To: [EMAIL PROTECTED]
Subject: RE: WSDL

based on your reply then WSML is a useless artifact?
Generating a C#Proxy would be an exercise in futility on a Unix box since there are no C#compilers/interpreters on Unix boxes( at least none to my knowledge)
the question is That:
This individual is writing a Java SOAP Service to be used on a Unix box ..
and he desires similar functionality as a .NET Server for a Java SOAP Service operating on a Unix box (under apache)
Note we also do not have IIS running here..
If this was a 2K or XP Server he could go Microsoft .NET and gain intended functionality.
We need to turn this conversation to situations where we would be running Apache under Unix..
Your turn,

Martin Gainty

______________________________________________

Disclaimer and confidentiality note

Everything in this e-mail and any attachments relating to the official business of Laconia Data Systems (LDS) is proprietary to the company. It is confidential, legally privileged and protected by law. LDS does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of LDS.

The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way.

LDS can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference.

_______________________________________________

>From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
>Subject: RE: WSDL
>Date: Thu, 13 Jun 2002 16:09:21 -0400
>MIME-Version: 1.0
>Received: from [63.251.56.142] by hotmail.com (3.2) with ESMTP id MHotMailBED246CB00364004321C3FFB388ED6240; Thu, 13 Jun 2002 13:08:43 -0700
>Received: (qmail 33488 invoked by uid 500); 13 Jun 2002 20:08:21 -0000
>Received: (qmail 33478 invoked from network); 13 Jun 2002 20:08:21 -0000
>Received: from rwcrmhc53.attbi.com (204.127.198.39) by daedalus.apache.org with SMTP; 13 Jun 2002 20:08:21 -0000
>Received: from TPX21 ([66.30.2.199]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020613200826.JUYY11659.rwcrmhc53.attbi.com@TPX21>; Thu, 13 Jun 2002 20:08:26 +0000
>From soap-user-return-13965-mgainty Thu, 13 Jun 2002 13:10:03 -0700
>Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
>Precedence: bulk
>list-help:
>list-unsubscribe:
>list-post:
>Delivered-To: mailing list [EMAIL PROTECTED]
>Message-ID: <[EMAIL PROTECTED]>
>X-Priority: 3 (Normal)
>X-MSMail-Priority: Normal
>X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
>Importance: Normal
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
>In-Reply-To: <[EMAIL PROTECTED]>
>X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
>
>Martin,
>
>WSML is the _service_ configuration file for MS SOAP Toolkit. It's
>equivalent to the Apache Axis WSDD. It tells the MS SOAP Listener where to
>route a call when it's received. A SOAP message comes in; the MS SOAP
>Listener determines which operation has been requested; it looks in the WSML
>file to figure out what COM object to load.
>
>You don't need a WSML file with a .NET service (since you're not loading a
>COM object).
>
>You also don't need a WSML file for either a .NET client or an MS SOAP
>client. That's because you aren't servicing the request on the client --
>you're sending the request to the remote Web Service (which I assume is a
>Java service? perhaps an Apache SOAP service?). So what you need to do is
>get your hands on a WSDL description of the service and feed it to the .NET
>wsdl.exe utility (the .NET WSDL compiler), which will generate a C# proxy
>object for the remote service. Then your client application can simply make
>method invocations on the C# proxy object. The proxy object will convert the
>method invocations into SOAP calls, which will get sent to your service.
>
>Anne
> -----Original Message-----
> From: Martin Gainty [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 13, 2002 3:38 PM
> To: [EMAIL PROTECTED]
> Subject: RE: WSDL
>
>
> You're only Half way there..
> You may have WSDL but you are missing WSML
> read the definition of WSML:
> A WSML file provides information that maps the operations of a service (as
>described in the WSDL file) to specific methods in the COM object. The WSML
>file determines which COM object to load to service the request for each
>operation....
>
> How does one make a COM object from a Java Class or JAR???
> when there are NO COM Objects here..
>
> Ten Cuidado Mattias,
>
>
> Martin Gainty
>
>
> ______________________________________________
>
> Disclaimer and confidentiality note
>
> Everything in this e-mail and any attachments relating to the official
>business of Laconia Data Systems (LDS) is proprietary to the company. It is
>confidential, legally privileged and protected by law. LDS does not own and
>endorse any other content. Views and opinions are those of the sender unless
>clearly stated as being that of LDS.
>
> The person addressed in the e-mail is the sole authorised recipient.
>Please notify the sender immediately if it has unintentionally reached you
>and do not read, disclose or use the content in any way.
>
>
> LDS can not assure that the integrity of this communication has been
>maintained nor that it is free of errors, virus, interception or
>interference.
>
> _______________________________________________
>
>
>
> >From: "Anne Thomas Manes"
> >Reply-To: [EMAIL PROTECTED]
> >To:
> >Subject: RE: WSDL
> >Date: Thu, 13 Jun 2002 15:23:38 -0400
> >MIME-Version: 1.0
> >Received: from apache.org ([63.251.56.142]) by hotmail.com with Microsoft
>SMTPSVC(5.0.2195.4905); Thu, 13 Jun 2002 12:22:54 -0700
> >Received: (qmail 90570 invoked by uid 500); 13 Jun 2002 19:22:42 -0000
> >Received: (qmail 90553 invoked from network); 13 Jun 2002 19:22:42 -0000
> >Received: from rwcrmhc51.attbi.com (204.127.198.38) by
>daedalus.apache.org with SMTP; 13 Jun 2002 19:22:42 -0000
> >Received: from TPX21 ([66.30.2.199]) by rwcrmhc51.attbi.com (InterMail
>vM.4.01.03.27 201-229-121-127-20010626) with SMTP id
><20020613192243.KQNR11426.rwcrmhc51.attbi.com@TPX21> for ; Thu, 13 Jun 2002
>19:22:43 +0000
> >Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> >Precedence: bulk
> >list-help:
> >list-unsubscribe:
> >list-post:
> >Delivered-To: mailing list [EMAIL PROTECTED]
> >Message-ID:
> >X-Priority: 3 (Normal)
> >X-MSMail-Priority: Normal
> >X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
> >Importance: Normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
> >In-Reply-To: <005901c212e7$a78d0ee0$01050aa3@vaio>
> >X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
> >Return-Path: [EMAIL PROTECTED]
> >X-OriginalArrivalTime: 13 Jun 2002 19:22:55.0273 (UTC)
>FILETIME=[B8077990:01C2130F]
> >
> >Matias,
> >
> >Was that a typo? did you mean to ask how to obtain the WSDL file?
> >
> >From .NET all you need is the WSDL file to generate a client. You only
>need
> >a WSML file when you're using MS SOAP Toolkit to build a service (not a
> >client). Note that you don't need WSML with .NET.
> >
> >How did you build your service? with Apache SOAP? or some other SOAP
> >toolkit?
> >
> >If your service is built with Java, then you should be able to use a
> >java2wsdl tool to generate your WSDL. You can find a java2wsdl tool in
>the
> >Apache Axis kit.
> >
> >Anne
> > -----Original Message-----
> > From: Mati [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, June 13, 2002 10:35 AM
> > To: [EMAIL PROTECTED]
> > Subject: WSDL
> >
> >
> > Hi, i want to create the WSDL to make available the service to a .NET
> >application. How can i obtain this WSML from the service created and
>deplyed
> >in SOAP?
> >
> > Thanks a lot.
> >
> > Matias.
> >
>
>
>----------------------------------------------------------------------------
>--
> Join the world’s largest e-mail service with MSN Hotmail. Click Here
>

Chat with friends online, try MSN Messenger: Click Here

RE: WSDL

Reply via email to