Dims, unless our tests were run wrong it appears the only way it works is to have two files - foo.mar and foo.jar both available. The foo.jar needs to be under the WEB-INF/lib dir, but the foo.mar can be in either WEB-INF/lib or WEB-INF/modules. Leads me to two questions: 1 - is this the right design? Doesn't seem the most user friendly. 2 - if the .mar file can be in either place, is there any point to having the modules dir?
thanks -Doug ______________________________________________________ STSM | Web Services Architect | IBM Software Group (919) 254-6905 | IBM T/L 444-6905 | [EMAIL PROTECTED] "Davanum Srinivas" <[EMAIL PROTECTED]> 02/14/2007 06:50 PM Please respond to [email protected] To [email protected] cc Subject Re: accessing methods in a module Doug, Come to think of it. i think If you place the mar file in WEB-INF/lib. The module is loaded and the code in there is available to services. Need to test it of course... -- dims On 2/14/07, Doug Davis <[EMAIL PROTECTED]> wrote: > > If I have a module that exposes some static utility methods - what is the > way axis2 developers are supposed to model that? > For example, let's say a popular module like WS-Addressing were to expose > some utility method to convert a chunk of XML into an EPR. Clearly logic > that falls within the WS-Addressing module's domain but useful for more than > just the module itself. Applications (on the client and/or server) may need > this kind of utility for their own purposes. From my understanding, the > module classloading logic in axis2 is such that if I wanted to expose these > static methods I would need to duplicate the appropriate jar files. In > other words, I need to copy the jars from the .mar file out into the normal > classloader path - e.g. WEB-INF/lib. If correct, this seems less then > friendly since from the application's point of view, once the module is > engaged they may wonder why those classes are not available to be used - and > this would mean that module developers would need to package their code in > such a way that jars could easily be extracted for reuse outside of the > module w/o duplicating all jars (and they would need to communicate which > jars need to be copied in their docs). > > thanks > -Doug > ______________________________________________________ > STSM | Web Services Architect | IBM Software Group > (919) 254-6905 | IBM T/L 444-6905 | [EMAIL PROTECTED] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
