* ZedroS Schwart:
Just a small question : could you document what you need the beta
testers to do ? As such I could try to have a more efficient auto
reload ^^
Or just point you to the existing documentation :-)
Thanks for the tip Matej !
Joseph
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
Eclipse run will not run the program in debug mode. Thus you have no
reloading at all. To have at least basic jvm reloading (when the class
shape doesn't change), you must debug you application in eclipse.
-Matej
On 7/7/07, ZedroS Schwart [EMAIL PROTECTED] wrote:
Hi
Just a small question :
* Carlos Pita:
Up till now my experience with ReloadingWicketServlet has been
idyllic. It worked fine for every single change I've done to
java sources, property resources and templates, playing at home
and working at the office. It's a life-saver (it's giving me at
least an extra
Up till now my experience with ReloadingWicketServlet has been
idyllic. It worked fine for every single change I've done to java
sources, property resources and templates, playing at home and working
at the office. It's a life-saver (it's giving me at least an extra
free hour per day :) ). Thanks
sun should first improve the method change/delete/rename/add thing that ibm
already can do.
That shouldn't be to hard because the internal memory of the instance
doesn't have to be changed then
After that i think what they should try to do is have a depricated class
version of something
So all
I'm not sure it's that easy or else they would have done it. In any
case you should probably post to their forum instead of here :)
Gili
Johan Compagner wrote:
sun should first improve the method change/delete/rename/add thing that
ibm already can do.
That shouldn't be to hard
Hi all,
I find that reloading the entire app stack (wicket + spring +
hibernate) every time I change a page class is somewhat overkiller.
When coding simple toy examples restricted to just wicket, the
jetty:run maven plugin monitors my target folder and reload the
application in a matter of a
I find that reloading the entire app stack (wicket + spring +
hibernate) every time I change a page class is somewhat overkiller.
When coding simple toy examples restricted to just wicket, the
jetty:run maven plugin monitors my target folder and reload the
application in a matter of a second
See wicket.protocol.http.ReloadingWicketFilter. YMMV though, as Wicket
I will give this filter a try. I see it's included in the trunk but
not in 1.2.x releases. Is it compatible with wicket 1.2.5?
the JDK provides. Some SDK implementations are working on improved
support (I think Johan has
See wicket.protocol.http.ReloadingWicketFilter. YMMV though, as Wicket
I will give this filter a try. I see it's included in the trunk but
not in 1.2.x releases. Is it compatible with wicket 1.2.5?
Nope. Not planned either, sorry. If you are starting out, 1.3 (from
svn or get snapshots here
this is mostly a dream anyways for early stages where you are still adding
fields
see
http://www.theserverside.com/news/thread.tss?thread_id=44119#226916
hls' reply here
http://www.theserverside.com/news/thread.tss?thread_id=44119#226916
my rebuttal that drives the point home
Seems there might not be a full-proof fix for this problem:
http://forum.java.sun.com/thread.jspa?threadID=572396tstart=0
Gili
Carlos Pita wrote:
See wicket.protocol.http.ReloadingWicketFilter. YMMV though, as Wicket
I will give this filter a try. I see it's included in the trunk
I'd read that thread before. I think I understand your point Igor. But
I don't pretend that old instances keep somehow up to date with new
incompatible reloaded classes. If I could start all again from a
bookmarkable page, everything being reinstantiated again, I will be
happy, even if some
Seems there might not be a full-proof fix for this problem:
http://forum.java.sun.com/thread.jspa?threadID=572396tstart=0
But at least they're working on it, and any improvement would be welcome imo.
Eelco
-
Take
Please keep us informed when you play with the reloading filter. I
think Jean-Baptiste deems it usable in it current state. But any
improvements/ suggestions (especially in the form of patches!) would
be welcome.
Eelco
On 4/6/07, Carlos Pita [EMAIL PROTECTED] wrote:
I'd read that thread before.
I'm pointing my pom repositories to
http://wicketstuff.org/maven/repository just right now. I will keep
you informed of my experiences along next week, toying with it at home
and more seriously using it with my development team at work.
Cheers,
Carlos
On 4/6/07, Eelco Hillenius [EMAIL PROTECTED]
Maybe I'm missing something but I can't get ReloadingWicketServlet to
work. I have subclassed it and included a pattern for my web tier
package as documented. The relevant code and configuration is given
below. If I modify a class residing at home.web and then re-enter its
page (not just refresh
Maybe this could be relevant:
* I'm using jetty:run maven plugin.
* I run it from the console and from apache.
* I run it on top sun jdk 1.6.0 and ibm jdk 5.
Carlos
On 4/6/07, Carlos Pita [EMAIL PROTECTED] wrote:
Maybe I'm missing something but I can't get ReloadingWicketServlet to
work. I
* Carlos Pita:
Maybe this could be relevant:
* I'm using jetty:run maven plugin. I run it from the console
* and from apache. I run it on top sun jdk 1.6.0 and ibm jdk 5.
Hi Carlos,
You're running jetty:run so I guess your Eclipse classpath is
setup with Maven as well. So classes
20 matches
Mail list logo
