Re: [Axis2] Engaging modules from classpath
Deepal, I believe the ability to have a single deployment descriptor that provided the information about all the modules needed by a project would be a much cleaner model than having an XML file per module. I am not advocating taking any support away, but just saying that if we added the capability for a single XML file it would be useful. Also, it would reduce the overhead of having to load the separate XML files into memory (though I realize this isn't critical). Deepal jayasinghe [EMAIL PROTECTED] wrote: +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 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 wrote: On 8/1/07, Saminda Abeyruwan 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] - Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.
[Axis2] Engaging modules from classpath
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 make them available for engagement. If there needed to be only single module descriptor, let it be either module.xml or module-foo.xml. Thank you Saminda -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org
Re: [Axis2] Engaging modules from classpath
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 make them available for engagement. If there needed to be only single module descriptor, let it be either module.xml or module-foo.xml. Thank you Saminda -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org - Yahoo! oneSearch: Finally, mobile search that gives answers, not web links.
Re: [Axis2] Engaging modules from classpath
+1 to modules.xml with multipe module elements 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 make them available for engagement. If there needed to be only single module descriptor, let it be either module.xml or module-foo.xml. Thank you Saminda -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Engaging modules from classpath
Gents, What you're discussing seems very closely related to a jira I filed a litte while ago: https://issues.apache.org/jira/browse/AXIS2-3026 https://issues.apache.org/jira/browse/AXIS2-3026 Is this essentially what you're asking for? Cheers, Mark B From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wed 8/1/2007 10:44 PM To: axis-dev@ws.apache.org Subject: Re: [Axis2] Engaging modules from classpath +1 to modules.xml with multipe module elements 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 make them available for engagement. If there needed to be only single module descriptor, let it be either module.xml or module-foo.xml. Thank you Saminda -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Engaging modules from classpath
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 for allowing multiple module elements in modules.xml Thanks, Sanka Dustin Amrhein 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] mailto:[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 make them available for engagement. If there needed to be only single module descriptor, let it be either module.xml or module-foo.xml. Thank you Saminda -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org http://www.wso2.org -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org http://www.wso2.org -- Yahoo! oneSearch: Finally, mobile search that gives answers http://us.rd.yahoo.com/evt=48252/*http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC, not web links. - -- Sanka Samaranayake WSO2 Inc. http://www.bloglines.com/blog/sanka http://www.wso2.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (GNU/Linux) iD8DBQFGsWch/Hd0ETKdgNIRAiefAJ9uaE+H5qtVOdEyi4umPtyu1aCGmQCfe7Xl T0mml4KkDDArf4UdYpCp/yI= =5aWZ -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Engaging modules from classpath
Gents, What you're discussing seems very closely related to a jira I filed a litte while ago: https://issues.apache.org/jira/browse/AXIS2-3026 Is this essentially what you're asking for? Nope, this is something else. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Engaging modules from classpath
+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]
