Since all of your data is in a mysql database, you could write stuff in java that will manipulate that data and perl will see the changes as well.
Of course, it is highly recommended that you not do this, because now instead of having your app split into 3 pieces (web, perl, and mysql) you have 4, or possibly 6 depending on how you look at it. (web, perl, mysql, and java) or (web, perl, mysql) and (web, java, mysql), meaning that you will be duplicating logic. This gets messy when a new requirement is added for a field, then you have to update it in both places.
If you must do this, consider converting the perl code to java or whatever as needed (screen at a time or functional units), and THROW THE PERL AWAY. There should never be 2 ways of doing the same thing, either one codebase or the other should be handling it.
In reply to Re: Migrating Perl to Java or .NET
by Tuppence
in thread Migrating Perl to Java or .NET
by Jason Hollman
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |