Re: [Springframework-developer] Component Centric Web Framework for Spring

[Seth L. <set...@gm...>]

Sounds like an interesting project.  Can you compare to Wicket
(http://wicket.sourceforge.net/) ?

The one concern I have is, how quick is it to test changes to the
code?  From the impression I get, if I want to make a change to a
page, I need to shut down the application and restart it so that the
ANT task can recompile the page classes?

IMHO, a really cutting edge Java web application framework would
require absolutely zero shutdown and restarts of either the servlet
container or the servlet context itself.  Do you happen to plan on
attacking the "constant redeploy" problem?

Also, not sure if it does already, but does the configuration support
sensible defaults, or conventions?  A really cutting edge Java web app
framework would be able to run with zero XML.

For instance, given your example:

<application>

=09<page id=3D"home" file=3D"home.html" springBean=3D"home" />

</application>

I would image the default rule would be: "convert home.html to 'home'
and find the matching bean by name".  In other words, don't make me
write the above XML when it's obvious what I am declaring. :)

Seth


On 3/24/06, Cristi PASCU <cri...@cr...> wrote:
> Hi everybody!
>
> My name is Cristian Pascu and I am developing an opensource project
> named "wedge" (http://wedge.sourceforge.net) which is a component
> centric web framework built on Spring.
> It is similar to Tapestry and aims to provide some features that are not
> yet available in Tapestry. Namely:
>         * better and easier integration with Spring.
>         * simple POJO classes behind clean xhtml pages. There is no need
> to extend specific framework classes. The classes are easy to test as
> they are easy to instantiate and configure.
>         * all page classes may be managed by Spring inversion of control
> container. This way, services from the business tier will be injected in
> the presentation tier.
>         * a simpler component/pages specification. There should be a
> single configuration file and not one for each component.
>         * the configuration of the application should be very simple,
> one xml file with few tags and attributes. Much of the configuration
> will be on the spring side.
>
> Most of these features are already implemented. There is still some work
> to do on the validation mechanism. The upload support is also missing
> but is not to hard to implement.
>
> But what differentiate the wedge framework from tapestry framework is
> that instead of using runtime reflection it follows the "code
> generation" paradigm. Let me be more specific: The connection between
> the template and the class behind it is made through an intermediary
> generated class that binds the two. Thus, the generated code "knows"
> exactly which is the structure of the template, that components to
> render, what classes to use and what methods to call at the right time.
> The generation is done with an ANT task each time before the application
> is started.
>
> If you have any thoughts on what I am trying to do, critics or advices,
> all are welcomed!
>
> Do you think that such a framework is needed?
> Do you think that my approach is a good one?
>
> Thank you very much!
>
> Cristian
>
>
> PS: There is not any release yet. You may check out the project from
> sourceforge: https://svn.sourceforge.net/svnroot/wedge
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=
ge
> that extends applications into web and mobile media. Attend the live webc=
ast
> and join the prime developer group breaking into this new coding territor=
y!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid=110944&bid$1720&dat=121642
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>