- This topic has 1 reply, 2 voices, and was last updated 17 years, 12 months ago by
.
-
Posts
-
Since I’m stuck waiting for MyEclipse’s Spring 2.0 support *coughs* I decided that I’d just manually edit my project’s build path to include the necessary JARs. A restart of Tomcat was not sufficient to get these new libraries in place, but I feel it should have been. There should be a hot code replacement attempt, and if it fails, a popup warning stating that it could not update the WEBROOT/WEB-INF/lib directory, or wherever, which I think is the default??
Vitals:
*** Date: Mon Oct 30 10:13:51 EST 2006 *** System properties: OS=WindowsXP OS version=5.1 Java version=1.5.0_09 *** MyEclipse details: MyEclipse Enterprise Workbench Version: 5.0 GA Build id: 20060805-5.0-GA *** Eclipse details: Eclipse SDK Version: 3.2.1 Build id: M20060921-0945 Eclipse Graphical Editing Framework Version: 3.2.0.v20060626 Build id: 20060627-0816 Eclipse Platform Version: 3.2.1.r321_v20060921-b_XVA-INSQSyMtx Build id: M20060629-1905 Eclipse RCP Version: 3.2.1.r321_v20060801-2ekW2BxmcpPUOoq Build id: M20060629-1905 Eclipse Java Development Tools Version: 3.2.1.r321_v20060905-R4CM1Znkvre9wC- Build id: M20060921-0945 Eclipse Plug-in Development Environment Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG Build id: M20060921-0945 Eclipse Project SDK Version: 3.2.1.r321_v20060801-tQ1w49KnTArT0FZ Build id: M20060921-0945 Eclipse startup command=-os win32 -ws win32 -arch x86 -launcher C:\Program Files\eclipse\eclipse.exe -name Eclipse -showsplash 600 -exitdata c60_54 -vm C:\Program Files\Java\jdk1.5.0_09\bin\javaw.exe -vm C:\WINDOWS\system32\javaw.exeMyEclipse++
You are exactly right, changing your build path or any other “build” function is actually what triggers the autodeploy feature. THe problem is, on Windows if Tomcat was running, the autodeploy *occured* when the JAR files were locked, which means it likely failed silently. THe trick would be to shut down Tomcat, redeploy, then restart.
We are making some nice changes to the deployer in the 5.0.3 release, like making it more resillient (no longer silently fail, and a locked file will no longer stop a redeploy) in addition to some more nice changes like touching the web.xml file to force a reload automatically for full redeploys to running app servers.
I’m going to close this, but file a note in the developer’s tracking system to make sure they test for this case and follow up if it’s still not working.
NOTE: Also a reminder this only works with exploded deployments.
