David Illsley wrote:
I still think some kind of pluggability would be a good thing, as this
has come up for a number of scenarios (JAX-WS, building an ESB,
WS-RM). What you're describing is really a hack, and it doesn't
actually stop the mU code running in the engine. How about a form of
plugability at the level of a boolean on AxisConfiguration which can
turn off the built in mU code? It's clear from these discussions that
it's really easy to hack round the mU code. I can't see the harm in
making it easier and more effiecient for those who really want to do
it.
Hi David:
I'd really rather not look at it this way. I want the MU handling in
the Engine to be *flexible*, not *omittable*. A mechanism which lets
external components register QNames they are taking responsibility for
is fine (and I don't think of that as really "hacking around" the MU
code, just extending it). An easy mechanism to completely switch off
the MU checking is, IMHO, fraught with peril. :) Yes, you can screw up
either way, but I think putting in pluggability at the level you suggest
would make it easier.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
