Felipe Curty do Rego Pinto wrote:
I vote JSF. It is in the J2EE standard, so many developers are studing... In
future version 2.0, it will bring components. For now, we can use Myfaces.
It's follow the standard and have great components.
Whichever framework is chosen, I highly recommend that Spring
(www.springframework.org) be used to tie all the pieces together. If
you haven't looked at or worked with Spring do so as soon as possible.
It is lightweight, flexible, and very powerful. Spring is an IOC
(Inversion of Control) and AOP (Aspect-Oriented Programming) Container
that allows you to inject dependencies into your code (database
connections, JMX managed session, etc.) that are declared externally via
XML and also to apply aspects to your code to satisfy cross-cutting
concerns like logging, persistence, and transactions. The end result is
that your source code only contains business logic and everything else
is applied externally at runtime. The result is powerful, flexible, and
very lightweight. A good friend of mine and brilliant technologist,
Rick Hightower, provides the following opinion piece:
http://www.sys-con.com/read/47735.htm
Assuming that we do decide to use Spring to wire the pieces together,
the flow control / MVC portion can be handled by any number of
technologies: JSF, Struts, SpringMVC, Tapestry, etc. My personal
preference is to use either JSF or SpringMVC to handle this. The
decision between the two comes down to whether we're looking for a
richer UI (JSF) or higher performance and more flexibility (SpringMVC).
The only other consideration is that JSF is "official" (JSR) and Spring
is just an open source project with no intention of pursuing JSR status.
-KG
Best regards,
Felipe
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: quarta-feira, 12 de outubro de 2005 06:45
To: [email protected]
Subject: Re: [magnolia-dev] ControlSuper confusing API
#: 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
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
