FinishingFlow

The current status of the Flow implementation. Feel free to add your name if an issue is open

Issues to be solved before rc1

empty

Issues solved recently

• basic implementation of the FOM
  --> done (Christopher)
  
  
• get e.g. request parameter "xyz" using
  cocoon.request.xyz
  --> done (Christopher)
  
  
• implement getComponent( id )
  --> done (Reinhard/Christopher)
  

• implement releaseComponent( component )
  --> done (Reinhard)

• implement load( script )
  --> done (Christopher)
  
  
• sendPage( "internalOnlyPipeline", bizData )
  --> done (Sylvain)
  
• Implementation of the continuations object see http://wiki.cocoondev.org/Wiki.jsp?page=FOM_Continuation
  --> done (Christopher)
  
• discussion: Do we allow actions to wrap flow function calls?
  --> done (was also part of votings)
  
  
• move FOM to main trunk and make it the default flow implementation
  --> done (Christopher)
  
  
• move Petstore to main trunk (and use FOM)
  --> done (Reinhard)
  
  
• move JXForms to main trunk (and use FOM)
  --> done (Christopher)
  
  
• move the JXTemplateGenerator to main trunk (and use FOM)
  --> done (Christopher)
  
  
• sorting order of parameters
  http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=105732398423404&w=2
  --> done (Christopher)
  
  
• all flow examples have to use the FOM
  --> done (Reinhard)
  
  
• votings
  --> done results
  
  
• flow/session handling
  --> done http://archives.real-time.com/pipermail/cocoon-devel/2003-July/016957.html
  

Issues to be solved before release

• legacy.js
  provide access to input modules and actions using loadLegacyFunctions()
  (not absolutly necessary for the 14th but for release) --> open
  
• reorganize the docs and give the flow a more prominent
  position
  --> Stefano http://marc.theaimsgroup.com/?l=xml-cocoon-docs&m=105837473715122&w=2
  
• BUG: strange exceptions when requesting flow pages with JMeter (occurs only if FOM is used see http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=105714319527551&w=2
  --> discuessed on dev list
  
• test continuations expiration
  There has been a mail that there are some problems with it.
  

Issues to be solved before release (nice to have)

• raise exception if component is unreleased
  (not absolutly necessary for the 14th!)
  --> open
  
• Linotype has to use FOM
  --> open (Stefano) (as unstable block not necessary for rc1)
  
• Woody has to use FOM
  --> open (Bruno?) (as unstable block not necessary for rc1)
  

Issues for Cocoon 2.1.1 (or later)

• suport event handlers
  (see FOM_Cocoon for details)
  
• synch rhino-continuations with Rhino
  (GR)The current Rhino version is an old development one. Porting the continuation engine to the last version it's not an easy task, but should be pretty high priority oon the list. See http://marc.theaimsgroup.com/?t=105637688900023&r=1&w=2&n=13
  --> GR, CO
  
• Sitemap integration
  --> discussion (FlowSitemapIntegration)
  
• automagical lookup and release of stateful components in flows with continuations support

    
     function myFlow() {
     var c = cocoon.getComponent( "blabla" );
        c.doSomething();
        sendPageAndWait(...):
        c.doSomethingElse();
        sendPage();
     }