Why is j2midp superior to WAP? [Confused inspiration]

Why is j2midp superior to WAP?

J2midp addresses limitations of the limitations of WAP.

Developed through the Java Community process (JCP) program under the guidance of
Expert group composed of twenty companies representing the wireless industry
MIDP addresses programming issues most relevant to mobile clients, such as user interface,
Networking, persistent storage and application model.

Compared to WAP solutions, j2midp provides the following advantages.

Lower network usage and sever Load

In a WAP Solution, the server is responsible for generating display markup. This requires
A round-trip every time the interface changes. In contrast, a j2midp client's Interface
Is contained within the device, so it can operate even when disconnected. On occasions
When the devices does interact with the server, it incurs less network traffic, because
It downloads only application data, as opposed to application data plus Interface
Markup.

Better User Experience

WAP markup langauges such as WML are, by design, restricted in the types of interactions
They can offer. With the midp gui APIs, it is easy to implement customised Widgets
And event-handling, opening up unlimited possibilities for mobile client interfaces
That are easier and more interesting to use.

Why j2projects fail?