[
https://issues.apache.org/jira/browse/WICKET-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462864
]
Eelco Hillenius commented on WICKET-126:
----------------------------------------
It can be in trunk for now. Before we release (either 1.3 or 2.0), we have to
decide where it ultimately will stay. Probably extensions, but I'd like to run
a vote on that first.
It would also be interesting to hear people's experiences with this filter.
> Reload Java Classes for Improved Developer Experience
> -----------------------------------------------------
>
> Key: WICKET-126
> URL: https://issues.apache.org/jira/browse/WICKET-126
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Reporter: Jean-Baptiste Quenot
> Assigned To: Eelco Hillenius
> Attachments: 20061129-wicket-1.x-ReloadingClassLoader,
> 20061130-wicket-1.x-ReloadingClassLoader,
> 20061130-wicket-1.x-ReloadingClassLoader,
> 20061201-wicket-1.x-ReloadingClassLoader,
> 20061203-wicket-1.x-ReloadingClassLoader-includes,
> 20061203-wicket-1.x-ReloadingClassLoader-includes,
> 20061205-wicket-1.x-ReloadingClassLoader, WICKET-126-1.x.patch,
> WICKET-126-trunk.patch
>
>
> Currently in Wicket it is possible to reload the templates in DEVELOPMENT
> mode, but it is not possible to reload Java classes. That makes it very
> painful for the developer, as a server restart is required every time. One
> can still use hot code replace within the debugger, but that is not reliable
> and does not work every time, especially when the method signatures change.
> The attached *experimental* patch addresses that issue by providing a custom
> classloader and an adaptation of WicketFilter to allow reloading the Wicket
> application upon a class file change. As soon as a Java class is updated
> in the classes directories, the corresponding application is reloaded by
> WicketFilter. Also, bookmarkable pages are properly reloaded.
> On the TODO list:
> * allow to switch off class reloading
> * allow to specify the location of directories containing class files
> * porting to WicketServlet
> * more testing
> I wanted to share this code ASAP for you to test. It is based on branch 1.x.
> Note that part of the code comes from Apache Cocoon, released under the
> Apache license.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
