Java status (was: final push to PHP4)
| From: | rubys at us dot ibm dot com | Date: | Sun, 12 Mar 2000 20:59:29 +0000 |
| Subject: | Java status (was: final push to PHP4) | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-16730@lists.php.net to get a copy of this message | ||
Summary: code is in good shape, I'm working installation issues, and I
still have no clue how to include this in the existing documentation.
Code status:
ext/java: I've tested a wide variety of Java classes, with various
parameter types and overloads and the like. While there will always be
tweaks and the occasional bug, I consider this ready for release.
sapi/servlet: I've got PHP equivalents of all the Jakarta servlet
examples running. At the moment, I require a servlet engine supporting
the 2.2 specification (sorry JServ users). This code is not quite as
mature, but it should be included in the release - if there are any
problems, I will fix them.
JSP: it was my hope to make PHP a JSP language by this point, but at the
moment, it seems smarter to focus on installation issues.
Installation issues:
I've had a number of people try out java support with the latest JDK for
Linux from Sun. I had never tried it myself, and it didn't work. The
reason was simple - instead of putting all the shared libraries in a
single directory, they split them over three. Something else is
different about this version of the JDK, as I do not seem to be able to
defer the resolution of these symbols until execution time.
I'm reworking the configure scripts to detect the JDK level better, and
move setup information from being in the php.ini into the rpath of the
compile and installation steps.
Installation on Windows continues to not be a problem.
Documentation issues:
The essence of the java support is that every Java class ever written
(and even ones yet to be written) are PHP classes. So standard rules on
how to document PHP classes can't be practically applied here.
I don't even have any PHP functions defined. Initially, the only part
of Java that is visible is the ability to do a
new Java("classname", constructor_args...);
Beyond configuration information, the only thing notable about
sapi/servlet is that two additional objects are available to the PHP
script: $request and $response.
Suggestions welcome.
Beyond this, I plan to start working on articles that describe why I
consider this function important, how it relates to other Java based web
server technologies (JSP, Cocoon, etc), differences in object models
between PHP and Java, and other topics.
- Sam Ruby