So, just to be clear again...
> > > > > > > Hi Venkat > > > > Can I just clarify that you are saying that you are having problems > > because > > of the way that the shader plugin is aggregating the definitions.xmlfiles > > that now appear in various extension modules, e.g. binding-ws-axis2, > > poilcy-logging et. and that this is not specifically related to the > > bingbank > > demo or to the way that Tuscany subsequently aggregates the contents is > > finds in definitions.xml files. > > > > Yes I am talking about aggregating the definitions.xml files from the > various modules. The shade plugin is working alright. In as much that the shade plugin is identifying that there are multiple files with the same name, definitions.xml in this case, and is blindly concatenating them? > This is not specific > to the bigbank demo - more a general problem. I think I have been caught > on > wrong foot trying to use this META-INF/services aggregation for the > definitions.xml file as well. :( I agree that having all of the files called definitions.xml located in the same logical place on the classpath is causing problems and also that the choice of META-INF/services doesn't seem to be right. Don't think these two things are related though. > > > > > > > Does definitions.xml have to appear in META-INF/services. Could we, for > > example, further qualify the definitions.xml file by putting it in a > > directory that represents the name of the extension module to which it > > refers? Or does that make it difficult to pick them up generically? > > > > I did think of including the extension module where it is defined, but > then > we must enlist all extension modules then or in otherwords enlist the > locations of these definitions.xml file somewhere. Am not sure if we can > search for resources using regular expressions - something like > /*/definitions.xml. For example, could you use something like policy-logging\src\main\resources\org\apache\tuscany\policy\logging\definitions.xml > > > Thanks. > > > > > > Simon > > >
