I'm attempting to define a server in the Eclipse (Oxygen) Server view. My project was not visible in the list of resources so per the following answer:
Cannot add a project to a tomcat server in eclipse
I configured project facets as follows:
Dynamic Web Module: 4.0
Java: 1.8
JavaScript 1.0
This made the the project visible when I tried again to define the server but I can't add it because "Tomcat version 8.5 only supports J2EE 1.2, 1.3, 1.4, and Java EE 5, 6, and 7 Web modules". This answer:
Tomcat version 7.0 only supports J2EE 1.2, 1.3, 1.4, and Java EE 5 and 6 Web modules
makes some suggestions for Tomcat 6 and 7 but I can't get it working for 8 (also don't seem to be able to back out of the facet configuration, though I haven't tried deleting it in .settings yet).
Thanks in advance for suggestions.
Related
Few years back, I develop a web application using Java 1.7, SpringFramework 4.1.1.RELEASE and Hibernate 3.6.10.Final. This webapp is running on Tomcat 7.0.4 at the time.
Now, I planning to upgrade and compile everything using OpenJDK 19, and Tomcat 10.1.
How do I know which version to use in my pom.xml (Maven) so that theres no error after compilation and during runtime.
WHat should I do first?
Using the latest Eclipse and I have downloaded both Tomcat 10.1 and OpenJDK 19.
I've set the Java Compiler to openJDK 19 and added both JRE System Library and Server Runtime in the build path.
I have also added some more jar file to fix issues in Marker tab but I encountered error during starting up application.
Tomcat 10.1 uses Servlet API 6.0 which is now part of Jakarta EE. As part of the move from Java EE to Jakarta EE, the packages in javax.servlet.* are moved to jakarta.servlet.* since the error you are getting.
If your target platform is Tomcat 10.1, you should move to Spring Framework 6.
Check the migration guide
we are migrating from WAS 8 to WAS 9 and WAS9 is providing MyFaces 2.2 but we would like to override with MyFaces following jars
myfaces-extcdi-core-api-1.0.5.jar
myfaces-extcdi-core-impl-1.0.5.jar
myfaces-extcdi-jsf20-module-api-1.0.5.jar
myfaces-extcdi-jsf20-module-impl-1.0.5.jar
myfaces-extcdi-message-module-api-1.0.5.jar
myfaces-extcdi-message-module-impl-1.0.5.jar
basically we don't need WAS provided MyFaces , when I can uninstall myfaces on WAS 9 server, I see the MyFaces jars "Plugins" folder.
removing jars from plugins folder is not working
any suggestions please
The MyFaces JSF implementation provided with WAS 9 cannot be uninstalled. You should not remove any jars from plugins. In WAS versions 8.0 and 8.5.5 an application option was provided to select between SunRI and MyFaces - however in WAS 9 only MyFaces 2.2 is provided, so there is no such configuration option.
IBM has a documentation page for configuring JSF. Once you've determined the correct MyFaces libraries to use, you'll want to bundle those libraries (as well as the correct dependencies) into an isolated shared library.
I have installed the Weblogic 12c server and I want to add it to a project in Netbeans 11. When I select "add server" from server instance, the Weblogic server option is not displayed
I expected to see the option as shown in the following link https://www.oracle.com/webfolder/technetwork/tutorials/obe/java/wls_12c_netbeans_install/wls_12c_netbeans_install.html
I was able to connect the plugin for weblogic from netbeans version 8.2.
You must copy the plug-in files from the netbeans 8.2 directory to the netbeans 11 directory.
Files of a plug-in:
...\plugins\servers\enterprise\modules\org-netbeans-modules-j2ee-weblogic9.jar
...\plugins\servers\enterprise\config\Modules\org-netbeans-modules-j2ee-weblogic9.xml
...\plugins\servers\enterprise\update_tracking\org-netbeans-modules-j2ee-weblogic9.xml
...\plugins\servers\enterprise\update_tracking\org-netbeans-modules-weblogic-common.xml
Checked on versions 11, 11.1, 11.2.
Update.
Second method
The plugin can be compiled from sources.
Plugin sources here:
https://github.com/apache/netbeans/tree/master/contrib/j2ee.weblogic9
But you need to build all netbeans project. Build command:
ant all
The resulting .nbm file can then be imported in NetBeans (Tools -> Plugins -> Downloaded -> Add Plugin)
Discussion of the problem here:
https://issues.apache.org/jira/browse/NETBEANS-2476
Compiled nbm plugin file:
https://issues.apache.org/jira/secure/attachment/12991973/org-netbeans-modules-j2ee-weblogic9.nbm
Checked on versions 12.x
From what i can tell only Netbeans versions 7.2, 7.3, 7.4, 8.0 can work with weblogic as of now. Also the guide you are following is using a pre Apache Netbeans version. I would recommend switching to one of the following Netbeans versions. Download the All bundle or EE.
Netbeans 8.0
Netbeans 7.4
https://netbeans.apache.org/kb/docs/web/jsf-jpa-weblogic.html
Unfortunately Apache NetBeans 11.0 does not currently support the addition or use of a WebLogic server. See open Apache NetBeans Bug Report 2476: Netbeans 11 EE Support Weblogic Server
I don't know for sure, but I suspect that this is a legal problem is related to licensing issues rather than any technical obstacles. The absence of licensing on Apache NetBeans 11.0 also impacts other important products such as Hibernate (NETBEANS-2719 Resolve Hibernate Support), and Wildfly (NETBEANS-2415
Bring back support for WildFly server).
There are licensing issues because Apache assumed ownership of NetBeans releases from Oracle last year.
Also, because WebLogic was supported "out of the box" in NetBeans 8.2 there is no old WebLogic plugin available for use on Apache NetBeans 11.0.
Your options are:
Regress NetBeans to use the most recent NetBeans release which does support WebLogic: Oracle NetBeans 8.2. Note that this means you cannot develop using Java EE 8, nor use any JDK version > 8.
Stick with Apache NetBeans 11.0, and instead of WebLogic use one of the four application servers which it formally supports "out of the box": Payara, Glassfish, Apache Tomcat and Apache TomEE.
Install your WebLogic server outside of Apache NetBeans 11.0, and deploy your NetBeans web applications to that external server.
I'm starting a new project and considering moving to Java 8 already, since newest Spring Framework 4.0 supports it, and it's not so long until final release this march.
Currently we are using STS 3.4 (Eclipse 4.3.1 based) and I have installed latest JDK8 and Java 8 (BETA) support. Simple projects seems to find themselves at home with Java 8, but not UI project (Dynamic Web Module 3.0, the one deployed on server). I'm getting error that compiler version (1.8 BETA) doesn't match installed project facet "Java" (1.7). And there is no such option "1.8" in "Java" project facet...
Have anybody succeeded running UI project with Java 8?
Thanks!
Have you tried to install WTP's org.eclipse.jst.common.fproj.enablement.jdt.feature.patch from here?
http://download.eclipse.org/webtools/patches/drops/R3.5.2/P-3.5.2-20140329045715/repository
You might also want support for Java 8 in Maven, PDE, and JDT.
For those features, use these sites:
Maven (M2E) 1.4.1 (org.eclipse.m2e.feature) http://download.eclipse.org/technology/m2e/releases/1.4/1.4.1.20140328-1905
JDT & PDE Feature patches : http://download.eclipse.org/eclipse/updates/4.3-P-builds/
If you happen to be a fan of JBoss Tools, it's coming directly to JBoss Central:
https://issues.jboss.org/browse/JBIDE-17002
Can someone please explain to me the difference in the EAR versions.
Is it tied to the JDK version 1.4, 5 and 6?
Thanks.
It is not JDK version. It is J2EE/Java EE version.
It is asking you which J2EE/Java EE version the ear format (deployment descriptor etc) should adhere to: J2EE 1.2 or 1.3 or 1.4 or Java EE 5 or Java EE 6.
Application servers publish their compliance levels. And some application servers generally support older ear versions as well. For e.g. WebSphere 6.x is J2EE 1.4 compliant but it can still run 1.3 ear version.
enter link description hereWhat application server and version are you looking to ultimately deploy to? You would want the ear to match the level of compliance the target application server is. For example, Oracle 10.1.3.5 Is J2EE 1.4 while JBoss 7 is Java EE 6.0 compliant.
Wikipedia and others attempt to track what each vendor's compliance level is.