Re: Cocoon development using blocks

Tue, 10 Jan 2006 02:00:45 -0800 

Reinhard Poetz wrote:


Leszek Gawron wrote:


Daniel Fagerstrom wrote:


Leszek Gawron skrev:



...
3. How are we going to distribute .xconf files? As they are also artifacts of some kind users shouldn't copy them into own project and modify but rather xpatch them as it is performed now. I know we have .xconf inclusion and multiple xconf files. Still there are some things that inclusion does not solve.
The .xconf files will be parametrized with the parts that users might be interested in changing, and a fixed .xconf will be included in the blocks jar.
So how do I add my own cforms convertor? The only way to do it now is xpatch.
How do I parametrize continuations manager. It's current configuration is rather incoherent: 

  <continuations-manager logger="flow.manager" time-to-live="3600000"
                         session-bound-continuations="false">
    <expirations-check type="periodic">
      <offset>180000</offset>
      <period>180000</period>
    </expirations-check>
  </continuations-manager>

(BTW type="periodic" is not even parsed by the component :))
We'll probably need to redesign the way some parts of our systems are configured. I'd love to use Carsten's idea of property files to parametrize components. After all almost every xml configuration can be expressed with a set of properties.
Blocks can be parameterized. I'm not sure how this will work together with Carsten's idea of property files.
Right now they don't. But if each block has a unique namespace, we probably could find some way to let the property org.mydomain.myblock.foo set the block parameter foo. 

/Daniel