On 6/8/11 6:42 AM, forums_at_java.net wrote:
> Hi Ludo - Thanks for reply, I'm sorry if the post was persived as rude
> - it
> was not ment to be... In fact glassfish comes highly recommended and has
> excellent tooling which is why I'm evaluating it. You're right in that
> it's a
> special case for tapestry, and a few other frameworks that provide a
> class
> reloading strategy. I just wanted to know if there was anything You've
> considered or have support for. Btw, tapestry class reloading has
> reported
> issues with tomcat - and I couldn't get it working by replacing class
> manually in glassfish either... I've never done Grails, but suspect it
> would
> be same scenario..? cheers Magnus
>
> --
I could do a System property test ("glassfish.save.but.not.deploy") that
you could set globally in the Eclipse VM to avoid the "deploy" set on
the compile on save?
Not very exposed, but testable.
Ludo
>
> [Message sent by forum member 'MagnusKvalheim']
>
> View Post: http://forums.java.net/node/809990
>
>