Although the schema says it's legal, that doesn't mean that products
necessarily support it. I would avoid defining multiple services in a
single WSDL file. Note that a single service can expose any number of
ports, and each port can implement a different binding, exposing
different portType operations.

WSDL 2.0 imposed (IMO) an unreasonable restriction of one interface
(the replacement for portType) per service.

Anne

On 5/16/07, Glen Mazza <[EMAIL PROTECTED]> wrote:
Ouch.  I misread the schema.  Thanks/Sorry.

Glen


Am Donnerstag, den 17.05.2007, 08:10 +1200 schrieb Dennis Sosnoski:
> Actually it's unbounded:
>
>    <complexType name="definitionsType">
>       <complexContent>
>          <extension base="wsdl:documented">
>             <sequence>
>                <element ref="wsdl:import" minOccurs="0" 
maxOccurs="unbounded"/>
>                <element ref="wsdl:types" minOccurs="0"/>
>                <element ref="wsdl:message" minOccurs="0" 
maxOccurs="unbounded"/>
>                <element ref="wsdl:portType" minOccurs="0" 
maxOccurs="unbounded"/>
>                <element ref="wsdl:binding" minOccurs="0" 
maxOccurs="unbounded"/>
>                <element ref="wsdl:service" minOccurs="0" 
maxOccurs="unbounded"/>
>                <any namespace="##other" minOccurs="0" maxOccurs="unbounded">
>                   <annotation>
>                      <documentation>to support extensibility elements 
</documentation>
>                   </annotation>
>                </any>
>             </sequence>
>             <attribute name="targetNamespace" type="uriReference" 
use="optional"/>
>             <attribute name="name" type="NMTOKEN" use="optional"/>
>          </extension>
>       </complexContent>
>   </complexType>
>
> So the answer is yes, the WSDL can contain multiple instances of
> anything except the <wsdl:types> element. Note that the repeated
> elements need to be in the correct order, though - the types element,
> then all the messages, then all the portTypes, etc. I've seen some
> schema that had repeated elements all jumbled together, and these are
> invalid.
>
>   - Dennis
>
> Dennis M. Sosnoski
> SOA and Web Services in Java
> Axis2 Training and Consulting
> http://www.sosnoski.com - http://www.sosnoski.co.nz
> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>
>
>
> Glen Mazza wrote:
> > No, according to the schema[1], the maxOccurs of wsdl:service is 1.
> >
> > Glen
> >
> > [1] http://www.w3.org/TR/wsdl#A4.1
> >
> >
> > Am Mittwoch, den 16.05.2007, 08:33 -0700 schrieb Anil VVNN:
> >
> >> Hi,
> >>
> >> Can one WSDL file contain multiple operations i.e. multiple <wsdl:service>
> >> tags with each having its own port and binding information.
> >>
> >> Thanks.
> >>
> >
> >
> > ---------------------------------------------------------------------
> > 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]
>


---------------------------------------------------------------------
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]

Reply via email to