We needed to execure Perl programs from an already established Java environment (CMS engine).
InlineJavaPerlInterpreter wasn't suitable, as it seems to require the JNI setup, and its portability is under a big question, at least it is much harder to automate.
I've automated the Inline::Java installation from CPAN (so that we can deploy our application and its Perl part "just runs" anywhere where Perl is installed; here is how I did it, in case anybody is interested: http://bizlink.ru/public/perl/install.pl).
Then i've started the InlineJavaServer manually, from a separate thread, in the shared mode.
Cudos to the Inline::Java developers, everything seems to work as expected: we can execute Perl programs from Java and they can access anything from inside our Java VM using static method invocations on STUDY-ed classes.
I want to restrict that "backdoor" to our JVM to be accessible only from the lo (127.0.0.1) interface. Of course i can (usually) use a firewall for that, but it still would be fine to have a "host" argument in the InlineJavaServer constructor. Like that:
(4)
]
