- This topic has 4 replies, 3 voices, and was last updated 20 years, 9 months ago by Scott Anderson.
-
AuthorPosts
-
sjonesMemberI have a J2EE application utilizing a Struts framework, JSPs and Stateless Session EJBs for database persistance.
The Eclipse Project started out as a WSAD Java project that has Web Capabilities added by the MyEclipse Plug-in.
I am currently deploying my application as an exploxed archive and deployed it to the Weblogic Server 7.0 SP2 running inside of Eclipse.
I have sucessfully achieved JSP Debugging, but have been unable to get Hot Deployment of changed JSPs or Java files to be reconized by the Weblogic Server. I must stop Weblogic, Redeploy App, and Restart Weblogic to see JSP or Java file changes.
The message I recieve when attempting to Hot Deploy file is –
Hot code replace failed
weblogic.Server at localhost:14423 was unable to replace the running
code with the code in the workspace.
Reason: The target VM does not support hot replaceIs this expected since Weblogic is running JDK 1.3 or should Eclipse allow hot deployment to a running Weblogic Server?
Weblogic 7.0 SP2 JVM: SUN JDK 1.3.1_06
Eclipse JVM: SUN JDK 1.4.2_03
support-michaelKeymasterHot code swapping support requires your WLS instance to be run with JDK 1.4.x. We do this all the time without issue. Please note there are some limitations to the extent of code changes supported by the hot swap feature, i.e., can not change the shape of a Java class.
support-michaelKeymaster
sjonesMemberOk,
I switched the Weblogic JDK to run with the SUN JDK 1.4.2_03 and I now get Java file hot deployment.However, if I change a JSP it does not appear to get redeployed to the server.
I see the JSPCC compiler excute in the Eclipse status bar upon saving the JSP file, but no indication of redeployment is issued.
When the changed JSP page is executed, no DOS window pops-up indicating a need to recompile the JSP on the fly and the old JSP information is displayed. I tried clearing the Internet cache, but did not help.
Are there additional setting required (web.xml, weblogic.xml, Eclipse deployment configuration, etc) requried to support hot deployment of JSPs?
Scott AndersonParticipantTwo things might be affecting this. First, we need to determine if the new JSP is being copied to the deployment directory after you modify it within MyEclipse. You can check that by modifying and saving the file in MyEclipse and then checking the contents of the same file in the deployment directory to see if it contains the changes.
If it does, then the problem is most likely that you have WebLogic configured to ignore JSP updates for running applications. I forget which setting this is, but WebLogic can be configured either way, either recompile JSP’s on modification or ignore them until application restart.
-
AuthorPosts