Hi everyone,
For those who have built a web application using the standard MVC pattern
I'm sure you have found it can be quite a tedious and cumbersome solution.
The constant need to jump in and out of html/java and the messy process of
moving data between the model, the controller and the view
Well that particular project you referred its just a generic construction
set for Html or Xml. The toolkit I've proposed goes beyond that, my objects
actually have state and are true objects in the OO sense.
The toolkit does more than just abstract html construction via java
manipulation, if
Well yes like any solution there are strengths and weaknesses. You're
absolutely correct here, if you do need to change your html then you will
need to change your java code and recompile. But mind you the Jsp is only
one part of the overall solution (I'm talking in the traditional mvc
sense),
Hi August,
Your examples are very specific and are aimed where the traditional mvc
pattern would serve well. But there also many situations where having to
write a jsp, a bean and a controller just proves to be a very tedious and
cumbersome process. I know it, I've done it!
This toolkit is
