Which Seam framework version is supported in JBoss AS 7?
I am planning to use Seam2.2.2, is it compatible with Jboss AS 7?
Yes and no.
If you visualize yourself the timeline of Seam, the answer comes from alone:
Seam 2.x was created to ease development against Java EE 5 and to serve as an incubator for future standards, mainly Java EE 6 and JSF 2
Java EE 6 took the ideas from Seam 2 (and others) to specify CDI (and improve APIs like JSF)
Seam 3 brings new ideas to Java EE 6 and serves as an incubator for future standards, mainly Java EE 7 and JSF 2.x
Yes, Seam 2 is - more or less - compatible with JBoss AS 7. Why? Because Java EE 6 is downwards compatible with Java EE 5. But you will have to deal with some issues, like this and like that one. I just migrated a Seam 2.x application from JBoss AS 4 to JBoss AS 6, and it took me a good deal of a month.
No, don't use Seam 2 for a new project, not in 2011. CDI is so much more mature than Seam 2 bijection, JSF 2 is so much easier than JSF 1.2, that any kind of application development will simply be much more fun with Seam 3. And at the end, it's all about having fun at work, or?
I can tell about my experience : we recently migrated a seam 2.2.0 / jsf 1.2 / primefaces 1.1 / jpa 1.0 project on Jboss as 5.1 to seam 2.3.0 CR1 / jsf 2.1 / primefaces 3.4 / jpa 2.0 on Jboss as 7.1.
In fact the seam 2.3 branch was specifically developped to support jsf 2 and it "naturally" targets Jboss as 7.
Our application uses extensively the "Seam Application Framework" and the migration happened to be relatively straightforward, you can check this for instructions. In the other hand, as it already has been said above, for a new project there should be better alternatives.
Related
right now my app use 4.2 jboss with java 1.5.
I manage to build my app (EJB, jsf, hibernate, seam) with java 1.8, but i get some problems with running jboss 4.2 with java 1.8.
So I wonder, whether it is even possible or it will be better to switch to another version of jboss(with will be also complicate)?
Thank you for clarification.
So another question appear, if I use new jboss and java8 , Am I need to change hibernate (eg. I use hibernate-ejb 3.3.2ga), jsf, etc. to newer version? Application was build with java 8 with success.
You can't run JBoss EAP 4.2 on Java 1.8 (Or any other java newer than 1.6)
Use new version of JBoss EAP instead. This will give you better performance some cool new features and server will be easier to monitor and maintain.
Here is the link
I need to develop a presentation layer for an existing Java EE application running on JBoss AS 4.2.1.GA. I have been reading on JSF, Facelets and RichFaces and tried a few examples - some things worked but others didn't because of the limitations of library versions I used, considering the outdated JBoss.
Can someone recommend the direction I need to be heading to get this done as quickly as possible by using the mentioned server? By this I mean the Eclipse tool (WTP, JBoss Tools, ...), type of project, dependencies, ... Also, to shorten development time, maybe also use JRebel?
I know I would be better off using the latest server, but unfortunately it is not an option.
Also, I have installed JBoss Tools for Eclipse Indigo, but for creating RichFaces Project, it requires JBoss EAP 6 or AS 7.1.
I had created applications using JSF 1.2, RichFaces 3.3.3, JBoss Seam 2.0.2 (not required) for JBoss AS 4.2.2.GA. For development was used Eclipse (3.4/3.5) IDE for Java EE Developers. Version of Eclipse is not important. Yes, you need WTP. In my projects seam-gen was used for generating project skeleton. If you don't use Seam you can create Web project.
I am working with GlassFish 3.1.2.2 and I can not upgrade to 4 due to OS restrictions. I'm interested in upgrading JPA 2.0 to JPA 2.1 and JSF 2.1 to JSF 2.2 in GlassFish 3.1.2.2. How can I achieve this?
I can't speak for JPA, but for JSF it's a matter of replacing javax.faces.jar file in its /modules directory by the desired version. Don't forget to clean the GlassFish cache and work folders before deploying, because the older JSF version may still hang in there and then cause conflicts.
I can either install Tomcat or glassfish server in the production server inorder to deploy my JSF 2.0 project. Which from which versions of these servers are compatible with JSF 2.0? Please give suggestion.
I have developed with Mojarra 2.0.2, Facelets and PrimeFaces, Netbeans 6.8
In general you need at least a server that supports Servlet 2.5 or later for JSF 2.0 (found at coreservlets.com JSF 2.0 tutorial), e.g.:
Tomcat 6+
Glassfish 2.1+
Jetty 6+
Google App Engine
JBoss 5+
WebSphere 6+
WebLogic 9+
If not integrated, you then need jsf-api.jar and jsf-impl.jar for JSF 2.0
If you have a server that supports Java EE 6 (Glassfish 3, JBoss 6, WebLogic 11g) these jar's are already included.
JSF 2.0 uses version 2.5 of the servlet-api, which means it should be compatible with Tomcat version 6.0.x.
Sources:
http://javaserverfaces.java.net/nonav/rlnotes/2.0.0/releasenotes.html
http://tomcat.apache.org/whichversion.html
I have the WTP 3.1 plugin installed and have also installed the Glassfish v3 plugin. I am able to register my server.
When I create a dynamic web project, I can see that the maximum dynamic web module version available is 2.5. I then choose the default configuration for Glassfish v3 but, when I look at it JSF, it is not selected by default. When I select it, the maximum version available is 1.2.
I want to use JSF with facelets - does Eclipse support this? I can't seem to find anything helpful on the Eclipse WTP site.
Java EE 6 / JSF 2.0 is relatively new. Most tools are already ready, but Eclipse has to catch up it yet.
The status as far:
IntelliJ Ultimate Edition was early in this. Unfortunately not freeware. Note: the free Community Edition doesn't provide tools for much of Java EE, let alone JSF.
Netbeans 6.8 came a bit later almost full Java EE 6 support, including JSF 2.0.
Eclipse for Java EE planned to support Facelets in Galileo, but it was cancelled and postponed to the successor Helios which is currently in one of its latest Release Candidate stages been released at 24 July 2010. Helios for Java EE will ship with full fledged Java EE 6 support, including JSF 2.0.
As of now, it just works fine in Eclipse Ganymede/Galileo when you select JSF 1.2 and uses JSF 2.0 libraries. You'll only miss some code assistance which may be useful for JSF 2.0, but you can write code as good yourself.
Use Eclipse with JBoss Tools Plugin. It has support for JSF2 and CDI.
http://in.relation.to/14750.lace
Note, that you can do JSF 2.0 development in Eclipse, but not with as much tool support as might come later.
You can always edit xhtml files directly as XML-files (and have the namespaces registered), and have Glassfish deployments. I've done that, with stock Eclipse 3.5.2 Java EE edition, and the Glassfish plugin.
Have a read on http://weblogs.java.net/blog/2009/05/18/using-ide-write-jsf-20-app
It describe in details on how to setup your eclipse for jsf 2.0 development.