WSF (Talk)

Document created by risicare1 on Aug 22, 2007
Version 1Show Document
  • View in full screen mode

Wicket, I suggest.

http://wicketframework.org/

With proper mark-up/logic separation, a POJO data model, and a refreshing lack of XML, Wicket makes developing web-apps in Java simple and enjoyable again. Swap the boilerplate, complex debugging and brittle code for powerful, reusable components written with plain Java and HTML.

It's V1.3.0 coming.






I started looking at feasibility of using Grails to provide required functionality.

Benefits of Grails:


  1. Groovy is a natural choice for scripting, but complied language, that can produce scalable applications.
    1. Can provide compiled execution
    2. Can execute user created script in controlled security context
    3. Draw on richness of Java
    4. Good XML, RSS, SOAP, REST support
  1. Grails provides all tools required for implementing framework fast
    1. URL mapping and manipulation tools enable user-friendly URLs
    2. Template and layout functionality can easily enable skins and personalised layouts
    3. Hibernate and Spring provide good base for applications

Risks and cons:


  1. Grails is young
  2. Use of Spring Web dictates how it interacts with Servlet container

JRuby + Rails


The team at Sun have done some great work on JRuby.
I know that Alfresco is Java and Groovy + Grails has a Java heritage, but reading through the WSF wiki goals I think JRuby better meets your needs.

Attachments

    Outcomes