GWT - 没有 WC3 XML DOM 实现？我有什么选择？
我最近开始使用 GWT 来测试它作为下一版本 XML 编辑器应用程序的可能解决方案。
我立即意识到的一件事是，用于处理 XML 的 GWT 类（例如 com.google.gwt.xml.client.Document）不符合 WC3。主要是它们缺少像 createElementNS 这样的方法，
我知道他们这样做是为了兼容性，但是对于任何严肃的 XML 应用程序来说，使用命名空间是必须的。
所以我决定扩展 GWT 类并添加缺少的方法。像这样的东西：
import com.google.gwt.xml.client.impl.DocumentImpl;
public class Document extends DocumentImpl implements com.google.gwt.xml.client.Document {
public Element createElementNS(String ns, String localName)
{
....SOME JNSI ACTION HERE....
}
}
但显然 DocumentImpl 在它自己的包之外使用是不可见的，所以我很快就陷入了必须自己实现所有 DOM 方法的情况。
我真的不想这样做，有人有建议吗？
谢谢，
凯西
I recently started working with GWT to test it as a possible solution for the next version of our XML editor application.
One thing I realized right away was that the GWT classes for working with XML (like com.google.gwt.xml.client.Document) were not WC3 compliant. Mainly they lack methods like createElementNS
I understand that they did this for compatibility, but working with namespaces is a must for any serious XML application.
So I decided that I would just extend the GWT class and add the lacking methods. Something like this:
import com.google.gwt.xml.client.impl.DocumentImpl;
public class Document extends DocumentImpl implements com.google.gwt.xml.client.Document {
public Element createElementNS(String ns, String localName)
{
....SOME JNSI ACTION HERE....
}
}
But apparently DocumentImpl is not visible to be used outside its own package, so I am quickly in a situation where I start to have to implement all the DOM methods myself.
I really would prefer not to do this, does anyone have suggestions?
Thanks,
Casey
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我们通过调用 Javascript 并访问底层 Javascript DOM 的设施来完成一些扩展。但您很快就会开始遇到浏览器依赖性，并意识到 GWT 故意忽略了其中一些功能，因为它们很难以跨浏览器的方式实现。他们给你最低公分母（我的意思当然是最高公因数......）是有充分理由的。
We've done some extensions by calling out to Javascript and accessing facilities of the underlying Javascript DOM. But you quickly start hitting browser dependencies, and realising that GWT deliberately left out some of these features because they are quite difficult to implement in a way that works cross-browser. They give you the lowest common denominator (by which I mean of course the highest common factor...) for a good reason.