- This topic has 5 replies, 4 voices, and was last updated 17 years, 4 months ago by
.
-
Posts
-
Jetty 6 has been available for a while. When will there be an update supporting Jetty 6. Since it has been rebuild completely just pointing the jetty 5 app config to a jetty 6 location does not work. However I do believe its not a very major adjustment.
perhaps there is allready a pre-release available?
Regards, Wouter
@support-rkalla wrote:
Wouter,
We are going to try and get it into 5.5 if possible.Did I miss anything? I saw Jetty 6 in 5.5. After I set it up, I found HotSync does not work well. class files, resource bundles etc are deployed automatically but I have to re-start the server to make it work.
I guess my question is, is there any config for Jetty 6 to enable “complete” hotsync?For us, Jetty is the Dev time choice because of Tomcat’s PermGen memeory error when using Hibernate…
bridgeforce,
The issues you are seeing are Jetty configuration issues. We are working to make this even easier going forward, but it’s covered in the Jetty 6 docs on how to get it to reload a context when something like a resource bundle or other file changes here:
http://docs.codehaus.org/display/JETTY/ContextDeployerBased on my experience, this does not work with resource bundle.
It works with compiled class file though but changed scheme is not available. That means if you add method or property it won;t reload.
HTH
HTH,
There are a few things happening that are referred to (confusingly) all as “hot sync”.1. VM Hot sync — Where the server VM and debugging VM in MyEclipse will actually communicate and replace class file byte code on the fly. This is VERY limited to body-contents of methods and cannot be changes that effect the “shape” of the class file (member vars, add/remove methods, etc.)
2. Server Context Reloading — Servers can note changed resources and trigger the context for that specific web app reload without needing to restart the app server.
