| MAP | PageMixer Documents > Motivation [ <| 1| 2| > ] |
JSP is one of solutions to develop system based on Web computing, and is certainly easy way at early period of development. But the larger the amount of artifacts becomes, the more expensive the cost of ones shown below becomes.
To execute code embedded in JSP, you must execute it in Servlet environment. And it decreases testability of server side processing. For example:
"Shopping basket" page may have not only "Shopping basket" function but also "Login" for not-logged in user, and it is natural for you to want to test each separately.
Sometime it is difficult on client side.
On client side, HTTP response or HTML as part of it are all the materials to examine correctness of server side processing, and they are not good to be examined programatically.
Because JSP framework needs code embedding, you must adjust JSP files at each merges of design and processing, if they are developped parallelly.
And you must do it manually in most cases even if "diff3" UNIX command, or other tools may assit it.
XMLC is one of solution for weak points of JSP shown as former section. But some requirements are not satisfied.
XMLC represents HTML page as "DOM tree", so you must know how to operate it.
XMLC also provides utilities for easy access to "DOM node" identified by specified ID, but it does not seem to be usefull enough (at least for me).
XMLC has performance problem at points shown as below:
It is represented as "DOM tree", and consists of over 100 Java objects.
XMLC renders HTML page by traversing of "DOM tree", which consists of many Java objects and may need intermediate "String".
In conclusion, I noticed that I want the framework which takes a middle position between JSP and XMLC.
And I also noticed that I must develop it by myself.
| MAP | PageMixer Documents > Motivation [ <| 1| 2| > ] |