In the Java version we are using WSDL2.0's wsdlLocation feature:
http://www.w3.org/TR/wsdl20/#wsdlLocation-aii
For an example of how a service would look you might check this thread:
http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200608.mbox/%
[EMAIL PROTECTED]
--
Jeremy
On Aug 11, 2006, at 12:57 AM, Pete Robbins wrote:
of course this supposes that all the schema and wsdl is local. We
probably
need to support the case where the wsdl is remote e.g.
http://mySite/flobber.wsdl
Cheers,
On 11/08/06, Pete Robbins <[EMAIL PROTECTED]> wrote:
Actually the wsdl/xsd are loaded for a particular composite so if
there
were more say 2 .composites in a folder and 3 xsds we would load
all 3 xsds
twice, once for each composite.
On 11/08/06, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
> so we load any wsdl/xsd in the same folder as the .composite file?
> Sounds reasonable.
>
> Cheers,
>
>
> On 11/08/06, Jean-Sebastien Delfino <[EMAIL PROTECTED] > wrote:
> >
> > Pete Robbins wrote:
> > > This is similar to what Java had. I think htis is replaced by
> > > <include.wsdl >
> > > and <include.xsd> or soemthing. Not sure if this got into
the spec.
> > >
> > > Cheers,
> > >
> > >
> > > On 11/08/06, Jean-Sebastien Delfino < [EMAIL PROTECTED] >
wrote:
> > >>
> > >> It looks like Tuscany-model.config just lists the WSDLs and
XSDs
> > used in
> > >> an application. Do we still need it? or could we just
figure out
> > >> ourselves what the WSDLs and XSDs are?
> > >>
> > >> Just trying to make it simpler for users to write SCA
applications,
> > and
> > >> limit the number of things that they have to worry about...
> > >>
> > >> --
> > >> Jean-Sebastien
> > >>
> > >>
> > >>
> >
---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >> For additional commands, e-mail: tuscany-dev-
[EMAIL PROTECTED]
> > >>
> > >>
> > >
> > >
> >
> > As far as I know <include.wsdl> and < include.xsd> are not in
the spec
> > yet. I'm actually thinking that placing the WSDL and XSD files
in the
> > directory containing the application should be enough to
indicate that
> >
> > they should be used. In other words, no need to edit an XML file
> > telling
> > the runtime that some WSDL and XSD files are there, the
runtime should
> > be smart enough to just scan and find them...
> >
> > --
> > Jean-Sebastien
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
>
> Pete
>
--
Pete
--
Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
