RE: Patch for Context Class Loader problems (was Re: Fresh CVS ch eckout - AdminClient list fails)

[Glen Daniels <gd...@macromedia.com>]

Hi Dr. J!

Don't feel ignored - we're psyched that you're getting involved in the
project, and I'm personally really looking forward to having more people
with a deep systems/J2EE perspective on the team.  A lot of us just tend to
be really busy, and so it can take a while for things to be absorbed and
reacted to.

I'll respond to your earlier post today at some point after a bunch of
meetings - I've been a huge proponent of dealing with the classloader issues
in the Right Way for many moons now, and I think your suggestions move us in
that direction.

More later...

--Glen

> -----Original Message-----
> From: Jung , Dr. Christoph [mailto:christoph.jung@infor.de]
> Sent: Thursday, October 04, 2001 10:50 AM
> To: 'axis-dev@xml.apache.org'
> Subject: AW: Patch for Context Class Loader problems (was Re: 
> Fresh CVS
> ch eckout - AdminClient list fails)
> 
> 
> Hi all,
> 
> -----Ursprüngliche Nachricht-----
> >Von: Davanum Srinivas [mailto:dims@yahoo.com]
> >Gesendet: Donnerstag, 4. Oktober 2001 16:32
> >An: axis-dev@xml.apache.org
> >Betreff: Patch for Context Class Loader problems (was Re: Fresh CVS
> >checkout - AdminClient list fails)
> 
> >+
> Thread.currentThread().setContextClassLoader(AxisServlet.class
> .getClassLoade
> r());
> 
> In conjunction with the way the MessageContext.classLoader is 
> currently
> (NOT!) set, this 
> presupposes that any class or resource that is resolved during the
> AxisServlet.service() call 
> must be available from the classloader that points to the axis.jar. 
> 
> I think that this is too restrictive as it either means not to resolve
> anything 
> after deployment anymore (no service options à la "classname" 
> possible) or
> requires all the 
> logic residing in one big classloader setup at VM-start.
> 
> Wrt to possible solutions (Engine stores service 
> classloaders/Handlers store
> their deploying classloader) I could contribute, I refer to 
> my previous
> posting.
> 
> *Feeling ignored*,
> CGJ
> 

RE: Patch for Context Class Loader problems (was Re: Fresh CVS checkout - AdminClient list fails)

[Davanum Srinivas <di...@yahoo.com>]

Hey Guys,

The least you guys can help us is to get us up and running. This patch does exactly that and it is
VERY, VERY easy to comment it out as well. So for the short-term, *******PLEASE******* consider
this patch. 

Thanks,
dims

--- Glen Daniels <gd...@macromedia.com> wrote:
> 
> Hi Dr. J!
> 
> Don't feel ignored - we're psyched that you're getting involved in the
> project, and I'm personally really looking forward to having more people
> with a deep systems/J2EE perspective on the team.  A lot of us just tend to
> be really busy, and so it can take a while for things to be absorbed and
> reacted to.
> 
> I'll respond to your earlier post today at some point after a bunch of
> meetings - I've been a huge proponent of dealing with the classloader issues
> in the Right Way for many moons now, and I think your suggestions move us in
> that direction.
> 
> More later...
> 
> --Glen
> 
> > -----Original Message-----
> > From: Jung , Dr. Christoph [mailto:christoph.jung@infor.de]
> > Sent: Thursday, October 04, 2001 10:50 AM
> > To: 'axis-dev@xml.apache.org'
> > Subject: AW: Patch for Context Class Loader problems (was Re: 
> > Fresh CVS
> > ch eckout - AdminClient list fails)
> > 
> > 
> > Hi all,
> > 
> > -----Urspr�ngliche Nachricht-----
> > >Von: Davanum Srinivas [mailto:dims@yahoo.com]
> > >Gesendet: Donnerstag, 4. Oktober 2001 16:32
> > >An: axis-dev@xml.apache.org
> > >Betreff: Patch for Context Class Loader problems (was Re: Fresh CVS
> > >checkout - AdminClient list fails)
> > 
> > >+
> > Thread.currentThread().setContextClassLoader(AxisServlet.class
> > .getClassLoade
> > r());
> > 
> > In conjunction with the way the MessageContext.classLoader is 
> > currently
> > (NOT!) set, this 
> > presupposes that any class or resource that is resolved during the
> > AxisServlet.service() call 
> > must be available from the classloader that points to the axis.jar. 
> > 
> > I think that this is too restrictive as it either means not to resolve
> > anything 
> > after deployment anymore (no service options � la "classname" 
> > possible) or
> > requires all the 
> > logic residing in one big classloader setup at VM-start.
> > 
> > Wrt to possible solutions (Engine stores service 
> > classloaders/Handlers store
> > their deploying classloader) I could contribute, I refer to 
> > my previous
> > posting.
> > 
> > *Feeling ignored*,
> > CGJ
> > 


=====
Davanum Srinivas, JNI-FAQ Manager
http://www.jGuru.com/faq/JNI

__________________________________________________
Do You Yahoo!?
NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1