|
From: <php...@li...> - 2008-12-12 22:10:20
|
Thanks for your reply. After re-reading the FAQ thoroughly, I made several experiments to see the bridge's reaction to placing the jars in different places. What I found is this: I had given a *relative* path for each jar to java_autoload. It loaded them successfully, and I was able to *explicitly* instantiate classes from all those autoloaded jars. However, if a Java class A tried to instantiate a class B located in another jar, it ran the risk of not finding the appropriate jar (even though, again, PHP was able to instantiate B). What I mean by "risk" is that loading only sometimes failed. When I specified the *absolute* paths for the jars, the problem went away. I would humbly suggest to document this behaviour in the FAQ, or to fix the bridge such that the VM's class loader behaves just like java_require. Thanks, K. |