Luca,

If you're compiling from Ant, why can't you just make that task also ping
the server or touch appengine-web.xml? We don't think of the aforementioned
solutions as "hacky". They are purposefully designed so that we don't start
loading a webapp context with half-compiled classes, jsps, etc...

On Fri, Mar 11, 2011 at 3:57 AM, Luca Matteis <[email protected]> wrote:

> Wow thanks for this really interesting framework. I'll have a look at
> it definitely!
>
> About the context-reloading part, I realized that you can just touch
> appengine-web.xml to force server context reload. Also loading the
> page under /_ah/reloadwebapp will reload the servers context - even if
> it gives you a 404, it will still reload the context. I wish there was
> a standard programmatic way of reloading context instead of these 2
> "hacky" solutions.
>
> Luca
>
> On Fri, Mar 11, 2011 at 3:33 AM, Yasuo Higa <[email protected]> wrote:
> > Hi Luca,
> >
> > Slim3 supports HOT reloading.
> > https://sites.google.com/site/slim3appengine/
> >
> > Yasuo Higa
> >
> > On Thu, Mar 10, 2011 at 7:58 PM, Luca Matteis <[email protected]>
> wrote:
> >> Hello everybody!
> >>
> >> I'm using Google AppEngine with their built in web server. My
> >> development goes about in a simple way: I make changes to my .java
> >> sources or .jsp and compile using ant and to see the changes I have to
> >> restart the development server.
> >>
> >> I'm wondering if there's a way I can avoid this last step of
> >> restarting my development server - somehow refresh the cached classes
> >> context of my web-server. The options provided by Google on this dev
> >> server are quite limited and am wondering if there's a better way.
> >>
> >> I would like to avoid using something like JRebel which I could buy,
> >> but for this simple project I'm just wondering if I can remove the
> >> burden of restarting my web-server... otherwise I'll live with it.
> >>
> >> Thanks.
> >>
> >> Luca
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups "Google App Engine for Java" group.
> >> To post to this group, send email to
> [email protected].
> >> To unsubscribe from this group, send email to
> [email protected].
> >> For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
> >>
> >>
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> "Google App Engine for Java" group.
> > To post to this group, send email to
> [email protected].
> > To unsubscribe from this group, send email to
> [email protected].
> > For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
> >
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine for Java" group.
> To post to this group, send email to
> [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Reply via email to