禁用 SOAP 架构验证、JAX-WS 和 JAXB，如何？
我从 Java 代码中执行的几个先前工作的 SOAP 调用出乎意料地给出了“DefaultValidationEventHandler：[ERROR]：意外元素...”。
它正在抱怨响应对象。但有一些事情；它一直工作正常，我没有更改模式或 EJB 或调用者代码，我在端口上没有模式验证功能，并且响应对我来说看起来很好。抱怨的是客户端。服务器成功执行请求，没有注释。
我认为我的 Eclipse 环境可能出现故障。
有没有办法禁用来自服务或端口对象的响应的客户端模式验证？
Out of the blue several previously working SOAP calls I do from Java code give "DefaultValidationEventHandler: [ERROR]: unexpected element...".
It is complaining about about the response object. A few things though; it had been working fine, I did not change the schema or the EJB, or the caller code, I do no have a scheme validation feature on the port, and the response looks just fine to me. It is the client side that is complaining. The server successfully executes the request without comment.
I think my Eclipse environment may be malfunction.
Is there a way to disable client side schema validation of the response from the service or port object?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我弄清楚了，正如我怀疑的那样，它是 Eclipse（赫利俄斯）。事实证明，如果 Java EE 视角和/或任何企业项目出现任何问题，Eclipse 将悄悄地停止重建。
当我删除构建/类下的所有内容时，我发现了这一点，然后什么都不会运行。一个不相关的项目被指向不再有效的服务器配置文件。
这如何导致我所看到的行为尚不清楚。如果知道如何禁用验证仍然会很高兴。默认情况下它应该关闭，但事实并非如此。
I figured this out and it was Eclipse (Helios) as I suspected. It turns out that if anything is incorrect with the Java EE perspective and/or any enterprise projects, Eclipse will quietly stop rebuilding things.
I found this out when I deleted everything under build/classes, and then nothing would run. An unrelated project was pointed at a no longer valid server profile.
How this resulted in the behavior I saw is unknown. And it would still be nice to know how to disable validation. It is supposed to off by default, but that but is not.