Another option is something we're implementing right now - use XML-RPC to encapsulate the areas that Perl and Java both need to talk to. We have a Perl app and a Java app that both need to work with the same tables, but those tables are in constant flux. So, we are putting up an XML-RPC layer to hide the details. Took us 30 minutes to get XML-RPC up and running using
Frontier::RPC2 as the server. (That included compiling Apache1 and MP1.)
------
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
I shouldn't have to say this, but any code, unless otherwise stated, is untested