#: Magnolia Dev changed the world a bit at a time by saying on 10/12/2005
10:22 AM :#
Philipp Bracher wrote:
This was mainly the reason to move to a better and standardized
framework.
Philipp Bracher
what do you mean by "move to a better and standardized framework"?
Is this about the plan to migrate to a component based web framework?
Yep I am.
Philipp Bracher
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
Have you any particular framework under consideration (Wicket,
Tapestry,JSF...). I'm asking this becouse of fact that most of
frameworks have MVC model based on one core servlet handling requests
and Magnolia has one already. Do we need frameworks with 1:1
corespondence between Controler (POJO class) and View (JSP), like SOFIA
framework have? (search for SOFIA: Salmon, pretty old framework but, I
can say... "magnolia compliant" in some way)
Kliment Simoncev
I would say that there are a few component-based frameworks outthere that may be considered. I am
thinking here about:
- WebWork (http://www.opensymphony.com/webwork)
- Tapestry (http://jakarta.apache.org/tapestry/)
- Wicket (http://wicket.sourceforge.net/)
- JSF
My personal preferences are going in the WebWork and Wicket direction as their addoption curve is
not so complex.
./alex
--
.w( the_mindstorm )p.
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
