Haven't used Java, but I have tried out Inline::Java (a year or two ago), which worked well. It also has a more recent release (although only 2011) and more good reviews, and Java seems to be failing all its tests on CPAN Testers (although Inline::Java doesn't look too great either)...

As for the approach in general - you'll lose some performance in the Perl<->Java interface. If your web interface doesn't get many queries that'll likely be fine, but for a heavily used interface you may run into performance issues, and a pure Java web interface would probably be advisable.

Not duplicating the DAOs is probably a good idea, especially if they contain some code (validation?), but if the schema is simple and you're willing to have duplicate DAOs, take a look at DBIx::Class.

Also, if you haven't yet, look at Dancer, Catalyst, Mojolicious, and Mojolicious::Lite.

Thanks much! Exactly what I was looking for. I had just this morning encountered this idea and appreciate the quick feedback. I have just begun recently to look at the frameworks you mentioned. Thanks for re-enforcing that as well.

...the majority is always wrong, and always the last to know about it...
Insanity: Doing the same thing over and over again and expecting different results...

wjw

" I have a potential opportunity ... why not write the web portion in Perl and use the Java app to access the DB ..."

Because the folks wanting the code might want Java programmers to maintain it. What extra value does a Perl implementation provide for the requesters of this code?

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

This is a point I raised with the potential. I did let them know that, were it me, I would take that route. However, the potential did ask the question, and I thought it would be in good taste to at least pursue an answer for them. I also find the concept interesting and outside my realm of experience, so decided to pursue.

To answer your question, none that I see, other than they expressed an interest and I am interested in their interest... :-)
...the majority is always wrong, and always the last to know about it...
Insanity: Doing the same thing over and over again and expecting different results...

wjw

Hi wjw

an application written for mobile apps in Java using a MySQL database

This leaves open questions. Depending on how the application is partitioned, i.e. what runs where, and if changes can be made to server-side Java, if any.

If the app was developed with the Android SDK and it connects to a server where mySQL runs with no server-Side Java you just need a database connect:)

If there is server-side Java (there are various flavours ranging from "simple" to Enterprise Edition) there are severalways. It very much depends how it is implemented and if changes can be made to it.

Using one of the mentioned alternatives will likely lose you more than "some performance". I propose a different approach. You can easily expose Java classes as Web services and this can be integrated a lot easier!

Cheers

Harry

Much appreciated Harry! The web services approach is exactly along the lines I was thinking. Thanks for articulating that.

What I would hope to do is let Perl handle the entire web user interface(forms, instructions, ajax calls etc...), and for data entry/manipulation, simply hand the collected results to the Web Service as you pointed out. Thus hopefully excluding the already developed access to the DB.

As a result, the developers working with the main app(mobile) can modify as they wish without having to have updates to the Web front end unless there are schema additions or removals.

Again, as jeffa pointed out, it seems to make more sense to just do the whole thing in Java. On the other hand, I can imagine a scenario where the app developers may not want, or are unable, to expand their internal team and just want to outsource the web portion of the project, thus allowing them to focus completely on the mobile app. I don't know that this is the case, but it seems possible based on my experience with small companies.

Thanks again for the input!
...the majority is always wrong, and always the last to know about it...
Insanity: Doing the same thing over and over again and expecting different results...
wjw