Hi all,

we have a web app based on Wicket, Tomcat 7 etc. and one of our
customers has a native Windows only app which is about to be replaced
now to 1. support Android as well, 2. add some missing features and 3.
provide some more modern GUI and such. The two most interesting things
for that replacement from my point of view are that the new app needs
to be able to work totally offline and that its current and some of
the new features contains things the customer already asked for the
Wicket-web app we've created as well.

Working offline is a hard requirement, so we can't just use the Wicket
web app as it is. But because features are clearly overlapping we
don't want to maintain a very comparable feature set with two
different technologies for years to come. Our customer totally agrees
with that and sees the functional overlapping as well.

So, is there already any experience or suggestions about or "down
votes" of an approach were one would embed some servlet container in
an Android app and provide the frontend using Wicket, HTML, JS and
CSS? This shouldn't be too much of a problem with Windows desktops,
but a completely different thing for Android.

I've found some posts about Jetty and Tomcat regarding this, which
don't look very promising.

But how about Wicket itself? Maybe someone already tried or knows it's
impossible because of the Android API or Dalvik or such.

Any thoughts welcome, thanks!

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail: [email protected]
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to