> +1 to "modules.xml with multipe module elements" > I am 0+ on this , I did not find a very useful use case for this. And if want we can do that by dropping multiple .jar files. I personal opinion is we do not need to have that much of flexibility.
If we do so , some one could ask , how about adding moduels.xml to module.mar rather than having module.xml Thanks Deepal > On 8/1/07, Dustin Amrhein <[EMAIL PROTECTED]> wrote: > >> Would it be feasible (and possible) to describe multiple modules within a >> single XML file? Instead of having multiple XML files in a JAR could we >> allow the use of a modules.xml with multipe "module" elements? If this is >> possible it may make things easier on the end user by reducing the number of >> deployment descriptors that need to be produced/maintained. >> >> >> Saminda Abeyruwan <[EMAIL PROTECTED]> wrote: >> >> >> On 8/1/07, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote: >> >>> Hi Devs, >>> >>> This may be beyond Axis2 1.3. At the moment, for a given .jar, we could >>> >> only have one module.xml to represent a module. Axis2 already ship >> addressing mar module.xml in the axis2-XX.jar. What if we need to have >> multiple module.xmls in a given jar. Looking at the work I've been engaged >> with there is a possibility of having this scenario. Thus, if a multiple >> module.xmls needed for a given .jar, wouldn't it be reasonable to give it as >> follows, >> >>> foo >>> +-META-INF >>> +- module-a.xml >>> +- module-b.xml >>> ... >>> >>> Thus, at deployment time, xmls can be read with the prefix "module" and >>> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
