Good Morning-

I agree defining a WSDL clearly defines what operations you will be Requesting 
from the Axis Server as well as
Input and Output parameters to those operations with stated endpoint addresses

+1
Martin--
*********************************************************************
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.



----- Original Message ----- 
From: "Paul Fremantle" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, July 12, 2006 8:07 AM
Subject: Re: RE: schema vs. xsd:schema


> Simon
> 
> Absolutely +1 to WSDL first development. It also helps if you restrict
> your use of schema to a set of fairly limited constructs.
> 
> As regards the looseness of the WSDL spec, its worth looking at the
> WS-I base profile (www.ws-i.org) which gives a much much more
> interoperable approach by restricting and subsetting WSDL, and SOAP.
> 
> Paul
> 
> On 7/12/06, Simon Fell <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> If interop between different stacks is important to you then I'd highly
>> recommend you do a WSDL first approach, write your WSDL first and then build
>> your code from the WSDL, and not have the WSDL generated from your code.
>>
>>
>>  Cheers
>>  Simon
>>
>>  -----Original Message-----
>>  From: Jarmo Doc [mailto:[EMAIL PROTECTED]
>>  Sent: Tue 7/11/2006 7:24 PM
>>  To: [email protected]
>>  Subject: RE: RE: schema vs. xsd:schema
>>
>>  Thanks very much guys (Simon, Ian, Paul).  Much appreciate the help.  I'm
>>  finding that I'm frequently having to debug WSDL that works fine with Axis
>>  but not necessarily with other client tools and it's quite a challenge to
>>  determine a) who's at fault and b) what's the lowest common denominator
>> that
>>  works with all.
>>
>>  The 1.1 WSDL docs that I refer to are heavy on terms like "should" and
>> "can"
>>  as opposed to "will" and "must".  More of a discussion than a
>> specification.
>>    I think the later specs are more precise, no doubt partly as a result of
>>  the problems caused by the earlier ones.
>>
>>  Thanks again for your help.
>>
>>
>>  >From: "Simon Fell" <[EMAIL PROTECTED]>
>>  >Reply-To: [email protected]
>>  >To: [email protected]
>>  >Subject: RE: RE: schema vs. xsd:schema
>>  >Date: Tue, 11 Jul 2006 16:22:34 -0700
>>  >
>>  >Good catch.
>>  >
>>  >-----Original Message-----
>>  >From: Ian Brown [mailto:[EMAIL PROTECTED]
>>  >Sent: Tuesday, July 11, 2006 3:51 PM
>>  >To: [email protected]
>>  >Subject: Re: RE: schema vs. xsd:schema
>>  >
>>  >Not to be a pedant, but I'm correcting a minor typo in Simon's response
>>  >so Jarmo does not get confused:
>>  >
>>  >On 7/11/06, Simon Fell <[EMAIL PROTECTED]> wrote:
>>  > > It depends on whether the schema namespace has been made the default
>>  > > namespace or not.
>>  > > <schema xmlns="http://www.w3.org/2001/XMLSchema";>
>>  > >   <element name="foo" />
>>  > > </schema>
>>  > >
>>  > > Is equivilent to
>>  > > <xsd:schema
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>>  > >   <xsd:element name="foo" />
>>  > > </xsd:schema>
>>  >
>>  >Cheers,
>>  >
>>  >- Ian
>>  >
>> >---------------------------------------------------------------------
>>  >To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>>  >For additional commands, e-mail: [EMAIL PROTECTED]
>>  >
>> >---------------------------------------------------------------------
>>  >To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>>  >For additional commands, e-mail: [EMAIL PROTECTED]
>>  >
>>
>> _________________________________________________________________
>>  FREE pop-up blocking with the new MSN Toolbar - get it now!
>> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>>
>>
>> ---------------------------------------------------------------------
>>  To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>>  For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>>
> 
> 
> -- 
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> 
> http://bloglines.com/blog/paulfremantle
> [EMAIL PROTECTED]
> 
> "Oxygenating the Web Service Platform", www.wso2.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

Reply via email to