axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas" <dava...@gmail.com>
Subject Re: [axis2] More Modules and classpaths
Date Mon, 04 Jun 2007 17:43:35 GMT
Enumeration enumeration = URLClassLoader.findResource("META-INF/modules.xml");

On 6/4/07, Sanjiva Weerawarana <sanjiva@opensource.lk> wrote:
> How exactly are you proposing to discover modules on the classpath?
>
> Sanjiva.
>
> Glen Daniels wrote:
> > Catching up on other msgs in this thread:
> >
> > David Illsley wrote:
> >> But surely you're still resolving that issue now... what if there's a
> >> copy on the classpath in the same directory as an axis2 jar and a copy
> >> in the modules directory?
> >
> > +1.  All we need here is a clear precedence mechanism, just like
> > classpaths in general.  IMO, we should be using the contents of the
> > modules/ directory FIRST, and THEN looking on the classpath for modules.
> >   For a given module, if you already have a module of that name loaded,
> > you log a WARNING about it and continue without loading it again.  Since
> > we have isolation for Modules, we just need to make sure that each
> > AxisModule object is correctly initialized with the appropriate
> > ClassLoader, and we should be all set.
> >
> > Incidentally, I believe we also should have an option to turn off
> > loading modules from the classpath (although I do think it should
> > default to on).
> >
> > --Glen
> >
> >> On 01/06/07, Deepal Jayasinghe <deepal@opensource.lk> wrote:
> >>> hi David
> >>> > Deepal, I took a look at that page and my understanding of what Glen
> >>> > is going to do is support modules anywhere on the classpath, not just
> >>> > when they are in the same directory as the other axis2 jars.
> >>> Initially we had that way , but when we have both the ways (class path +
> >>> modules directory) I faced conflicting  situation.  Say for an instance
> >>> we have module in class path and we have a new module in the module
> >>> directory , there I had issues of which one to use. Therefore I think if
> >>> some one can create a configuration context from a file system then he
> >>> can definitely put his modules into modules directory  and  then create
> >>> the configuration context. As I can see loading modules from class path
> >>> is really useful in the client side not in the server side.
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >>> For additional commands, e-mail: axis-dev-help@ws.apache.org
> >>>
> >>>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Director; Open Source Initiative; http://www.opensource.org/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message