Hi > Did anyone try to contact the blogger directly? We have not.
Reloading classes on the fly is a great benefit but when it comes to different frameworks some changes cannot be reloaded without an integration as the frameworks' internal structures are usually cached and need special handling. If also the framework specific configurations can be reloaded (or a a large part of them) then the integration is a go for us. Right now we cannot assess how much these patches actually help the developers who use Wicket as we just see ((AbstractRefreshableApplicationContext)context).refresh() on certain failures. Toomas On Mon, Mar 17, 2008 at 8:33 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > Did anyone try to contact the blogger directly? > > Eelco > > > > On Mon, Mar 17, 2008 at 6:43 AM, Toomas Römer <[EMAIL PROTECTED]> wrote: > > Hello > > > > ZeroTurnaround team has stumbled upon a blog post > > http://d.hatena.ne.jp/mdgw/20080314/1205513596 with a title > > Wicket+Spring+JavaRebel. The translated version of the post is here: > > > http://translate.google.com/translate?u=http%3A%2F%2Fd.hatena.ne.jp%2Fmdgw%2F20080314%2F1205513596&langpair=ja|en&hl=en&ie=UTF-8 > > > > The translated text is rather difficult to read and as we don't have > > Wicket experience could someone comment on the patches attached to > > that blog post: > > http://www.madogiwa.org/wicket/wicket-ioc-1.3.1-zt-patch.txt > > http://www.madogiwa.org/wicket/wicket-spring-1.3.1-zt-patch.txt > > > > JavaRebel is a ZeroTurnaround product and we are interested if the > > provided patches are actually useful? > > > > Toomas Römer > > ZeroTurnaround.com > > >
