so do you think that wsdl and shema should be loaded on a per "system" basis, i.e. we load all .wsdl and .xsd in either the root directory or any we find from the root down?
On 15/08/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
Pete Robbins 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. > Concrete scenarios will help us understand this better, but I'm starting to think that WSDLs are not loaded just per composite (or per composite folder). Let me illustrate this through my favorite bigbank scenario :) - The bigbank.account composite exposes an Account Service, described by bigbank.account/AccountService.wsdl. AccountService.wsdl is most naturally packaged in the bigbank.account composite folder or archive. - The system administrator creates a bigbank composite and inside it an instance of bigbank.account (a <component> with an <implementation.composite name="bigbank.account"/>). - The system administrator then decides to expose the AccountService to remote Web Services clients, at a configured endpoint, with the following: <service...> <interface.wsdl name="... Account"/> <binding.ws ... uri="http://myserver/account"/> </service> In this scenario you don't want to repeat/copy the WSDL in bigbank.composite just to override the endpoint exposing bigbank.account, so AccountService.wsdl needs to be known outside of the composite that initially packaged it. -- Jean-Sebastien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Pete
