Hi,
>And why would that be interesting or preferable or whatever?
because Wicket doesn't need servlets actually: Without the JEE baggage
you can keep your App smaller.
> mean that the frontend needs adoption for both different environments
All JEE related APIs are hidden behind Wicket specific classes and
interfaces (e.g. WebResponse), so there should be nothing to adapt in
the application itself.
Have fun
Sven
On 21.06.2015 11:06, Thorsten Schöning wrote:
Guten Tag Sven Meier,
am Samstag, 20. Juni 2015 um 20:18 schrieben Sie:
there seem to be different solutions already, why do you think they are
not promising?
https://github.com/jetty-project/i-jetty
The commit history doesn't look very active to me and I've read that
Tomcat and newer versions of Jetty rely on JMX, which shall be a no go
on Android. On SO where some unanswered questions about Tomcat on
Android as well. But I'm just at the start of my research and didn't
try anything myself yet.
Actually it would be interesting to just skip all servlet stuff and just
use an HTTP server:
https://github.com/NanoHttpd/nanohttpd
And why would that be interesting or preferable or whatever? Besides
the fact that it might be the only working solution at all, of course. ;-)
I guess it might be faster and such, but would mean that the frontend
needs adoption for both different environments, executing within a
servlet container or not. That's exactly what I would like to avoid as
much as possible.
Mit freundlichen Grüßen,
Thorsten Schöning
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
