java Seam 框架有多受欢迎
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/30281/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
How Popular is the Seam Framework
提问by Eduardo Diaz
I'm using JBoss Seam Framework, but it's seems to me isn't very popular among java developers. I want to know how many java programmers here are using it, and in what kind of projects. Is as good as django, or RoR?
我正在使用 JBoss Seam 框架，但在我看来它在 Java 开发人员中并不是很流行。我想知道这里有多少java程序员在使用它，在什么样的项目中。与 django 或 RoR 一样好？
采纳答案by Peter Hilton
In our JBoss Seam in Action presentationat the Javapolis conference last year, my colleague and I said that 'Seam is the next Struts'. This needed some explanation, which I later wrote-up as Seam is the new Struts. Needless to say, we like Seam.
在去年 Javapolis 会议上的JBoss Seam in Action 演讲中，我和我的同事说“Seam 是下一个 Struts”。这需要一些解释，我后来写了作为Seam 是新的 Struts。不用说，我们喜欢 Seam。
One indication of Seam's popularity is the level of traffic on the Seam Users Forum.
Seam 受欢迎程度的一个指标是Seam 用户论坛上的流量水平。
回答by Peter Hilton
I have used JBoss Seam now for about a year and like it very much over Spring. Unfortunately, I don't use this at work, more for side projects and personal projects. For me, it saves me a lot of time developing new projects for clients. And, one big reason I use it primarily is, the tight integration with each layer and I never get any lazy load errors that I used to get with Spring (even after the filter and other hacks).
我已经使用 JBoss Seam 大约一年了，并且在 Spring 期间非常喜欢它。不幸的是，我不在工作中使用它，更多用于副项目和个人项目。对我来说，它为我节省了为客户开发新项目的大量时间。而且，我主要使用它的一个重要原因是，与每一层的紧密集成，我从来没有遇到过使用 Spring 时遇到的任何延迟加载错误（即使在过滤器和其他黑客之后）。
An equivalent Spring application would have much more boilerplate code within it to get stuff working. Spring does not integrate each layer very well, it more or less is a wrapper for a lot of different things, but doesn't glue itself together very well.
一个等效的 Spring 应用程序将在其中包含更多样板代码以使其正常工作。Spring 并没有很好地整合每一层，它或多或少是许多不同事物的包装器，但不能很好地将自身粘合在一起。
The other nice thing I like with Seam is they practice what they preach. Take a look at their website. Take a guess what it is running, hmm, a live example of their code. Seam Wiki, Seam Forums, etc. If you truly believe in your code, stand behind it. I would be happy to have their pager 24x7x365, I bet it rarely goes off.
我喜欢 Seam 的另一个好处是他们实践了他们所宣扬的东西。看看他们的网站。猜猜它正在运行什么，嗯，他们代码的一个活生生的例子。Seam Wiki、Seam 论坛等。如果您真的相信自己的代码，请支持它。我很乐意让他们的寻呼机 24x7x365，我敢打赌它很少会关闭。
While you write a lot less code, the learning curve is about twice as steep. The further I get in, the more I understand how to write good code. I would like to see more comments, but as far as coding style, it is well written.
虽然您编写的代码少得多，但学习曲线却是陡峭的两倍。我越深入，就越了解如何编写好的代码。我希望看到更多评论，但就编码风格而言，它写得很好。
On the negative side, just as any product you try to market, Seam was years after Spring had already become popular so Spring is by far still more popular. Search on Indeed and Seam only has a few hits. If you look on Spring, there are roughly 40k registered users, while Seam has about 7k.
不利的一面是，就像您尝试推销的任何产品一样，Seam 是在 Spring 流行多年之后才流行起来的，因此 Spring 仍然更受欢迎。在 Indeed 和 Seam 上搜索只有少数点击量。如果您查看 Spring，大约有 40k 注册用户，而 Seam 大约有 7k。
Depends on what is important to you, as a Java developer/engineer/programmer, you should be able to work with both technologies and chances are, you will most likely encounter a Spring application before a Seam one. Learn both and how to leverage both. If you use both properly and know the nuances and quirks of each, development becomes much easier whether you're using Spring or Seam.
取决于对您而言重要的是什么，作为 Java 开发人员/工程师/程序员，您应该能够使用这两种技术，而且很有可能，您很可能会在遇到 Seam 之前遇到 Spring 应用程序。了解两者以及如何利用两者。如果您正确使用两者并了解它们的细微差别和怪癖，那么无论您使用 Spring 还是 Seam，开发都会变得更加容易。
I don't agree with the statement, "Seam is the next Struts". Struts was a view technology whereas Seam integrates all layers. I will agree that it is a new concept like Struts and will bring the same impact to the Java community that Struts did. I don't think we'll see that until Java EE 6 and CDI become more popular, and of course Seam 3 is released.
我不同意“Seam 是下一个 Struts”的说法。Struts 是一种视图技术，而 Seam 集成了所有层。我同意这是一个像 Struts 一样的新概念，并将给 Java 社区带来与 Struts 相同的影响。我认为在 Java EE 6 和 CDI 变得更流行之前我们不会看到，当然，Seam 3 发布了。
Walter
沃尔特
回答by IAdapter
Seam is fixed JSF based on annotations. No more crappy XML. I used it at work.
Seam 是基于注解的固定 JSF。不再有蹩脚的 XML。我在工作中使用过。
回答by IAdapter
Hope this helps a little, but at my college our web applications course just got revamped. So now we are going the jsp, servlet, hibernate route with the second part of the course on mostly JBoss Seam. So who knows, it probably just needs time to grow in the community.
希望这会有所帮助，但在我的大学，我们的 Web 应用程序课程刚刚改进。所以现在我们将使用 jsp、servlet、hibernate 路线，课程的第二部分主要是 JBoss Seam。所以谁知道呢，它可能只需要时间在社区中成长。
回答by Markos Fragkakis
I like Seam, have been using it for the past year professionally.
我喜欢 Seam，过去一年一直在专业地使用它。
However, the question concerns its popularity. I can see the following indications that it is not very popular (at least in comparison to plain JSF or Spring):
然而，问题在于它的受欢迎程度。我可以看到以下迹象表明它不是很受欢迎（至少与普通的 JSF 或 Spring 相比）：
Its forum is very inactive (at least at this point, they are working hard on Seam 3). http://seamframework.org/Community/SeamCommunityForumSlightlyInactive
You can also take a look at its comparison with Spring in Google insights for search: http://www.google.com/insights/search/?hl=en-US#cat=732&q=seam%2Cspring&cmpt=q
I only know one other company here in Athens where they use it, and I know a handful of companies that use plain JSF, Struts or Spring (of course, Athens is not representative for all the world).
它的论坛非常不活跃（至少在这一点上，他们正在努力开发Seam 3）。http://seamframework.org/Community/SeamCommunityForumSlightlyInactive
您还可以在 Google 搜索洞察中查看它与 Spring 的比较：http: //www.google.com/insights/search/?hl=en-US#cat=732&q=seam%2Cspring&cmpt= q
我只知道雅典的另一家公司在那里使用它，而且我知道少数使用普通 JSF、Struts 或 Spring 的公司（当然，雅典并不代表全世界）。
回答by Leonardo
We have been using Seam for a while in huge projects. Easy to kick-off a new project, reverse engineering is very handy.
我们在大型项目中使用 Seam 已经有一段时间了。轻松启动一个新项目，逆向工程非常得心应手。
回答by ivans
I would say that seam is a rather popular framework, it has great documentation, a great and helpful community and a forum with many many questions and problems answered.
我会说seam是一个相当流行的框架，它有很好的文档，一个伟大而有用的社区和一个有许多问题和问题回答的论坛。
It should be popular among developers who use jsf beacuse it works great with jsf, but not only that... it fixes jsf in many ways (s:convertEntity tag, and unified component model are my favourite examples).
它应该在使用 jsf 的开发人员中很受欢迎，因为它与 jsf 配合得很好，但不仅如此……它以多种方式修复了 jsf（s:convertEntity 标记和统一组件模型是我最喜欢的例子）。
回答by ivans
It really works for us....JSF+EJB3.0 with the help of seam framework is really fantastic.But i have a question...why this is not becoming more popular for developing large scale application.I have seen that many are using other frameworks for developing large scale j2ee application.It seems to me that seam really helps the developers to build a j2ee application...but still ...why this but coming in?
它真的对我们有用......在seam框架的帮助下JSF+EJB3.0真的很棒。但我有一个问题......为什么这在开发大型应用程序时没有变得越来越流行。我见过很多正在使用其他框架来开发大型 j2ee 应用程序。在我看来，seam 确实有助于开发人员构建 j2ee 应用程序……但仍然……为什么会出现这种情况？
回答by Mbada
When Java was introduced in the 90s as oak the community did not embrace it because it was too powerful for its time and was appreciated later on and is now running the show. Seam will get popular soon. if not it can be rebranded just as oak to java.
当 Java 在 90 年代作为橡树被引入时，社区并没有接受它，因为它在当时太强大了，后来受到了赞赏，现在正在运行。Seam 很快就会流行起来。如果不是，它可以像橡木一样重新命名为 Java。
回答by Kevin Yang
I have been using Seam from Seam 1.2 since 2007 in mid-size and large projects, sometimes in small projects no more than 200 users. My main concern is the productivity. Although my team has already gained obvious productivity from Spring since 2005, for some tricky clients developers have to code javascripts which is time consuming and error-prone. Seam was really helpful in this scenario because at that time most developers in my team had no experience with JSF. Happy to see Seam being more popular.
自 2007 年以来，我一直在中型和大型项目中使用 Seam 1.2 中的 Seam，有时在不超过 200 个用户的小型项目中。我主要关心的是生产力。尽管自 2005 年以来我的团队已经从 Spring 获得了明显的生产力，但对于一些棘手的客户，开发人员必须编写 javascripts，这既耗时又容易出错。Seam 在这种情况下非常有用，因为当时我团队中的大多数开发人员都没有使用 JSF 的经验。很高兴看到 Seam 更受欢迎。
