The future of JBoss Seam

At the JavaOne meeting, Pierre Fricke, the JBoss product director, did not talk about a merger with Red Hat. He talked about the first release of JBoss JBoss seam supporting the new Java EE5, and he talked about the future of JBoss seam and Ajax and that JBoss would join the NetBeans community.

Can you make a clear positioning for jboss seam? Is it a lightweight web development framework?

Pierre Fricke: No, it's more than that. JBoss seam is more than a Web application framework, and it is a further simplification of EE5. In EE5, you still have to write a lot of code to build the EJB3 model on the Java Server faces model. Also, you do not have a meta model for the workflow. Therefore, you have to build a lot of different models to complete all the applications. What we're basically doing is building more integrated EJB3 and Java Server Faces, then working with Jbpel[java Business process Execution Language] (workflow tools in the Java environment, and XML The BPEL in the Web service environment is different) collaborate together. Therefore, you can complete the page flow and automate process type processing through the program framework.

How does JBoss seam and spring compare?

Fricke:spring is one of the more things people talk about in this field. Spring is a simplified, lightweight model, and ours is, of course, lightweight and fairly simple. But spring is a type of stateless application, and jboss seam can do stateless applications, and can do stateful applications that can do transactional applications and workflow applications. In fact, we build richer types of mainstream applications, we go farther than spring, and the architecture that handles these types of scenarios is completely different. So, while we have all the features of lightweight Web application frameworks and are simple to program, our models are more powerful.

How does JBoss seam manipulate Ajax?

Fricke: Now, you can use JBoss seam to do a lot of interactive applications, but we still have some work to do to determine how much Ajax can add to existing tools. We haven't finished the work yet. Therefore, this is a standard compatibility or model-compatible thing. But I don't think we're ready for the discussion of Ajax in JBoss seam. It still needs to be weighed, but it does add a lot of functionality to the interactive application. Now, you need to look at the value of Ajax, not the value, and then decide what to do next. If it makes sense, we certainly will not do it. But we think the JBoss seam programming model has a long way to go in understanding the connotation of Web2.0, and how to make more robust, transactional, stateful and interactive applications.

What do you think Web2.0 is?

Fricke: I think it's just a term name for this new, more interactive application, and it's the progress of the web environment. At the JavaOne conference, JBoss announces that you will join the NetBeans open source community. What makes you choose NetBeans rather than eclipse? Fricke: We didn't choose Eclipse. We just add NetBeans to our community and we join the NetBeans community. Therefore, this is not a two-choice thing. I want to emphasize that eclipse is also our strategy. The JBoss IDE is based on Eclipse, and the IDE's contribution is derived from the Eclipse plug-in. So, eclipse is still important. And NetBeans is just as important. The technology it uses is exquisite, especially in terms of dealing with Web services. We are an open community, we welcome everyone, the more open tools the better. So I believe we can bring in an jboss ecosystem and open it up for both Eclipse and NetBeans developers to use. This is a big win for the good.

Turn from: http://developer.51cto.com/art/200906/129267.htm