The professional, friendly Java community. 21,500 members and growing!

The Java Programming Forums are a community of Java programmers from all around the World. Our members have a wide range of skills and they all have one thing in common: A passion to learn and code Java. We invite beginner Java programmers right through to Java professionals to post here and share your knowledge. Become a part of the community, help others, expand your knowledge of Java and enjoy talking with like minded people. Registration is quick and best of all free. We look forward to meeting you.

Re: convert java EE to an androide app

I'm beginner to Java EE, I'm building a Java web app using frameworks as JSF, JPA and EJB and I want to convert the entire or just a part of the app to an android app. Any ideas?

These kinds of "conversions" are, according to me, very pointless and fictional. A Java EE application is a totally different thing from a native android application. Apart the language that is Java for both types of application, the only thing that may be eventually "portable" are classes for "beans" and business logic that don't have any connection/relation to the user interface.

But the overall architecture and user interface require a total rethinking.

Re: convert java EE to an androide app

Going off of andbin's comment, when I create large-scale programs where I intend to have a web GUI and companion Android app, I make my framework extremely modular.
I do this because Android does NOT fully implement the java JDK. There are many built-in java APIs which you will find are not accessible from Android (for example, the Swing framework just doesn't exist in the Android JDK).
So I create modular layers of projects based on functionality that can (and should) be shared by both the web GUI and Android app.

The WebFramework and the AndroidFramework would both have SharedFramework as a dependency. It is important that SharedFramework does not import any APIs which cannot be accessed by the AndroidFramework.
SharedFramework would have all the general business logic and functionality, while the WebFramework and the AndroidFramework have their more platform-dependent functionality.

I've found this is the best way to "port", because it means that if there is a required change to the business logic which will effect both the web and Android platforms, I can make that change in one place: the SharedFramework, and then redistribute both at the same time. This also means that the business logic and basic functionality will not be different depending on the platform.

NOTE TO NEW PEOPLE LOOKING FOR HELP ON FORUM:

When asking for help, please follow these guidelines to receive better and more prompt help:
1. Put your code in Java Tags. To do this, put [highlight=java] before your code and [/highlight] after your code.
2. Give full details of errors and provide us with as much information about the situation as possible.
3. Give us an example of what the output should look like when done correctly.

Join the Airline Management Simulation Game to manage your own airline against other users in a virtual recreation of the United States Airline Industry. For more details, visit: http://airlinegame.orgfree.com/