Its certainly possible that a future JAXB implementation would switch to a different way of generating code, making CodeModel obsolete. But nothing is stopping you from using the current version on newer JDKs, backward compatibility is taken very seriously by oracle and sun before. The code is open source so no one would be stopping you from fixing bugs either.
CodeModel probably won't get extended to support newer language features like Strings in switch in java 7 or lambda in java 8 unless these would be useful to the JAXB implementation.
发布评论
评论(1)
未来的 JAXB 实现当然有可能会切换到不同的代码生成方式,从而使 CodeModel 过时。但没有什么可以阻止你在较新的 JDK 上使用当前版本,以前 oracle 和 sun 非常重视向后兼容性。该代码是开源的,因此没有人会阻止您修复错误。
CodeModel 可能不会得到扩展以支持较新的语言功能,例如 java 7 中 switch 中的字符串或 java 8 中的 lambda,除非这些功能对 JAXB 实现有用。
Its certainly possible that a future JAXB implementation would switch to a different way of generating code, making CodeModel obsolete. But nothing is stopping you from using the current version on newer JDKs, backward compatibility is taken very seriously by oracle and sun before. The code is open source so no one would be stopping you from fixing bugs either.
CodeModel probably won't get extended to support newer language features like Strings in switch in java 7 or lambda in java 8 unless these would be useful to the JAXB implementation.