J2EE 容器应该实现什么版本的 JSR？
J2EE 容器提供符合 JSR 公共审查版本而不是最终草案（甚至提议的最终草案）的实现是否可以接受？我不确定在这种情况下如何量化/限定“可接受”一词，但是说明实施是否足够的“黄金标准”是什么？是否需要完全符合TCK？
这或多或少是由于对 IBM WebSphere 6.1 的 Web 服务功能包中的 JAX-WS 2.0 实现感到失望 - 显然，如果 JAX-WS Web 服务具有使用 @BindingType 定义的 SOAP 1.2 绑定，则不会为 JAX-WS Web 服务生成 WSDL。注解。当我上次检查 JAX-WS 2.0 规范时，其中一项更改是消除了这种歧义（出现在第 3.8 节的公共审查中，但在拟议的最终草案中进行了澄清）。
Is it acceptable for a J2EE container to provide an implementation that complies with the public review version of a JSR, as opposed to the final draft (or even proposed final draft) ? I'm not sure on how to quantify/qualify the word 'acceptable' in this context, but what would be the 'gold standard' for stating that an implementation is adequate ? Is complete compliance with the TCK required ?
This is more or less born out of frustration with the JAX-WS 2.0 implementation in the Web Services Feature Pack for IBM WebSphere 6.1 - apparently, WSDLs are not generated for JAX-WS webservices if they have a SOAP 1.2 binding defined using the @BindingType annotation. When I last checked the JAX-WS 2.0 specification, one of the changes had removed this ambiguity (present in the public review in section 3.8, but clarified in the proposed final draft).
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
不幸的事实是，做用户“接受”的任何事情都是“可接受的”，而用户通常对此事没有任何发言权，因为某种原因而被绑定到特定的实现。
WebSphere 尤其以快速而宽松的规范而闻名（Google websphere jsp 问题< /a> 为例）；值得赞扬的是，IBM 他们通常迟早会解决这些问题（重点是稍后），但这对于此时此地并没有太大帮助。
The unfortunate truth is that it's "acceptable" to do whatever is "accepted" by users and users often don't have any say on the matter, being bound to a particular implementation for one reason or another.
WebSphere in particular is known for playing fast and loose with specs (Google websphere jsp problem for an example); to IBM's credit they usually fix those issues sooner or later (emphasis on later) but that's not much help for here and now.
是的……作为绝对最低限度。您还应该期望在 TCK 未涵盖的领域中遵守规范的文字和精神。
但假设您已经致力于使用某些特定的 J2EE 实现，我不确定这对您有何帮助。不幸的是，您无法强制软件供应商遵守相关标准或特定版本的标准。您最多能做的就是将业务转移到其他地方。
Yes ... as an absolute minimum. You should also expect compliance to the letter and spirit of the spec in areas that are not covered by the TCK.
But I'm not sure how this helps you, assuming that you are already committed to using some specific J2EE implementation. Unfortunately, there is nothing you can force a software supplier to conform with relevant standards, or particular versions of standards. The most you can do is take your business elsewhere.