I really like that auto discovery of WSDL without having to explicitly have anything pointing to it in the scdl. Didn't the really old Java code that was first given to Apache work like this? I think Ken has also mentioned that the JAXWS binding he's doing will work like that as well. Probably there still needs to be a way to explicitly define this in the SCDL, i did like the old import.wsdl way that the Java M1 code had, it was much nicer than the tuscany-model.config we used to use and i think it makes things clearer than having a wsdlLocation on the interface.wsdl or biniding.wselements. Whatever we do we should try to keep this consistent across the Java and C++ runtimes.
...ant On 8/11/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: <snip/> 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]
