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.
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
In eclipse ,I am trying to upgrade my JPA from 1.0 to 2.0 (EJB project). I have made changes in the library and using eclipselink also but when I am again creating a project it is not giving an option of JPA 2 in faclets to select
any one have some idea whats the problem
It will depend on the version of Eclipse, and the weblogic plugin (OEPE) you are using. Without the correct connectors Eclipse is only aware that WebLogic server can run JPA1.0.
Perhaps try the latest version of OEPE pack here and point it at your workspace.
You also need to make sure the version of WebLogic you are using supports JPA2- you have tagged the question as weblogic 10.x which only supports JPA2.0 in 10.3.4 and later, and may require you to patch weblogic to enable the support.
I am working with GlassFish 3.1.2.2 (I can not upgrade to 4 due to OS restrictions).
I'm interested in upgrading JPA 2.0 to JPA 2.1 GlassFish 3.1.2.2. How can I achieve this?
This is most likely not possible at all. JPA 2.1 is part of EE 7 and therefore not fully integrated with EE 6 GF 3.1.2.2.
Did you try just replacing the EclipseLink and JPA jar files in Glassfish?
It will probably work, but if you use managed persistence units they will not expose any JPA 2.1 API, you would need to unwrap the EntiyManager to access these.
I'm using Hibernate 4.3.8 (requires JPA 2.1) with Glassfish 3.1.2.2.
Note: I'm not using any services provided by glassfish. All the libraries I use are in the WEB-INF/lib.
1 - Override all JPA classes (package javax.persistence) in glassfish/modules/javax.persistence.jar with JPA 2.1 version. You should not replace the entire JAR, only override the classes. This JAR has an OSGI manifest and other classes that must remain there.
2 - Remove all javassist classes (package javasssist) from glassfish/modules/weld-osgi-bundle.jar. This solves a possible incompatibility if you are using Hibernate.
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.
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