Ok, this was an issue because some internal jax-ws ri classes moved to
the istack workspace. The problem had actually already been corrected
in XWSS but the latest jar hadn't been integrated into WSIT. This was
made clear becuase the bleedingedge tests had better results than the
non-bleedingedge tests (and no instances of this particular failure)
I've integrated the newer xwss3.0 build to fix this.
And Thanks! to Kohsuke for indentifying what had happened to
XMLStreamException2.
regards,
Ken
Ken Hofsass wrote:
> The WSIT E2E local tests are failing (I think) as a results of
> integrating jaxws-ri #1886 or saaj-ri #197
>
> One that is missing and causing numerous failures is
> 'com/sun/xml/ws/util/exception/XMLStreamException2'
>
> Where does that come from? Is it a mistake that it disappeared or
> something that needs downstream code to change?
>
>
> thanks,
> Ken
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
>