>> Has there been a change to the jax-ws runtime that could be causing
>> this? As far as I know, the mex code hasn't changed in a long time.
>
> May be it is related to
>
> https://wsit.dev.java.net/issues/show_bug.cgi?id=232
Nice timing -- I was just checking my jax-ws email to send a note that
it's resolved. I think it is related to 232, because now the schema is
coming in a separate metadata section, and the test (by my own
suggestion) just assumed that there would only be one section with a
wsdl containing the schema.
So we're all set, thanks. I've suggested a fix for the test to allow for
the way the data is coming back now (which, as you know, is a valid way
for it to work).
Cheers,
Bobby