|
From: <php...@li...> - 2007-06-14 14:17:56
|
> It is certainly possible to load classes so that > class@classLoader1 is assignment-incompatible to > class@classLoader2.=20 >=20 > But I don't see this as a problem of the PHP/Java > Bridge. -- When the request is done all versions of > the PHP/JavaBridge allocate a new > DynamicJavaBridgeClassLoader to avoid such problems > (one class coming from the VM cache, the other one > from the loader). Assuming for a moment that there may be a classloader issue, do you think it might be safer for us to put all our jars in one of the directories the Bridge loads by default, rather than use java_require()? > Can you please open a problem report, and attach code > which allows us to reproduce the problem? And/or > please set the log level to 4 and attach the log at > the end of the ticket. I'd be happy to. Unfortunately, we don't have any code that can reliably reproduce the problem -- it comes and goes without notice -- but I'll do my best. As I've said, we see the problem most often when the Bridge is running in Tomcat. How do I configure the Tomcat-deployed Bridge to put its log file in the directory of my choosing? Thanks, Jonathan |