No, the original WSDL threw that exception in JBoss, but it worked fine on a standalone JAX-WS client using the reference implementation. I guess it isn't really JBoss's fault that it doesn't work since the WSDL is invalid, but I would really appreciate a better error message instead of a NullPointerException. I guess wsconsume could simply stop the client generation if the WSDL is invalid, or the JBossXS runtime could give me a message that the schema doesn't make sense etc.
Andre