Hi,
We have developped a small tool that permits to handle binding definitions that are split across multiple files, and that adds the possibility to define sort of templates that can be included in binding definitions in a quite seamless way. I would like to know if somebody is interested in it.
It is based on an XSLT stylesheet.
There is not much to say about splitting binding definitions across several files: it simply groups
all bindings and reorders the namespaces, formats and mapping definitions, and places the result into a single file.
As far as including is concerned, here is an example:
<binding>
<includes>
<structure id="S1" name="test" class="Test" .../>
</includes> <mapping id="M1" name="test2" class="Test2">
<structure name="class3" class="Class3".../>
<include-element ref="S1"/>
</mapping> <mapping name="class4" class="Class4">
<value name="sth" .../>
<include-content ref="M1"/>
</mapping>
</binding>The idea is
- the <includes> element is ignored (I mean, its content does not go directly into the resulting binding definition)
- any element can have an id attribute; an element with an id attribute can be included.
- it is possible to include a referenced element entirely (<include-element>), or only its content (<include-content>).
- includes can be nested to any level.
I find this system much more powerful than the actual abstract binding mechanism. But as I don't know what Dennis is planning as far as templatized bindings are concerned, I don't know if my system will still be very useful when beta4 is out.
Comments?
Guillaume Pothier
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
jibx-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jibx-users
