Topics of MiniTalk

by Sylvain

The cocoon.xconf is really frightening, because it lists every component with every possible option. The result is that average (or even advanced) users don't even dare to touch it, except adding datasources. Here are a few ideas that could make it easier:

• Having sensible builtin defaults in every component (maybe it's already the case)
• Autopopulating selectors by "scanning" implementations existing in the classpath (natively provided by Fortress?)
• Expanding {...} expressions with a set of bootstrap input-modules to move away some deployment-time parameters in web.xml, external configuration files or system properties.
• Running modes: have conditional sections depending on a running mode (dev, debug, deployed, etc).
  
  

Additional comments:

• (yours here)
  
  

Outcome of the hackathon discussion:

(check back after monday 6th October)