commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin van den Bemt <>
Subject [PATCH] Betwixt. setting namemapper for attributes.
Date Wed, 05 Jun 2002 15:18:06 GMT
Hi James,

Finally found the problem. The nameMapper is also used for attributes.. 
so if I have an xml file like
<PHYSICAL_SCHEMA autocreate="yes"/>

You end up with trouble ;).. Since autocreate will be mapped to the
attribute AUTOCREATE, which doesn't exist. 

So I added an extra nameMapper setter (setAttributeNameMapper), which
you can call if you want to use a different nameMapper for attributes.

I have chosen not to make a specific attributenamemapper Interface /
abstract class for simplicity and easier reuse of code.. 

The default is to use the normal NameMapper, so no backward
compatibility issues on this.

If you don't mind, I will make my testcases a little bit later.
(hopefully tonight, or else on sunday, since I am off sailing for a
couple of days..)
Hope you wil apply the patch however, ran all tests and it doesn't break
backward compatibility. 

Hope it is usefull for you too ;) 


View raw message