Re: [Php-java-bridge-users] "Djava.security.policy==" ?

[<php...@li...>]

Hi André,

okay, I will comment out the java.security_policy=On in the java.ini.

BTW: Which Java VM is it? The "policy==" syntax is valid (http://java.sun.com/j2se/1.4.2/docs/guide/security/PolicyFiles.html), but some JVM implementations (GNU Java?) may not recognize it.


> The "Djava.security.policy==" issue was commited
> at bind.c v1.92 [0]

It happened when I switched on the policy in the java.ini file:

-----------
        * VERSION, php-java-bridge.spec: Version 5.2.2.3 released

2008-09-21  Jost Boekemeier  <jostb@intern>

	* java.ini: Use a very restrictive security setting.
-----------



> I will adapt the packaging to include the Java.inc and
> JavaRaw.inc files.

Java.inc is everything PHP users really need. Java users who want to call PHP libraries from Java also need the JavaProxy.php within the PHP web application. I would simply install the entire java/ folder into the PEAR include path (/usr/share/pear?). (http://php-java-bridge.sourceforge.net/pjb/docs/php-api/ric_README.html)


> What about the "jce.jar" issue?

I think it's a misunderstanding. Unlike other VM implementations Java doesn't have a "GAC", a single repository for Java packages. GNU used to use /usr/share/java, Sun introduced /usr/java/packages/lib/ext in Java 1.6. java_require() searches both locations, then $HOME/lib and then PHP_INCLUDE_PATH/libname/libname.jar.

I think we should sidestep these Java class loading issues by always requiring a Tomcat back end. -- This would automatically eliminate the java.security.policy issue mentioned above and probably other (GNU-/Kaffe-/...) JVM releated issues; the Tomcat maintainers have much more experience with the different JVM implementations than we have.

Unfortunately I can't nuke the java.so and require a Tomcat back end because of *BSD kernel issues[1]. But for Debian/Ubuntu it may be a viable alternative, I think.


Regards,
Jost Boekemeier
[1] BSD is the only operating system which still doesn't contain John Nagle's TCP/IP bug fix: http://lists.freebsd.org/pipermail/freebsd-bugs/2006-April/018144.html and http://unix.derkeiler.com/pdf/Mailing-Lists/FreeBSD/net/2006-01/msg00156.pdf