I am not going to answer your question directly because I don't know the
answer.
However, consider that not many people use jpl. Therefore, it is likely
that it has more bugs than other parts of Perl. Also consider that the
software you use may end up disliking the process model and rely on
in-memory sharing (since java is multi-threaded, this assumption is made a
lot -- especially for caching) so the model of Apache/mod_perl may not
marry well.
Given these assumptions (which may not be entirely true in your
situation... YMMV), your better bet may be to set up a Java server that
communicates with your 3rd party Java libraries and then call the server
from mod_perl using an RPC mechanism. Since it sounds like you want to get
up and running quickly, I recommend prototyping with a few select
procedures you want to call manually... But for production, you could
consider CORBA (I wouldn't unless it's a huge well defined interface) or
SOAP (or some other XML-RPC mechanism) -- I tend to like these better as
they are easier to troubleshoot for mere mortals than IIOP/CORBA.
Mixing languages is a bit like mixing drugs... Not that I would know of
course. Although I do think Perl and Java are both addictive substances.
Later,
Gunther
At 02:59 PM 4/17/00 -0400, Paul G. Weiss wrote:
>I have a requirement to make use of some third party software
>written in Java. I would like to get my mod_perl based scripts
>to talk to this software. To that end I am interested in the
>jpl shipped with 5.6. Has anyone successfully integrated this
>with mod_perl on Solaris? If so, how did you build Perl. I
>am particularly interested in the threading options.
>
>More generally, how do the threading options in Perl influence
>mod_perl? Does mod_perl simply ignore them, being process based?
>Is it ill-advise to enable threading when you will be using
>mod_perl?
>
>-P
