Remy Maucherat wrote:
Bill Barker wrote:
"Remy Maucherat" <[EMAIL PROTECTED]> wrote in message
I don't know how to avoid it in a simple way without a hack. Bill,
any ideas ?
We're pretty consistant in our attribute names in server.xml, so while
it isn't the cleanest solution, it should work for us. How about
adding to Digester (depending on taste) either
setFakeAttributes(String [] names)
or
setFakeAttributes(List<String> names)
The second lets us hide the lookup in List.contains, the first makes
the caller simplier for a small list of exclusions. Then
Digester.addSetProperties can pass it on to the setPropertiesRule.
If this was for c-d, then we'd probably need:
setFakeAttributes(Map<Class, List<String>> names)
but that seems like overkill for our fork of Digester.
Yes, I think I'll try something like that.
It should be implemented now. I ended up using the slightly more complex
Map based version.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
