java ee - Glassfish 2.1 unrelyable deployment -


I have a glassfish 2.1 server that is plugged into my eclipses and it is fast that when I deploy my project I have

I have a very simple EAR which I want to deploy for initial web services and successfully achieved it. It has been very fleeting since then, sometimes it will be deployed and the second can say that it is by its loyalty but the administration is not shown on the console

I will restart, clean, republish and project I'm going through the process of adding and removing nothing to work.

As recently I am doing this process for one hour, I try and work it without any dry work. I need to go in a trustworthy way because I am doing some experiment which will continue to upload me the project

Is there something that I can do to improve its properties or there? Is a more reliable way to rely on applications?

Thanks John

I have no experience with glassfish, but looked the same Problems with Weblogic and Tomcat

Eclipse has plugins to integrate with these app servers, they usually do a remarkable job but they are not correct. In the case of Tomcat, Eclipse quickly compiles all the compiled .class files directly into the Tombat's blasted application directory, and Tomcat, running in development mode, finds the changed code, and reload the application Does. When this works, it means that your new code is ready for the moment after pressing Ctrl-S to save a modified source file. But sometimes the app server is not syncing properly.

An option that has served me well is to do without tight server integration: Operate the apple server standalone (i.e. out eclipse), ant .ear To create a file and close your app, update your update and restart it. Deployment Cycle What the Eclipse plugin does for you, and you will have to work a bit harder to set up remote debugging. But I think this is the best way to get repetitive, effective, reliable deployment.


Comments