This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Why not set reloadable="true" ? | ||
---|---|---|---|
Product: | serverplugins | Reporter: | _ gsporar <gsporar> |
Component: | Tomcat | Assignee: | Petr Hejl <phejl> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | bleonard, mkleint, pjiricka |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
_ gsporar
2007-09-22 14:32:32 UTC
I agree with you this is very useful functionality. We should evaluate the change carefully to be sure that we won't break anything (debugging for instance). When doing this we should also consider default usage of antiJARLocking - it could be helpful for clean & build while server is running (see issue 112529). BTW Reloadable can be set to true by setting it manually in META-INF/context.xml in current nb ide version. We should also (if possible) make clear that this option should not be used in production builds. Fixed JAR locking (configured antiJARLocking="true" for tomcat 5.5 and 6.0) 07525c2cca71. Reloadable does not make sense with CoS.
>Reloadable does not make sense with CoS.
What exactly is "CoS" ?
Thanks - Gregg
Compile/Deploy on Save. Is there a specification for Compile/Deploy on Save available that explains in a bit more detail why reloadable="true" is not necessary? Thanks - Gregg http://wiki.netbeans.org/CompileOnSave It is not necessary because Deploy on Save is doing the exactly the same thing as reloadable. BTW tomcat is not doing "automatic reloading of classes" as mentioned in first comment. Tomcat just monitors changes in classes and reload the (whole) application. With CoS we know when the class is changed and we can call reload directly - doing the same thing. Integrated into 'main-golden', available in NB_Trunk_Production #339 build Changeset: http://hg.netbeans.org/main/rev/07525c2cca71 User: phejl@netbeans.org Log: #116397 Why not set reloadable="true" ?: Fixed jar locking. Deploy on Save is great feature, but not always. First of all what if I change 3-4 files (java, properties, etc..) and hit save on each separately? Tomcat will do redeploy after each save which is not very cheap process when working with large webapps. On the other hand, some of my coworkers (eclipse ones) continuously reminds me that redeploy is not always needed. If I only change log message in some class, only that class needs to be replaced in classpath, which is extremely faster than reloading. Any suggestions on this? my general advice for top-class class reloading is JRebel. |