[ http://nagoya.apache.org/jira/browse/CACTUS-46?page=history ]
Vincent Massol closed CACTUS-46:
--------------------------------
Assign To: Vincent Massol
Resolution: Won't Fix
Ramesh,
Tomcat does support class reloading. Your issue can be solved easily by configuring
Tomcat to reload classes as they are modified. This is the same for all other
containers. The reason this issue is "WON'T FIX" is that it is not up to Cactus to
manage class reloading. It is up to the container. Thanks for your help!
> TestClass Loader
> ----------------
>
> Key: CACTUS-46
> URL: http://nagoya.apache.org/jira/browse/CACTUS-46
> Project: Cactus
> Type: Bug
> Components: Framework
> Versions: 1.4.1
> Environment: Operating System: All
> Platform: All
> Reporter: Rameshkumar
> Assignee: Vincent Massol
> Fix For: 1.7
> Attachments: AbstractWebTestCaller.java, TCClasspath.xml, XMLClasspathReader.java
>
> Once we load the test class once in server side (by executing the class in the
> client side), it is not getting reloaded for the next time when a call comes
> from client side. Due to this suppose I want to modify a test during test case
> development time, I have to stop the tomcat server and restart it. Is there any
> way to overcome this. I tried by modifying "AbstractWebTestCaller.java" (using
> URLClassLoader), it works fine.
> Does reloading of the test class have any side-effect or disadvantage? If not, I
> think this issue has to be addressed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
