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

Very helpful. This looks like a cool project.

Interesting that I also seem to think the best/esiest way to integrate Java
with PHP is via a Java servlet accepting network requests from a PHP
client.PJB has other options, but seems to favor this one.

The XSLT example was useful, although I don't think I will use the standard
Java API for that since it does not cater to XSLT2 according to
http://www.saxonica.com/documentation/using-xsl/embedding.html

Thanks for the assistance.

On 26 March 2010 02:23, <php...@li...> wrote:

> Hi,
>
> XML processing examples can be found in the examples folder of the
> documentation download.
>
>
> http://php-java-bridge.cvs.sourceforge.net/viewvc/*checkout*/php-java-bridge/php-java-bridge/examples/XML/html_to_text.php?revision=1.7
>
>
> http://php-java-bridge.cvs.sourceforge.net/viewvc/*checkout*/php-java-bridge/php-java-bridge/examples/XML/ellipse.php?revision=1.4
>
>
> > Should I be checking out PJB instead of the servlet/REST option?
>
> Please see http://php-java-bridge.sourceforge.net/pjb/how_it_works.php
> and http://php-java-bridge.sourceforge.net/pjb/FAQ.html#performance
>
>
> Regards,
> Jost Bökemeier
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> php-java-bridge-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users
>



-- 
http://TerenceKearns.com | ABN 58705023254 | ph 0412 235 575

Hi,

XML processing examples can be found in the examples folder of the
documentation download.

http://php-java-bridge.cvs.sourceforge.net/viewvc/*checkout*/php-java-bridge/php-java-bridge/examples/XML/html_to_text.php?revision=1.7

http://php-java-bridge.cvs.sourceforge.net/viewvc/*checkout*/php-java-bridge/php-java-bridge/examples/XML/ellipse.php?revision=1.4


> Should I be checking out PJB instead of the servlet/REST option?

Please see http://php-java-bridge.sourceforge.net/pjb/how_it_works.php
and http://php-java-bridge.sourceforge.net/pjb/FAQ.html#performance


Regards,
Jost Bökemeier

hi all, I am new to the list.

Before getting too much into pjb, I want to find out whether I am barking up
the right tree.

I have developed an XML/XSLT framework for php at
http://xao-php.sf.netwhich I use for all my apps. I don't really
promote the project, but I share
the code all the same.

I would, however, like to use the best XSLT processor (Saxon) from within my
PHP/XML apps. Saxon is either Java or .NET. I'm not gonna use .NET. The
documentation over at php.net about Java integration is somewhat depressing.

Anyway, I was thinking of just creating a simple servlet to expose Saxon via
a REST API. This is hardly an "integration", but it would get the job done
in a way which could be relatively reliable.

Since XAO is designed to run on miscellaneous hosted PHP5 environments, it
would be nice if I could have a more portable solution.

Should I be checking out PJB instead of the servlet/REST option? or am I on
the right track.

Opinions would be appreciated.

ps.
The idea is for users of XAO to be able to do something like

$obj = new XAO_AppDoc("MyRootElName");
/* begin boring stuff */
$obj->SetXsltProcessor("Saxon");
$obj->objTransformer->SetServletUrl("http://localhost:8080/Saxon");
$obj->ndBuildXslPi("MyXslt2Template.xsl");
/* end boring stuff */
$obj->BuildSomeXmlContent();
$obj->Transform(); // with XSLT processor and stylesheet
$obj->Send(); // transformed output to the requesting user-agent.

of course, this is not how you would code it in real-life. Normally you
would extend AppDoc and do all the boring setup stuff in the new sub-class's
constructor.