php-java-bridge-users Mailing List for PHP/Java Bridge

Hi,

we keep the C wrapper because some distributions use it. If you have questions regarding the distribution packages, please contact the distributor.


> If it was needed only back then, why is it still part of 'make install',
> 'install.sh'?

It's for backward compatibility.


> 'INSTALL.LINUX' from CVS says:

Ah, I see. The latest INSTALL.LINUX file is in the binary download. I will check it in, if I have some time.


Regards,
Jost Boekemeier



      __________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com

Hello,

first of all this thread discovered some new stuff again for me as well :->

php...@li... schrieb:
> Hi Felix,
> 
> [java.so for backward compatibility]
>> Well, this sounds for me like a bad april fool.
> 
> Bear in mind that I have written the PHP/Java Bridge in 2003. PHP 4
> didn't have the functionality required to access Java, so a piece of
> glue code called "java.so" was necessary.

If it was needed only back then, why is it still part of 'make install',
'install.sh'?

I assume the only purpose of 'java.so' now is to enable the
httpd(apache) to start a JVM as child, which could serve as a backend
for the php-java-bridge?

>> So all (current) articles that describe the use of the extension
>> are just crap?
> 
> I don't think so. -- If you find a bug in our documentation, please
> file a bug report.

'INSTALL.LINUX' from CVS says:
<quote>The "java.so" file contained in the Linux binary packages is the
PHP "Java.inc" compiled to native code</quote>

So,that's not true anymore, is it?

Thx and greets,
Peter