Skip to end of metadata
Comment: Migrated to Confluence 4.0
Go to start of metadata

Web Tier Framework Revisions

I think the current plan is to move Continuum to a new web presentation framework, based on more mainstream technologies. WebWork/JSP seems to be the best way forward, to make sure developers don't have to learn a specialized/custom web tier before they can contribute presentation code.

Plan

Can we:

  • Move to the new presentation framework for a Continuum 1.0.2 build.

What We're Missing

What types of adapters, APIs, etc. will we need to develop in order to get WW/JSP in place?

evenisse: I don't think we need something in particular because we have all in DefaultContinuum and Webwork wil can use it. But I'm not sure it's a good idea to keep all the code in DefaultContinuum. I think it will be better to split it in some utility classes and to create some DAO classes with CRUD functions.

What we'll do

  • All pages will be written in JSP
  • Pages decoration will be done with SiteMesh
  • Skin will be written with webwork templating mechanism (in velocity) => Need to use only webwork jsp tags for html tags
Labels
  • None

2 Comments

Hide/Show Comments

  1. Nov 20, 2005

    Brett Porter

    I'd prefer that this be a "background process". No earlier than 1.1, and not a requirement for 1.1. We should start to setup the infrastructure and use it as we go for new work as I believe that is possible.

  2. Nov 29, 2005

    John Casey

    The thing that concerns me about making this a background process is it will create latent risk with fixing any sort of UI bug or adding even small UI features. Not to mention risks associated with having two web tiers functioning in parallel...