Hi, First, thanks a ton for all the comments / opinions.
I agree, META-INF/services is not the right place for this. I suppose META-INF is ok because the definitions.xml does contain meta-data about binding and implementation types. For example, the definitions.xml in the binding.ws.axis module will define a binding type that will describe the mayProvides and alwaysProvides intents. Or, isn't this metadata at all ? Yes, the point is that definitions.xml can be a part of any contribution and hence can be anywhere. Infact, the samples / demos have the definitions.xml in the resources directory only. The issue is with the definitons.xml in the tuscany modules. They need to be loaded when the runtime is started and hence need to be explicitly searched for and loaded. Whereas in the case of contributions, the definitions.xml get processed like any other artifact in the contribution. So, the bottom line is how do we identify these various definitions.xml in the various tuscany modules ? Thanks - Venkat On Tue, Feb 26, 2008 at 4:55 AM, Jean-Sebastien Delfino < [EMAIL PROTECTED]> wrote: > Simon Laws wrote: > ... > > For example, could you use something like > > > > > policy-logging\src\main\resources\org\apache\tuscany\policy\logging\definitions.xml > > What you're proposing makes sense to me: let's put definitions.xml file > in logically named folders. > > I'm not sure that we even need a naming convention like > org/apache/tuscany/<module-name>. Definitions.xml files live in SCA > contributions and the Tuscany contribution code should be able to find > them wherever they are in the contribution (like we find WSDLs, XSDs, > composite files etc). > > -- > Jean-Sebastien > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
