What is superfluos here? I thought that the key-attribute attribute is there to distinguish between a
<server href=""/>
and a
<server host="" port=""/>
for example.
So I have defined in the first case key-attribute="href" and in the second case key-attribute="host". But exactly this causes the exception.
But without that he complains that there are two server-tags.
The key-attribute is to distinguish between:
<server href="a"/> <server href="b"/>
so a layer would look like
<server href="a" excalibur-configuration:merge="true" excalibur-configuration:key-attribute="href">
<!-- stuff to merge with a -->
</server>
... I wasn't thinking of an instance where you would have two peer elements that have different sets of attributes. If you want to create a testcase that illustrates what you want to do, I can modify the code to make it pass.
-pete
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
