Can I avoid redeployment of a project in WebLogic, if I only change JSPs?

deployment issues in weblogic server
deployment issues in weblogic server 12c
weblogic admin console page cannot be displayed
weblogic the configuration for is still being loaded
"weblogic + deployment failed state"
weblogic issues
weblogic admin console url not opening
weblogic begin callback dump

I have a project that runs inside the WebLogic server. 80 % of changes I do to the code affect JSP files only (not the class files). Those JSP files contain the frontend logic.

Whenever I change the JSP page, I need to do the following steps to see my changes:

  1. mvn install inside the source directory.
  2. Redeploy the application in WebLogic Admin Console ("Deployments", "Update").

Is it possible to avoid these two steps, if the only thing I change are JSP files (I don't touch Java files therefore, no class files are modified)?

Note that the application in question is set up in WebLogic so that it reads the directory with the class files (myProject/target), not a WAR file.

I have no definite information whether or not JRebel supports WebLogic. Its only alternative known to me, DCEVM, does not support WebLogic according to the last statement here.

Update 1 (02.05.2018 15:23 MSK): Changing




in myProject/src/main/webapp/WEB-INF/weblogic.xml didn't help. When I deploy the application, then make a change to a JSP file, then run mvn install, the changes do not take effect.

There is page-check-seconds properties in weblogic.xml (beside others). Take a look at "weblogic.xml"

WebLogic Server Known and Resolved Issues, For information about new and changed functionality in WebLogic Server 10.0, at this point results in an attempt to load the last JSP file in the completed assistant. Therefore, in an Enterprise application, you can only apply security policies to When you partially redeploy a single module from a set of inter-​dependent  I have a project that runs inside the WebLogic server. 80 % of changes I do to the code affect JSP files only (not the class files). Those JSP files contain the frontend logic. Whenever I change t

If you run in dev mode and not prod wls will redeploy each time a jsp changes at source

Redeploying Applications in a Production Environment, Oracle® Fusion Middleware Deploying Applications to Oracle WebLogic Server WebLogic Server uses the in-place redeployment strategy when performing Partial redeployment can replace either static files in an application, or entire files in a running Web application, such as graphics, static HTML pages, and JSPs. Once that’s done, without WebLogic running, deploy your project to WebLogic and inspect what files are copied to the deployment. You can easily do this with the Browse button on the Deployment Manager dialog or externally. I was hoping that if ME pre-compiled all my jsps they wouldn’t have to be re-compiled by weblogic at run-time.

No, for several reasons. JSPs have to be compiled. They are not simple html pages. They are also cached by the server. You most definitely have to redeploy the project.

Hot deployment and dynamic reloading, You can make various changes to applications and their modules without file so it has the new components or modules and then redeploy the EAR file. servlets, and JSP files) to a running server without having to stop the reloads JSP files only when the IBM extension jspReloadingEnabled in the  In addition, you can specify optional WebLogic Server XML deployment descriptors to configure WebLogic-specific behavior for handling the deployment. WebLogic Server deployment descriptors enable you to maintain the portability of the original J2EE module while utilizing features only available in WebLogic Server.

Run/Debug Configuration: WebLogic Server, WebLogic Server run/debug configurations let you deploy and debug your applications Note that JavaScript debugging is available only for Firefox and Google Chrome. The application artifact is rebuilt and redeployed. Specify what IntelliJ IDEA should do when you switch from the IDE to a different  To avoid recompiling your JSPs each time the server restarts and when you target additional servers, precompile them using weblogic.appc and place them in the WEB-INF/classes folder and archive them in a.war file.

How to configure hot deploy in Eclipse –, In this tutorial, we will show you how to configure Eclipse debugger to support hot deploy, hot swap or hot code replace without restarting the Server, this speed Assume a simple Spring MVC web project is deployed via the to support “hot deploy” resources, for example : JSP, XML and properties files. Before you can deploy your application, you must have a successful build completed. The following topic explains the basic concepts of deploying and debugging Workshop applications to WebLogic Server running in development mode. Development Mode. Weblogic Server can be started in one of two modes: development or production mode.

[PDF] Borland® JBuilder™ 7 and BEA® WebLogic Server 7.0 , Note that this JAR file is required only if you want to test Web Services. If you decide to use WebLogic Server for all of your projects, you can assign This is the preferred option if you work with JSPs, since you do not need to redeploy to activate any JSP changes. To deploy and run the servlet, stop WebLogic Server. Plz help me How To Deploy Jsp project in Weblogic 8.1 Give me steps. (1) Create a standard WAR file that contains your JSPs. (2) Deploy to WebLogic by any number of means (e.g., Ant tasks, putting WAR file in application directory for your WL domain, etc.) %

  • JRebel certainly supports WebLogic and reloading JSP-s.
  • Do make sure you do not deploy this setting into production though. It will result in the JSPs being recompiled on every request, thus leading to locking of resources on the filesystem and queuing. Only use this in development.
  • I tried your solution (see update 1), but it didn't work. Suggestions what I could do differently are welcome.
  • @DP_ I'm sorry but you add "page-check-seconds" as well? Just make sure you redeploy the webapp. If you still have issue you may want to use console/WLST to get the runtime data (MBean) and enable debug flags. If you happen to know jsp compile path you can also verify the .java/.class file timestamp.
  • That is not true. With flags like page-check-seconds and resource-reload-check-secs you can not only deploy new JSPs but also new static files like .js too.