RE: [Proxool-developer] Re: J2EE 1.2.1 compliance testing

[<chr...@em...>]

This problem could possibly be solved by using another lock than
ConnectionPoolManager.class:

diff -r1.3 ConnectionPoolManager.java
23a24
>     private static final Object LOCK = new Object();
35c36
<             synchronized (ConnectionPoolManager.class) {
---
>             synchronized (LOCK) {


...but this does not tell us what the problem actually is.

Maybe theres somthing wrong with our Manifest.mf file?

CHR


> -----Original Message-----
> From: pro...@li...
> [mailto:pro...@li...]On Behalf Of
> Alastair Calderwood
> Sent: 12 December 2002 23:50
> To: pro...@li...
> Subject: [Proxool-developer] Re: J2EE 1.2.1 compliance testing
>
>
> The error I mentioned earlier - NoClassDefFoundError when
> ConnectionPoolManager.class is referenced - only occurs with the Proxool
> jar, not with the normal classes.  It must have something to do with the
> getResource method in ClassLoader looking for the actual class name, and
> not being able to look in archives - but I thought that it would be
> enough to set the VM classpath to include the Proxool jar.  Anyway, for
> now I am continuing with the tests using unjarred classes.
>
> Alastair Calderwood
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer