Re: [Php-java-bridge-users] php/java bridge and Drupal sheet node

Hello Jost,

first of all, thx for clarification and all the great work you have put
into this.

php...@li... schrieb:
> Hi,
[...]
> During this time some things changed; the new PHP/Zend object system became
> stable, eliminating the need for a dedicated java.so/php_java.dll and global
> java.ini file (or a php.ini file with java declarations in it).

but then why does "make install" and/or "install.sh" from CVS sources
still put 'JavaBridge.jar, JavaBridge.war, java.so, php-script.jar,
RunJavaBridge and script-api.jar' into my PHP installations lib dir
(/usr/lib/php5/20060613/)?

Reading your comment and understanding more and more about the usage of
pjb(php java bridge) it seems like all of these are not needed in the
php installation where I want to use java.

> The proposed PHP namespace separator has changed, too.  Instead of

[...]
> To avoid the mentioned issues, please deploy JavaBridge.war or
> JavaBridgeTemplate.war to a JEE server or servlet engine, remove all legacy
> java.so/php_java.dll and php.ini, and then require() Java.inc directly from
> the back end.

with back end you refer to the php application here?

>> I do have JavaBridge running. However, somehow
>> Drupal doesn't seem to recognize that it exists.
> 
> Well, the communication goes through the HTTP URL connection you have used
> to fetch the Java.inc. If your script uses
> 
> <?php
> require("http://localhost:8080/JavaBridge/java/Java.inc");
> ...
> 
> all further communication uses the back end at
> 
>   localhost:8080/JavaBridge.

waow, I didn't spot this "autoconfiguration feature" yet. Seems like a
very cool and nice idea! This however requires "allow-url-fopen". Would
this be required anyway, or just here to include "Java.inc"?

I have seen the "make install / install.sh" put Java.inc into my pear
directory. So for me Java.inc is on the include path already. :->

> It's really that simple. Just get rid of the old php.ini cruft. :)

At least in the source distribution/CVS there are quite a few files with
peaces of documentation of all different scenarios and considering the
evolving history of pjb it is just not that easy to understand what one
has to do with the recent version to set it up properly. I am fully
aware that using CVS/sources one has to expect trouble, so I am not
complaining! ;)

Thx and Greets,
Peter