问题描述
我正在一个用BeansBinding编写一些代码的项目上开始工作.它似乎有效，但是我发现了这个可怕的帖子: http://weblogs.java.net/blog/fabriziogiudici/archive/2009/03/lets_fork_beans.html
I am starting work on a project that has some code written in BeansBinding. It seems to work, but I found this scary post: http://weblogs.java.net/blog/fabriziogiudici/archive/2009/03/lets_fork_beans.html
看来BeansBinding的开发已停止.为什么这个雄心勃勃的开发者不选择其他开发者停下来的地方呢?为什么需要分叉?BeansBinding是否存在一些严重的核心问题?
It appears that development on BeansBinding has stopped. Why wouldn't this ambitious developer just pick up where the other developers left off? Why is it necessary to fork? Are there some serious core issues with BeansBinding?
我还没有使用BetterBeansBinding.将来用BeansBinding编写的项目是否需要替换为"BetterBeansBinding"?BetterBeansBinding甚至与BeansBinding相似并且稳定吗?如果BeansBinding被视为遗弃软件"，那么BetterBeansBinding是否会有同样的命运?
I have not used the BetterBeansBinding yet. Will projects written in BeansBinding need to be replaced with "BetterBeansBinding" in the future? Is BetterBeansBinding even somewhat similar to BeansBinding and is it stable? If BeansBinding is seen as "abandonware" then will BetterBeansBinding have the same fate?
推荐答案
如果您碰巧遇到了bean绑定中的任何错误(大多数人没有)，也许您将被迫使用更好的beansbinding(他们可能有解决它).
If you happen to hit any the bugs in beans binding (most of the people don't) maybe you will be forced to use betterbeansbinding (where they may have fixed it).
BetterBeansBinding是beansbinding的直接替代品，它具有相同的api，因此可以将bettersbinding.jar替换为betterbeansbinding.jar是可以的.很稳定.
BetterBeansBinding in a drop-in replacement for beansbinding, it has the same api so it's ok to just replace the beansbinding.jar with the betterbeansbinding.jar. It's stable yes.
JSR-295本身被标记为非活动状态，因此可能是更好的bean绑定具有相同的命运.
JSR-295 itself was marked as inactive so it could be that better beans binding share the same fate.
但是考虑到bean绑定已于2007年停止并且人们仍在使用它(netbeans)这一事实，我认为您不应该害怕使用它.
But giving the fact that beans binding was stopped on 2007 and people still use it (netbeans) I don't think you should be scared to use it.
这篇关于bean绑定有什么问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！