We have a web application created using struts 1.2.9. We migrated that application to weblogic 12c. Now I want to use Jdeveloper 12 IDE for our development. So I could use the integrated weblogic 12c server. But it looks like Jdeveloper 12 no longer supports struts I framework. I had to upload the tag libraries manually and I'm not able to run the application using the IDE "Run" play button.
Getting the following error when I tried to run the application.
The target struts-config.xml cannot be started because it is not a runnable target.
Has anyone come across a similar issue and managed to solve it?
Related
I am following https://www.baeldung.com/spring-rest-openapi-documentation
I am using IntelliJ community edition 2022.3.2 as my IDE.
How to launch the mentioned file http://localhost:8080/swagger-ui.html automatically on startup?
Is there any configuration option, or am I supposed to write some custom code to launch it on startup of the Spring Boot application? For now I have done the latter, but I am concerned that this is not the right approach. In some of my past projects, I have seen this page open up automatically.
Our developers currently use the IBM RAD 8.5 to develop web applications (No enterprise Java beans (No J2EE), use Spring framework). The server team is planning to upgrade WebSphere from version 8 to version 9. Last I checked in the servers tab, RAD 8.5 supports WAS version 8, 8.5, and 8.5 Liberty profile. See screenshot.
Is it possible to continue to develop in RAD 8.5, and deploy to WebSphere 9 in the server environment? What kind of snag would I expect to run into? e.g. Assemble the WAR file in RAD 8.5, and deploy the WAR file in WAS 9.
Would there be any problem I should anticipate in the deployment descriptor? e.g. files like web.xml and application.xml?
Moving forward, is it better to use other IDE to do software development if we are not planning to upgrade RAD 8.5 to a newer version? Would MyEclipse(variant of Eclipse with better server support) or Eclipse IDE for Java EE Developers (oxygen) suffice? Do I also need the liberty profile?
https://developer.ibm.com/wasdev/downloads/liberty-profile-using-eclipse/
What kind of issues should I be expecting? Or continue using RAD 8.5 would be a better option?
Here are some of the stackoverflow links I had checked already. There are pretty high level.
what-are-the-differences-when-deploying-on-tomcat-vs-websphere
can-a-war-file-be-deployed-on-any-server
Thanks.
In my experience I could not use RAD 8.5 to control a v9 server. I could not use Java 8 in RAD 8.5. I would not expect RAD 8.5 to know about the newer versions of JPA, JAX-RS and other things in v9. You could continue to develop jee6 apps on a v8.5 server and then move them manually to a v9 server.
Liberty is worth a look but is not completely interchangeable. Liberty has features that traditional does not (MicroProfile) and lacks some older things that traditional has (JAX-RPC).
You might check out the WebSphere Developer Tools for Eclipse that have support for traditional v9. They're not as full featured as RAD but might be enough. More info is at https://www.ibm.com/support/knowledgecenter/en/was_beta/com.ibm.websphere.wdt.doc/topics/wdt_overview.htm
Adding to the information provided by Bruce, IBM had introduced OpenLiberty where one can deploy the war file built with RAD. Deploying to other application server (e.g. tomcatEE
) is possible, but it would require some work. OpenLiberty should be closest to the IBM Websphere in terms of setup and architecture.
Here are some links that provide more information.
OpenLiberty
IBM announces Open Liberty, an open source runtime for Java microservices
Difference between OpenLiberty and Websphere Liberty
I have no experience in jBoss and can't make it work. I installed it with the installer version and I open up user.home\EAP-7.0.0\bin\standalone.bat and this is what the console looked like. Command froze so I could not copy the text so I took a screendump. Do anyone have a suggestion of how to make it work?
EDITED
I followed this guide
4.2. INSTALLING JBOSS DEVELOPER STUDIO AND RED HAT JBOSS EAP
with a installer jar-file and it created a EAP-7.0.0 folder but no folder or icon for the jBoss Developer Studio. What I can't find out is how to start jBoss Developer Studio.
Your EAP 7 started just fine. Its a clean start of the server without any exceptions. What do you expect ? If you deploy any applications and make changes to any configuration, you will see the console highlighting those messages as well as you can check the log files.
EAP-7.0.0\bin\standalone.bat is the script used to start JBoss EAP in standalone mode in windows OS and the attached screenshot shows that your server has started without any issues.
JBoss Developer Studio is an IDE similar to the eclipse. Did you follow all steps in the document? I would recommend you to redo installation by following all step of chapter 4.2 in the document mentioned. Once the installation is complete successfully you would be able to see application under programs.
I've been asked to get a web application running in WebSphere using RAD 8.0.1, which isn't my usual app.server or development environment.
I'm starting off simple, using the default Ajax Test Server, but from what I can see, the default for a Dynamic Web Application is Servlets 2.5. Is there something buried in the twisty little maze of config dialogs to set it to Servlets 3.0, or must I handle that manually?
IBM Websphere Application Server 8.0 supports Servlet 3.0
IBM Websphere Application Server versions 7.0 and 6.1 do not support it.
So you need to use version 8.0. If you are using Websphere Portal, then you have a problem.
IBM Websphere Portal runs on same version Application Server (though you can for instance run Portal 6.1 on WAS 7 - I ran into some problems with AJAX though). So you might be able to get Portal 7 to run on WAS 8. It's the only way in the short term.
What is the run-time environment that you use?
WebSphere 7.x does not support Servlets 3.0 and it would be supported only by WebSphere 8.0.
WebSphere 8.0 is still in beta.
Interestingly, wikipedia is a good site for the list of supported APIs by WAS.
http://en.wikipedia.org/wiki/IBM_WebSphere_Application_Server
I don't have a RAD 8 handy with me to assist but i would check and ensure that the run-time associated with the project does support Java EE 6 (and Servlets 3.0)
HTH
Manglu
Websphere Application Server 7 can support servlets 3.0 if you installed Fix Pack 7.0.0.37 or later.
That shall upgrade JDK from 1.5.x to 1.6.x. Also you need to install WebSphere Application Server V7 Feature Pack for Web 2.0 and Mobile V1.1
I have WebLogic 10.3 installed (Server, Workshop and Portal).
However, some of the legacy service applications are deployed on WebLogic 9.2.
I have noticed that after using Ant to build the service library, I get an EBJ stub named ABCD_be9p7l_EOImpl_1030_WLStub.class.
Building it from WebLogic 9.2 gives ABCD_be9p7l_EOImpl_922_WLStub.class.
My question is, if I deploy the 10.3 one in the 9.2 server, will there be any compatibility issues that will stop the services from running?
If there is, is there any way that I can use WebLogic 10.3 to build applications that run on 9.2?
Read "Compatibility Statement for Oracle® WebLogic Server 10g Release 3 (10.3)" document:
Oracle attempts to support binary and source-level compatibility between the current version of WebLogic Server and all versions as far back as 8.1 in the areas of persistent data, generated classes, and API compatibility. In some cases, it is impossible to avoid incompatibilities.
and "Upgrading WebLogic Application Environments" article:
Application environments that run with WebLogic Server 10.3 can interact with application environments built on WebLogic Server 7.0, 8.1, 9.x, or 10.0.
Most existing WebLogic Server applications can be run without modification in the new WebLogic Server 10.3 application environment. You should review the compatibility information described in WebLogic Server 10.3 Compatibility with Previous Releases to determine whether any feature changes affect the applications in your environment. If your application uses APIs that have been deprecated or removed, then you may encounter warnings or exceptions at run time.