On Dec 12, 2007, at 7:55 AM, Daniel Kulp wrote:
On Wednesday 12 December 2007, Vespa, Anthony J wrote:
I would be interested in this as well for Aegis bindings - it does
not
make some of the JS libraries out there too happy.
That is why doing it at the interceptor level is ideal. It would be
completely independent of the databinding. Heck, you would be
able to
feed it a DOMSource if using a Provider<Source> type thing and the
namespaces would get stripped out as well.
I'm not sure this can be done with an interceptor. I'd guess that,
client that expects messages to be namespace free are unlikely to
send messages with the proper namespaces in the first place. When
aegis sees the xml without namespaces, it isn't going match nested
elements in the BeanType class to the xml elements because it matches
on qname.
From what I have seen of the BeanType code, think that you can make
aegis expect namespace free nested elements using a new TypeCreater
which creates BeanTypes with no namespace expectations. This is how
the StructType works.
Now that I think about it, I bet the javascript libraries are
expecting soap encoding which doesn't have namespace qualified nested
elements.
-dain
