现在,我们已经标注在Java中,是xdoclet的遗产? [英] Now that we have annotations in java, is xdoclet legacy?

查看:127
本文介绍了现在,我们已经标注在Java中,是xdoclet的遗产?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我来翻过的XDoclet项目,看看它享有/ ED很高的人气。所以,问题是,现在我们已经在Java注解:就是xdoclet的传统

I came accross the xdoclet project and see it enjoys/ed high popularity. So the question is, now that we have annotations in java: is xdoclet legacy?

或者是有什么与XDoclet我没有看到/明白了。

Or is there something to xdoclet I didn't see/understand.

推荐答案

的XDoclet 是通过的JavaDoc注解实施 。可能与的XDoclet 来完成(以及更多)什么都可以用 JDK5 + 注释来完成。

XDoclet is an annotation implementation via JavaDoc. Anything that could be done with XDoclet (and much more) can be done with JDK5+ annotations.

一个明显的区别不过是,的XDoclet 无创的。也就是说,它并不需要你导入类到自己的code。如果你在自己的code。使用第三方Java注释,那么你当然不能没有第三方罐present建立你的code。这不是一个缺点,即XDoclet的患有。 (你可以把它看成一个缺点都没有。)

One obvious difference however is that XDoclet is non-invasive. That is, it doesn't require you to import classes into your own code. If you are using 3rd-party Java annotations in your own code, then of course you cannot build your code without the 3rd party jars present. This is not a drawback that XDoclet suffers from. (You may not see it as a drawback at all.)

当然,即使的XDoclet 可能是传统,我怀疑,对于已经严重依赖于它的大多数项目,就没有急于迁移到使用注释(格言:如果没坏,不解决它)

Of course, even though XDoclet may be legacy, I suspect that for most projects which have relied heavily on it, there will be no rush to migrate to using annotations (maxim: if it ain't broke, don't fix it).

这篇关于现在,我们已经标注在Java中,是xdoclet的遗产?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆