- This topic has 9 replies, 3 voices, and was last updated 15 years, 8 months ago by
.
-
Posts
-
Is there anything special I need to do to use Jetty with MyEclipse 7.x? I downloaded it today and set it up like I have Tomcat. I can right-click and start the Jetty server and deploy web applications as well. However, I get a 404 when I try to access my webapp. This same deployment to Tomcat works fine.
Peace,
ScottScott,
I tried this out at my end and I was able to get the app to run via jetty. Can you create a new webproject called “TestProj” and deploy it to the Jetty server. Now start the server and try the url “http://localhost:8080/TestProj”. Does this work for you ?Thanks brother! Yeah, I deployed the application I had running on TC 6.x to Jetty 6.x using the Server right-click method. When I try browsing to the application running on the Jetty server, I receive a cute little Jetty 404! If I stop the Jetty server and strart TC 6.X, I can reload the web page just fine. Jetty is listening on 8080, right?
It seems to me to be a Jetty sever deployment issue of some sort since the same web app run fine deployed to TC
Peace,
ScottBefore we go much further, let me ask a couple questions.
1) I have heard that Jetty does not suffer from the PermGen errors the way TC does. Is this right?
2) The rumor is Jetty is much faster to develop on than TC, Thoughts?
This is why I am looking for a more productive server. I get the PermGen after about 4 or 5 redeployments which requires the whole server reboot deal! Do you know why classes are not reloaded in TC 6.x without redeploying the application?
1) I have heard that Jetty does not suffer from the PermGen errors the way TC does. Is this right?
2) The rumor is Jetty is much faster to develop on than TC, Thoughts?
Im sorry but I have limited knowledge about the Jetty server so cannot comment. You should start a new thread in the Off Topic >> General forum to get help from the users.
Do you know why classes are not reloaded in TC 6.x without redeploying the application?
The classes should be reloaded if you deployed in exploded mode. Did you deploy the app in exploded mode and the classes are not reloading?
Can you help resolve application deployed to TC 6.x works fine but when deployed to Jertty 6.x results in 404? Also, application is deployed as exploded to TC 6.x and classes are not reloading.
Hi Scott,
Sorry for the inconvinience. Can you PM me your application? This will help me reproduce this issue at my end.
Unfortunately, this application is too big to PM. Let me just say again that the application works fine on TC 6.x. However, when I stop the TC server and deploy (using MyEclipse) it to Jettty 6.X, Jetty starts but the same URL used for TC 6.x a few minutes earlier now results in a 404. Also, can you tell me why TC 6.x is not seeing modified class files at runtime? The application is deployed in exploded format.
Peace,
Scott
