Introduction to the main framework of J2ME and what are the main contents of J2ME technology

I feel like it's quicker to find a tutorial than to wait here for answers.

You just need to master J2SE to be proficient in this.

j2ee j2me is all side dishes.

The foundation knows no.

It's almost eliminated, just learn J2SE well.

In fact, those boxes in the WTK are the best reference.

You can study it and you'll find out when you've mastered these completely.

You're already a master at making a stupid game.

J2Me doesn't have a so-called framework.,If you want to make a game, you have to implement the game engine yourself.,IDE or something can choose NetBeans or Eclipse.,Other rulers are all universal.,When you really do it, you understand the Ling Mo Change.

Android is the operating system J2ME is just a part of the operation of the operating system.

The personal understanding of this thing of the framework is a routine model, the actual use depends on the specific situation of the project, there is no absolute good and bad in anything, you can maximize his performance, the most perfect and wonderful. For many people, s2sh is perfect, but there are still many people who use struts to attack.

I'll talk about the pros and cons of ss h or i.

ss=struts2,spring

h=hibernate

i=ibatis

Difference Between Ibatis and Hibernate:

Hibernate can be directly plugged through MyEclipse, without manually writing basic **, such as sessionfaction, datasource, etc., you can also brush classes through the built-in plug-ins, which is very convenient.

However, the usual database connections, etc., are only configured in the properties file.

ibatis is mainly used to configure the corresponding classes and fields of the database through XML files, as well as SQL statements. It's more troublesome.

But it's very easy to get started.

Struts, Spring, Hibernate and other smaller frameworks, MVC, etc.

A three-tier architecture is a design.

Patterns, i.e., MVC design patterns, are programming ideas that are not really frameworks.

MVC design pattern, M is the model that is, the business logic layer, all the business logic is in the model layer, and the new model class generates objects in the servlet or action in struts for business logic operations.

v is the view layer, which is used to display the interface, mainly using servlets and jsp to generate jsp pages that can be seen to display information.

c is the control layer, which controls the jump direction after the operation of each business logic, which is the configuration file.

I don't know what the three-layer architecture you are referring to is the three-layer JSP UI BL?