Hi Dan,
I'm open to correction on the security stuff, but I think we might still be OK
with the re-ordering approach even in the presence of whitespace, as the WS-Sec
in-interceptor (at least the WSS4J version anyway) also runs in the
PRE-PROTOCOL phase.
So as long as the CheckFaultIntercepto
WSCOMMONS-362 notes that NodeList is inherently non-thread-safe.
XmlSchema exposes a few APIs that accept and return NodeList's of
markup content for AppInfo and Documentation. Would anyone object to
changing those, incompatibly, to List (containing Nodes) for 1.4.3? I
might object myself, in which
Well I think we can safely declare a result here having received 14
endorsements (of which 12 were binding PMC-member votes), and no dissenting
voices.
So welcome to the team David!
There's a little bureaucracy required to get things squared away with the ASF,
Dan should be able to guide you
