Hi Sanjiva!
So I think we should carefully review, but keep the idea.
I'm not against a longer term fully general solution but I am opposed to
putting it into 1.3. This is a significant new feature added without
recent discussion and I request that it be removed at least for now. The
original issue can be handled with handlers as Jeff has already replied.
So we're not going to support <soap:header> in 1.3 either then - or at
least not completely, in that if someone actually sends us one of the
headers they specified in the WSDL with MU switched on, we'll barf?
(Trying hard to avoid using negative numbers in emails as those appear
unpopular ;-).)
:)
If you're vetoing a commit (which it sounds like you are?), fire away
with the -1s! However... I'm not entirely sure that "adding a feature
without discussion" is sufficient technical justification for a -1,
though. If we were doing review-then-commit, sure, but we're doing
commit-then-review. What do you think?
Not sure exactly what the right thing here is, but I think I'd prefer to
leave it in in some form rather than having JAXWS rely on a
Handler-based mechanism....
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
