I am a little confused why the line of questioning regarding putting tomcat/jboss on android came up? Tomcat/Jboss/et all are server based platforms, quite large and are for handling services from clients. Your phone would be a client, and while you can run a background service..it's not quite the same thing as service web requests that jboss/tomcat/et all would handle. Sure.. you could in theory do this..but why would you have clients contact an android phone server? You'd need an ip/dns name to reach it in the first place which I don't even know if that is possible. As a few others said and you agreed.. definitely not something to do. If you were absolutely going to do this, then take a look at Jetty.. it's a capable web/servlet server that is very small.
If anything, I'd look at using SMS or email as the "server" and put out a listener on one of those services the phone provides for you, and then do some code to filter the incoming messages/emails. Maybe I a missing something in the OP as to why you were considering tomcat/jboss on the phone? However, if you are trying to figure out if you can just take any exectuable app like jboss/tomcat and run it as is on the phone..the answer is no. The Android framework would require at a bare minimum an Activity of some sort.. from there you could launch a service and then with some work get it to run. Likewise for other libraries that have executable code... let's say a Swing app, you would still have to redo the UI to work under Android, as it's a different set of UI apis for Android. If you had a library that does unzipping, or an image codec, you could make use of those, most likely with no changes unless they have some native/JNI stuff in them.. but even then I don't know for sure that you wouldn't run in to some issues. They could for example utilize some JDK code that isn't supported on the Dalvik jvm as it's not a full J2SE implementation. Swing code, I think applet code, Corba, stuff like that I don't believe exists in the Android SDK. On Mon, Jan 11, 2010 at 11:53 AM, JFrog <jeremiah.paul.sna...@gmail.com>wrote: > > I suppose the answer you are looking for is this: you will have to run > > Tomcat as a service on the Android. > > I'll get the chance to analyze the service structure of the Android > SDK within the short future. Things will start falling into place > over time and you answer is probably > suited to a response that I was expecting. Thanks F. Weiss. > > > Putting Tomcat on Android would be akin to attaching a snowplow > blade to > > a dachshund. > > I agree, that would not be that useful of a solution and wouldn't > consider it, although there are some great advantages for having > mobile > databases for people out in the field. > > > Yeah Tomcat is way, way too big to fit on Android. JBoss will > > probably fit on future Android devices somewhere around 2035. :-) > > Technology is moving along quite quick, but yeah, I assumed that it > wasn't as simple as pumping java applications through a conversion > tool and then voila! > These were realistically just examples. In the commercial world why > would someone want to have an expensive handheld data system when they > can just access a database online through the internet medium or via a > mobile phone service. > > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en >
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
