简体   繁体   English

Seam框架有多受欢迎

[英]How Popular is the Seam Framework

I'm using JBoss Seam Framework, but it's seems to me isn't very popular among java developers. 我正在使用JBoss Seam Framework,但在我看来,它在java开发人员中并不是很受欢迎。 I want to know how many java programmers here are using it, and in what kind of projects. 我想知道有多少java程序员在使用它,以及在什么样的项目中。 Is as good as django, or RoR? 和django一样好,还是RoR?

In our JBoss Seam in Action presentation at the Javapolis conference last year, my colleague and I said that 'Seam is the next Struts'. 在我们去年Javapolis会议上的JBoss Seam in Action演示中,我的同事和我说'Seam是下一个Struts'。 This needed some explanation, which I later wrote-up as Seam is the new Struts . 这需要一些解释,我后来写了,因为Seam是新的Struts Needless to say, we like Seam. 不用说,我们喜欢Seam。

One indication of Seam's popularity is the level of traffic on the Seam Users Forum . Seam受欢迎程度的一个迹象是Seam用户论坛的流量水平。

I have used JBoss Seam now for about a year and like it very much over Spring. 我现在已经使用JBoss Seam大约一年了,并且非常喜欢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). 而且,我主要使用它的一个重要原因是,与每个层的紧密集成,我从来没有得到任何我曾经用Spring获得的延迟加载错误(即使在过滤器和其他黑客之后)。

An equivalent Spring application would have much more boilerplate code within it to get stuff working. 一个等效的Spring应用程序将在其中包含更多的样板代码以使工作正常。 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没有很好地集成每一层,它或多或少是很多不同东西的包装,但不能很好地粘合在一起。

The other nice thing I like with Seam is they practice what they preach. 我喜欢Seam的另一个好处是他们练习他们所宣扬的东西。 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. Seam Wiki,Seam Forums等。如果您真的相信您的代码,请站在它背后。 I would be happy to have their pager 24x7x365, I bet it rarely goes off. 我很乐意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. 从消极方面来说,就像你试图推向市场的任何产品一样,Seam是在Spring已经流行多年之后的几年,所以Spring到目前为止仍然更受欢迎。 Search on Indeed and Seam only has a few hits. 搜索确实和Seam只有一些点击。 If you look on Spring, there are roughly 40k registered users, while Seam has about 7k. 如果你看看Spring,大约有4万注册用户,而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. 取决于对您来说重要的事情,作为Java开发人员/工程师/程序员,您应该能够使用这两种技术并且很有可能,您很可能在Seam之前遇到Spring应用程序。 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. 如果您正确使用它们并了解每个的细微差别和怪癖,无论您使用的是Spring还是Seam,开发都会变得更加容易。

I don't agree with the statement, "Seam is the next Struts". 我不同意这句话,“Seam是下一个Struts”。 Struts was a view technology whereas Seam integrates all layers. Struts是一种视图技术,而Seam则集成了所有层。 I will agree that it is a new concept like Struts and will bring the same impact to the Java community that Struts did. 我同意这是一个像Struts这样的新概念,它将为Struts带来的Java社区带来同样的影响。 I don't think we'll see that until Java EE 6 and CDI become more popular, and of course Seam 3 is released. 在Java EE 6和CDI变得更受欢迎之前,我认为我们不会看到这一点,当然Seam 3也已发布。

Walter 沃尔特

Seam is fixed JSF based on annotations. Seam是基于注释修复的JSF。 No more crappy XML. 没有更糟糕的XML。 I used it at work. 我在工作中使用它。

Hope this helps a little, but at my college our web applications course just got revamped. 希望这有点帮助,但在我的大学,我们的Web应用程序课程刚刚进行了改进。 So now we are going the jsp, servlet, hibernate route with the second part of the course on mostly JBoss Seam. 所以现在我们将使用jsp,servlet,hibernate路由,其中​​第二部分主要是JBoss Seam。 So who knows, it probably just needs time to grow in the community. 所以谁知道,它可能只需要时间在社区中成长。

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相比):

  1. Its forum is very inactive (at least at this point, they are working hard on Seam 3). 它的论坛非常不活跃(至少在这一点上,他们正在努力研究Seam 3)。 http://seamframework.org/Community/SeamCommunityForumSlightlyInactive http://seamframework.org/Community/SeamCommunityForumSlightlyInactive

  2. 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 您还可以查看其与Google在Google搜索洞察中的比较: http//www.google.com/insights/search/?hl = zh-CN&gt = 732&q = seam%2Cspring&cmpt = q

  3. 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). 我只知道在雅典的另一家公司,他们使用它,我知道有少数公司使用普通的JSF,Struts或Spring(当然,雅典并不代表全世界)。

We have been using Seam for a while in huge projects. 我们已经在大型项目中使用了Seam一段时间。 Easy to kick-off a new project, reverse engineering is very handy. 易于启动新项目,逆向工程非常方便。

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. 我会说接缝是一个相当流行的框架,它有很好的文档,一个伟大而有用的社区和一个有许多问题和问题的论坛。

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 beacuse的开发人员中很受欢迎,它与jsf配合得很好,但不仅如此......它以多种方式修复了jsf(s:convertEntity标签,统一组件模型是我最喜欢的例子)。

它真的对我们有用.... JSF + EJB3.0在接缝框架的帮助下真的太棒了。但我有一个问题......为什么这对于开发大规模应用程序并不是越来越流行。我见过很多正在使用其他框架来开发大规模的j2ee应用程序。在我看来,接缝确实有助于开发人员构建一个j2ee应用程序......但仍然......为什么这样但是进来?

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. 当Java在90年代作为橡树被引入时,社区并没有接受它,因为它的时间太强大,后来被欣赏,现在正在运行该节目。 Seam will get popular soon. Seam很快就会流行起来。 if not it can be rebranded just as oak to java. 如果不是它可以像橡树一样重新命名为java。

Seam已于2012年停产。但是, Apache DeltaSpike是Seam的现代版本,该项目得到了积极维护,甚至还获得了2014年Duke选择奖。

I have used JBoss Seam on two commercial projects for two different clients. 我在两个不同客户的两个商业项目中使用了JBoss Seam。 Yet JBoss Seam is still a new approach to developing JSF Web Applications. 然而,JBoss Seam仍然是开发JSF Web应用程序的新方法。 One measure is the results from a Indeed Job Search. 一项衡量标准是“确实找工作”的结果。

Indeed Job Search 确实是求职

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. 自2007年以来,我一直在使用Seam 1.2中的Seam中型和大型项目,有时在小型项目中不超过200个用户。 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. 虽然我的团队自2005年以来已经从Spring获得了明显的生产力,但对于一些棘手的客户端,开发人员必须编写javascripts,这既费时又容易出错。 Seam was really helpful in this scenario because at that time most developers in my team had no experience with JSF. Seam在这种情况下非常有用,因为那时我团队中的大多数开发人员都没有使用过JSF的经验。 Happy to see Seam being more popular. 很高兴看到Seam更受欢迎。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM