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

Trying to install it on WinDoze..

Per the instructions found on the links page....

http://php-java-bridge.sourceforge.net/pjb/links.php


On Fri, Nov 14, 2008 at 1:43 PM, <
php...@li...> wrote:

> Hello!
>
> java-x86-windows.dll is not in the WAR.
> Detained in guantanamo, probably...
>
>
> Seriously, why do you need a .dll to install or run the bridge?
>
>
> Peter
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> php-java-bridge-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users
>

Hello!

java-x86-windows.dll is not in the WAR.
Detained in guantanamo, probably...


Seriously, why do you need a .dll to install or run the bridge?


Peter




      

java-x86-windows.dll is not in the WAR.

Is it no longer possible to setup the bridge per the following example?

http://www.dsl.uow.edu.au/~sk33/phpjava.htm

Hi,

the current download already contains the fix:

=> http://downloads.sourceforge.net/php-java-bridge/php-java-bridge_5.3.3_j2ee.zip?use_mirror=


Regards,
Jost Bökemeier


      

Hello!

Thanks for your reply and your explanation of the problem. We are looking forward to 5.3.3 :-)


> java(...)
> // workaround for a 5.3.2 bug which must execute the second java statement within 30 seconds
> java(...)
> wait(...)
> java(...)

> However, I am curious why the wait() for more than 30 seconds is necessary?

I can think of two possible explanations in our current setup.

Firstly, we are making use of the JavaBridge in a backend daemon PHP script which runs indefinitely polling a message queue at regular intervals. Handling a message usually involves making one or more java()-calls. The interval between java()-calls is therefore dependent on the message frequency. Using PHP for this kind of backend business logic is of course a rather bad idea, but having to work with an existing architecture, we don't really have an option.
Maybe this issue could be resolved on the user level by flushing the JavaBridge somehow before the daemon goes back to sleep waiting for its next message?

Secondly, the external Java API which we are calling using the JavaBridge is at times very, very slow (response times of up to several minutes). For example:

function getExternalObjectName($externalObjectId)
{
    $externalObject = java('...')->getObject($externalObjectId);
    // the script stalls for one minute waiting for the above call to finish
    return java_values($externalObject->getName());
}


Best regards,
Johannes Staffans
itCampus GmbH