RoadmapLenya3.0

Options

A: Evolution

• Preserve backwards compatibility

B: Clean Cut, Reuse Architecture

1. Migrate to Cocoon 2.2
2. Replace content repository with JCR
3. Start with minimal core
4. If possible, replace home-grown stuff with out-of-the-box components (a lot has happened since our components have been built)
   • Identity management: no internal user storage (maybe proxies), SSO support (OpenID integration etc.)
   • Workflow engine
   • GUI framework (GWT, Dojo, ...)
5. Migrate modules step by step

C: Clean Cut, Reuse Experience

1. Reconsider all requirements thoroughly
2. Derive architectural constraints
3. Choose architecture
4. Reuse code where it makes sense

Requirements

• Automatic content migration

Architectural Constraints

• No changes to URL space and URL-document mapping required
• Workflow-driven content manipulation
• Access control on repository level - permissions assigned to content objects rather than URLs