Hi Glen, The main idea of introducing that was to provide module related data from services . Say for an instance we engage module called "foo" globally by putting <module ref="foo"> in axis2.xml . And let's say that module to be work every service needs provide some kind of data , then those data can be added in side that.
We can not add those inside <module ref="foo"> , since we could engage that for globally and we need to configure them service level. Thanks Deepal Glen Daniels wrote: > Hi folks! > > Subj pretty much says it. Why do we have a separate <moduleConfig> > instead of just putting configuration directly inside <module > ref="foo">? This seems needlessly complex, causes extra hashtable > lookups, and I think it's confusing to new users. > > Is there a good reason for doing it this way? > > Thanks, > --Glen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Thanks, Deepal ................................................................ "The highest tower is built one brick at a time" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
