Hi!
> As we speak from different publishing framework, it may be of interest ot
note that quite many of these are already well advanced.
>
> Some of the Apache group:
> - Struts (MVC framework, http://jakarta.apache.org/struts/index.html)
Struts is cool, and is similar the work I am doing. However, mine is cleaner
and more flexible IMHO :-)
> - Cocoon I and the upcomping II (http://xml.apache.org/cocoon/index.html)
Cocoon has the right goal (separate control and view in MVC), but it is too
complex and requires XML and XSLT which are non-trivial technologies.
There's also seems to be a serious performance overhead with turning result
data into XML, and then "XSLT it" into HTML.
> - Jetspeed (portals, http://java.apache.org/jetspeed/site/overview.html)
> - Turbine (servlet based framework,
http://java.apache.org/turbine/index.html)
IMHO these are complete disasters. They are too large and complex, and ties
you into a framework that is quite large and bulky. They also do not
separate business logic and presentation in a very elegant way (the business
logic knows too much about how the result data is being used).
> It certainly exists tons of others ;)
Well, the ones you mentioned seem to be the most common ones. And overall
they're all horrible *IMHO* (please, no flame wars, this is just my opinion
based on what I managed to do myself in a couple of hours of coding).
I will flesh out the example I'm working on so you can see for yourself if
I'm talking BS or not.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
