[Ace_Balasador]

Hi! I am new to this forum and I would like to greet all of you a wonderful day! I used to be a Microsoft Programmer but Java (J2EE) has intrigued me for years and I have finally taken the courage to shift careers. I have heard from all of my Java friends about the MyEclipse and recommended it as the best RAD tool for J2EE apps.

For the pat few days I have been manually setting up my jsp/servlets/beans, using nothing but the windows command prompt and UltraEdit, i have downloaded Eclipse 3.1 latest build and MycEclipse GA 4.1.1, but to my dismay the installer didnt work, as well as 4.1.0, so I downloaded the manual install 4.1.1 and it worked.

I have successfully integrated the (My)Eclipse IDE with my tomcat5 app server, and whenever i deply my simple J2EE application it says that it did so. But when I view the pages i always get an error 404 🙁 But all of my other manually created applications are working well. Also, i noticed that whenever i remove EVERYTHING in the said folder, say context “/PRACTICE” and leave nothing but a simple index.jsp or index.html file i can finally see it in my web browser. 😯

what could be wrong here? i have spent at least the last 2 hours debugging things but i cant seem to pinpoint any culprit. any ideas??

Thanks in advanced!

– ace

[Riyad Kalla]

Hi! I am new to this forum and I would like to greet all of you a wonderful day!

Welcome Ace, glad to have you here.

I used to be a Microsoft Programmer but Java (J2EE) has intrigued me for years and I have finally taken the courage to shift careers. I have heard from all of my Java friends about the MyEclipse and recommended it as the best RAD tool for J2EE apps.

Fantastic, we are happy to hear that. I hope it proves to be a good tool for you.

For the pat few days I have been manually setting up my jsp/servlets/beans, using nothing but the windows command prompt and UltraEdit, i have downloaded Eclipse 3.1 latest build and MycEclipse GA 4.1.1, but to my dismay the installer didnt work, as well as 4.1.0, so I downloaded the manual install 4.1.1 and it worked.

Sorry to hear that, what platform are you on? The installer is using an older release of InstallAnywhere and it can get squirrely on certain platforms. At some point we will upgrade the install software and fix this, but for now your workaround of using the manual install is exactly the right thing.

what could be wrong here? i have spent at least the last 2 hours debugging things but i cant seem to pinpoint any culprit. any ideas??

I will point out a few general tips to you. On windows, running an app server usually creates read-locks on the files in a deployed application. Typically these locks are on the JARs in the projects WEB-INF/lib dir, but occasionally it can be on some of the resource files. If a read lock exists, on Windows, this will cause deployment removal and redeployment to fail sometime creating a partial deployed state (some files erased or deployed and other’s not). So make sure your app server is shut down if you are adding or removing a deployment.

Additionally, using an “exploded” deployment type will allow your deployment to be kept up-to-date in real time by MyEclipse. EVery time you save a file, it is immediately hot synced to the server. Your class files will be hot synced directly into the running VM, but not all changes are hot syncable (you will be notified when deployment fails, in which case, just restart your app server). Also if you perform enough hot syncing, it can sometimes cause the VM to just bomb out with a VM Termination, but that’s few and far between.

[Ace_Balasador]

@support-rkalla wrote:

Fantastic, we are happy to hear that. I hope it proves to be a good tool for you.

thanks, and it really is a good tool, all of us in our team which has at least 4 years of programming MS technologies are shifting to java and this is the tool that we’re using.

Sorry to hear that, what platform are you on? The installer is using an older release of InstallAnywhere and it can get squirrely on certain platforms. At some point we will upgrade the install software and fix this, but for now your workaround of using the manual install is exactly the right thing.

im on windows xp SP2 with all the latest updates.

I will point out a few general tips to you. On windows, running an app server usually creates read-locks on the files in a deployed application. Typically these locks are on the JARs in the projects WEB-INF/lib dir, but occasionally it can be on some of the resource files. If a read lock exists, on Windows, this will cause deployment removal and redeployment to fail sometime creating a partial deployed state (some files erased or deployed and other’s not). So make sure your app server is shut down if you are adding or removing a deployment.

Additionally, using an “exploded” deployment type will allow your deployment to be kept up-to-date in real time by MyEclipse. EVery time you save a file, it is immediately hot synced to the server. Your class files will be hot synced directly into the running VM, but not all changes are hot syncable (you will be notified when deployment fails, in which case, just restart your app server). Also if you perform enough hot syncing, it can sometimes cause the VM to just bomb out with a VM Termination, but that’s few and far between.

thank you very much! i have already encountered the erros revolving the file locking errors and i already know the solutions whenever i come up again that problem. Also, i didnt know that the very jsp names are also case-sensitive that’s why i always fail to see and get an error 404 on my pages. i also found about the “clean” workspace and rebuild tool.

anyway, thank you very much, sorry for being a NEWBIE 😀 🙂

[Riyad Kalla]

Glad to hear it’s working now.

[Author]

Posts