[Lenya Wiki] Update of "Lenya 3.0" by FlorentAndre

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification.

The "Lenya 3.0" page has been changed by FlorentAndre.
The comment on this change is: Copy text from 3.0 roadmap.
http://wiki.apache.org/lenya/Lenya%203.0?action=diff&rev1=6&rev2=7

--------------------------------------------------

  
  Useful reading and information have to be picked up from this documents :
  
-  * [[RoadmapLenya3.0]](Need to be reviewed and copy into another section, not really a roadmap IMO)
+  * [[RoadmapLenya3.0]]
   * [[WishlistLenya2.0]]
  
  Here comes some headings that have to be filled down. Headings and content are proposals, so don't hesitate to modify, suppress, etc...
@@ -128, +128 @@

  api have to be simple, understandable, etc... but it's not easy ! Let's discuss about it here.
  }}}
  
+ = Ideas to reuses =
+ 
+ * this ideas are from an old 3.0 roadmap.
+ * some of this ideas have to be reuse into this document : 
+ == Options ==
+ 
+ === A: Evolution ===
+  * Preserve backwards compatibility
+ 
+ === B: Clean Cut, Reuse Architecture ===
+  1. Migrate to Cocoon 2.2
+  1. Replace content repository with JCR
+  1. Start with minimal core
+  1. 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, ...)
+  1. Migrate modules step by step
+ 
+ === C: Clean Cut, Reuse Experience ===
+ 
+  1. Reconsider all requirements thoroughly
+  1. Derive architectural constraints
+  1. Choose architecture
+  1. 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
+