Details
-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
0
-
0%
Description
Some protocols (e.g. RELAY2 or FORK) need additional configuration, which is usually defined in a separate XML file, e.g.
<FORK config="/home/bela/fork-stacks.xml"/>
File fork-stacks.xml is:
<fork-stacks xmlns="fork-stacks"> <fork-stack id="counter"> <config> <COUNTER bypass_bundling="true"/> <COMPRESS/> </config> </fork-stack> <fork-stack id="locking"> <config> <CENTRAL_LOCK num_backups="2"/> </config> </fork-stack> </fork-stacks>
It would be nice to be able to optionally define such additional configuration inline, e.g.
<FORK> <fork-stacks xmlns="fork-stacks"> <fork-stack id="counter"> <config> <COUNTER bypass_bundling="true"/> <COMPRESS/> </config> </fork-stack> <fork-stack id="locking"> <config> <CENTRAL_LOCK num_backups="2"/> </config> </fork-stack> </fork-stacks> </FORK>
As the schema for config files is generated, we would have to able to tell the generator (XMLSchemaGenerator) to include a schema fragment defined by any protocol.
A schema fragment could be defined via an annotation, e.g. @IncludeSchema(schema="fork-stacks.xsd".
Investigate whether this is feasible.
Attachments
Issue Links
- relates to
-
JGRP-1827 Forked channel requires udp.xml file
-
- Resolved
-
