I'm trying to deploy an EJB 3 EAR project to WebSphere 7.
From RSA 8.0 I select the EAR file. When I select the EAR project > run as > Server > WAS7 I get the following error:
"the server does not support version 6.0 of the J2EE Enterprise application specification"
I changed my JRE/JDK to 1.5 in RSA, but the same thing happens. Is it a specific jar which causes this>
Java EE versions (J2EE 1.3, J2EE 1.4, Java EE 5, Java EE 6) are not the same like JRE/JDK version, this are two different things.
JRE/JDK is about the language, compiler and the java core frameworks.
J2EE/Java EE is about high level frameworks like EJB, JPA, JSF, CDI....
WebSphere Application Server 7 supports (only) Java EE 5 but not Java EE 6.
So you need to build a Java EE 5 application, reducing JRE/JDK from 6 to 5 is not enough, you also need to build a Java EE 5 EAR, without usage of any of the great Java EE 6 features.
So if it is only for your own, then I recommend to use GlassFish v3 instead, it has Java EE 6 support.
Related
I have recently upgraded a java maven project from JDK 8 to JDK 17 as well as changed IDEs from Netbeans 13 to Netbeans 16.
The project builds but when I go to run I get errors about the java server faces.
When I look at the project properties -> Frameworks -> JavaServer Faces the libaries are blank.
Is this an issue with Netbeans 16 or am I missing something?
If I open the same project in Netbeans 13 it has JavaServer Faces library entries.
I have tried to update the JavaServer faces library's in maven, the JDK 17 and the tried to add a differnt version of JSF via maven into the project, but the proejct frameworks remain blank .
Our application needs to support Tomcat 10.
We are migrating the code to Jakarka EE 9, but due to HazelCast we are blocked.
When can we expect the HazelCast jakarta EE migration??
Details:
We are evaluating to support Tomcat 10 in our product. To start it, we initially try to use Servlet 5.0 spec as Tomcat 10 supports Servlet 5.0 specification.
The Servlet 5.0 version migrated the classes to Jakarta.servlet.* from javax.servlet.. So, most of our java code have been migrated to Jakarta EE9.
But, in the middle we come to know that the HazelCast versions not compatible with Jakarta EE.
The internal classes of HazelCast still references to javax.servlet. from Servlet 3.0 specification.
So as a result, we got compile time issues as well.
Does the HazelCast compatible with Tomcat 10??
I want to migrate an application from Wildfly 8 to the latest Wildfly 18. The web application uses the following frameworks: hibernate 3, seam 2.2, JSF 1.2, and Richfaces 3.3.3. Since hibernate 3 isn't supported anymore in Wildfly, we need to migrate to hibernate 4 which isn't compatible with Seam 2.2. Thus, we have to migrate to Seam 2.3 and this leads to migrating to JSF 2.3 (Wildfly modules) and to Richfaces 4.
My project is an ear that contains inside it a war folder.
For JSF, I am using the supported module by Wildfly both com.sun.faces.impl and javax.faces.api. I also added jsf-facelets-1.1.15.jar as a jar under web-inf/lib.
For hibernate, I included the following jars in my ear: hibernate-commons-annotations-4.0.5.Final.jar, hibernate-core-4.3.11.Final.jar, and hibernate-entitymanager-4.3.11.Final.jar.
For seam, I included the seam jars: jboss-seam.jar, jboss-seam-debug.jar, ...
For Richfaces, I included the following libraries under the war folder: richfaces-a4j-4.5.17.Final.jar, richfaces-core-4.5.17.Final.jar, and richfaces-rich-4.5.17.Final.jar. I also included their dependencies.
I am still getting this error which I am not able to debug: Unsupported Operation Exception.
Did anyone encountered this issue ? And do you know if Seam 2.3 is still supported by the latest Wildfly especially that on Seam documentation, they gave the project examples on Jboss As 7?
Thank you for your help.
The migration you are trying to achieve will result in a non-supported environment as well.
From http://seamframework.org/
Seam Moving Forward
As many of you may be aware, there have been a number of changes
within Seam over the past year. Here is a quick highlight of the
changes and how they may affect you and your application.
Seam 2
Seam 2.2 targets JBoss AS 5 and 6 as well as JBoss Enterprise
Application Platform 5 - Java EE 5 based architecture Seam 2.3 targets
Java EE 6 capabilities such as JSF2 and JPA2 on the JBoss Enterprise
Application Platform 6 - Seam 2.3 also supports RichFaces 4 which is
also available for commercial support via Web Framework Kit. If you
are looking for the long-term support with a service level agreement
of Seam 2.2 and/or Seam 2.3 then please contact us at
http://www.redhat.com/contact/sales.html Seam 2.3 is part of Web
Framework Kit, included as part of the JBoss Enterprise Application
Platform subscription .
Seam 2.3 was released in September 2012. This is an update to the Seam
2 code base to make it compatible with Jave EE 6. It runs well on
JBoss AS 7.
Seam 3
Active development of Seam 3 has been halted by Red Hat. Many projects
have moved over to Apache DeltaSpike , and others have been absorbed
into different projects. Please see the below table for information
about where the functionality from each module has gone and how you
can participate.
So no, it does not support WildFly 18 (Java EE 8)
Richfaces is 'dead' (sunset) for 4 years now. https://developer.jboss.org/wiki/RichFacesEnd-Of-LifeQuestionsAnswers
JSF 2.x has facelets built-in, so no need to include them. (Causes problems even)
Wildfly 18 has JPA2 built-in so no need to include hibernate manually (Might cause problems even)
Also read https://docs.jboss.org/seam/2.3.0.Final/reference/en-US/html/migration23.html
Switching to using
PrimeFaces (fully html 5, css3 etc compliant)
JPA2
CDI (with Deltaspike)
OmniFaces
OptimusFaces
is a way better thing to do (Although JSF is 'old' compared to e.t.c. Angular it is still modern when combined with the above technologies and more stable).
We have application running JSF 1.1. Until these days we were using Java 6 deployed in WAS 7, now we are migrating to WAS 8.5 with Java 8 as runtime. Please advise where JSF 1.1 is supported with combo of Java8 with WAS 8.5.
Which version of JBoss AS supports Java EE 6 (specifically JSF2.0)?
None supports Java EE 6 fully yet. This may take some months. But JSF 2.0 in turn is backwards compatible with Servlet 2.5. This means that you can just use JBoss AS 4.2 or newer for this.
AS 6.0 will support Java EE 6. Currently nearing Milestone 2. If you want to try JSF 2, it works fine in the current trunk.
Following the instructions at http://aaron.ajexperience.com/2010/10/11/jboss-5-with-jsf-2-on-a-per-app-basis/ might let you use JSF 2 on JBoss 5.0.1 GA if you're using Eclipse.
Currently none and could take a while. Only Glassfish is supporting Java EE 6 right now