Reinhard Poetz wrote:
--- Daniel Fagerstrom <[EMAIL PROTECTED]> schrieb:
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.
This sounds like a workaround for now. Actually we
want to use the properties from block.xml, right?
That works allready, the above was a possible complement.
Another (related) question - see the XML below: Will
this scenario of differently configured blocks be
supported? (like in this example that blocks can use
different database connections)
<wiring
xmlns="http://apache.org/cocoon/blocks/wiring/1.0";>
<block id="core" location="core/"/>
<block id="test1id" location="test1/">
<mount path="/test1"/>
<connections>
<connection name="core" block="core"/>
<connection name="test2" block="test2id"/>
<connection name="test3" block="test3id"/>
</connections>
</block>
<block id="test2id" location="test2/">
<mount path="/test2"/>
<properties>
<property name="database-con" value="blahAAAA"/>
</properties>
</block>
<block id="test3id" location="test2/">
<mount path="/test3"/>
<properties>
<property name="database-con" value="blahBBBB"/>
</properties>
</block>
</wiring>
That should allready work AFAIK.
/Daniel
