On Wed, 15 Aug 2001, Martin van den Bemt wrote:
> A bit of concern here..
> I'm working constantly with 3.3 cvs version and have a lot of classloader
> issues and class context reloading issues.. (the lot means : it happens a
> lot..) Some are solved by moving the jar file to the root lib dir (didn't
> find the time to get a nice reproductions scenario yet, to see if a fix
> works).
Can you give more details ? Reloading is quite flexible, I may be able to
fix this. Have you filed a bug ?
If you don't change the files in the webapp, it shouldn't do a reload. And
so far the class loader worked amazingly fine - no "Sealing Violation" or
things of this sort.
The only problem I know of is JSPs includes - that has been fixed in
jakarta-tomcat-jasper.
> The class ,eh actually context reloading, issue is in bugzilla and
> didn't get around to fix that either. Reproducing it is for now only
> possible in our very big webapp. (reloading the context after a certain
> number of servlets is loaded will give state not ready for one servlet,
> which, you probably guessed already, our main entry point in the system).
> In short : How long do I have to fix the problems and from who can I get
> some help for these class(re)loading issues?
For help - me or Nacho ( who wrote the class loader hierarcy ).
The reloading and class loader are quite modular, a fix will probably
affect only 2-3 modules. That means in the worst case ( if we can't solve
this in 1-2 weeks ) we can still have the fix available as an add-on
module.
It's a sort of "update" mechanism, like you can find in mozilla or
netbeans. This is supposed to allow fixes to be provided without the
typical ( long ) release cycle. Of course, if we can get it in 3.3.0 - it
would be great.
Costin
