From: "Martin van den Bemt" <[EMAIL PROTECTED]> > If I am not mistaking the only change that is need then is to change the > current setNameMapper(..) to setElementNameMapper(..). > Since the attributeNameMapper is already a NameMapper type ;)
Agreed. > The suggestion was merely a mind spin, that it maybe better to use an > AttributeNameMapper type, so it is more clear. That mind spin came from > the fact that I thought that attributes were always read, not caring > about naming rules.. Since the setAttributeNameMapper is pretty clear, I > don't think we can leave it simple. > I am using the HyphenatedNameMapper for my elements > and the DecapitalizeNameMapper for my attributes ;) Yes, both of type NameMapper. So all I meant was let XMLIntrospector have 2 properties, of type NameMapper, one for elements and one for attributes. > My renewed patch will be sent tonight (seems like it is working, but > didn't get to parse the complete xml file yet). > > BTW I am now manually testing the thing I have the deadline on, which > makes life a little bit less stressfull ;) Cool. James _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
