[christerljung]

Im trying to setup myeclipse 4.1.1ga and Tomcat 5.28 with a large existing webapplication. After reading and testing the tutorials i have a setup that works in some parts.
The big problem is that after a full deploy is made, the webapplications main starting servlet ist available any longer. In some cases it is available but other parts of the application crashes. To solve this i have to manually copy all original class files to tomcat\webapps\webapp\webinf\classes. When i compare the classes made by myeclipse with the orginalfiles, i notice they havent got the same size??. From reading in myeclipsedocumentation i understand that Myeclipse uses its own compiler and not jdk. So, isnt the myeclipse compiler fully compatible? -I dont think this the answer. Maybe the red marks in some sourcefiles must be fully solved before its possible to get the correct classfiles deployed?
Im still able to step thru the code, and even make some changes and have them appere in the application. But suddenly Myeclipse makes a “bulding workspace” and everyone of the hundreds of classfiles is changed, even without a deploy…
Im probably missing something big here…
I tried a new install with myeclipse 5 but i wasnt able to get the jsp-debugging to work. The previus problem after full deply was still there too.
Any help is apreciated.

/Christer, Sweden.

[Riyad Kalla]

So, isnt the myeclipse compiler fully compatible?

Yes, it’s the Java compiler from the JDT project under the Eclipse umbrella. It’s a fully compliant compiler.

Maybe the red marks in some sourcefiles must be fully solved before its possible to get the correct classfiles deployed?

Yes, that can cause a deployment to fail in some cases.

But suddenly Myeclipse makes a “bulding workspace” and everyone of the hundreds of classfiles is changed, even without a deploy…

It’s possible if the class you are changing is used by many other classes, then some of those other classes can get rebuild or re-analyzed.

Christer,
To be honest I don’t know what the problem is here. It sounds like you still have some outstanding problems/bugs to fix in the code to get rid of all the compilation errors, but even with those you are able to debug some of the code which is great.

Can you be a bit more specific exactly what the problem is?

[christerljung]

Allright, lets start with the errors. Since the sourcecode belongs to a released, functional webapplication i havent paid much attention to the errors, but her they are:

Here is screendumps of my errors:

http://www.labutb.falun.se/christer/__portal/error1.jpg
http://www.labutb.falun.se/christer/__portal/error2.jpg
http://www.labutb.falun.se/christer/__portal/error3.jpg
http://www.labutb.falun.se/christer/__portal/error4.jpg
http://www.labutb.falun.se/christer/__portal/error5.jpg
http://www.labutb.falun.se/christer/__portal/error6.jpg
http://www.labutb.falun.se/christer/__portal/error7.jpg
http://www.labutb.falun.se/christer/__portal/error8.jpg
http://www.labutb.falun.se/christer/__portal/error9.jpg
http://www.labutb.falun.se/christer/__portal/error10.jpg

[christerljung]

And this is a dump of my project structure in j2ee-perspective.

http://www.labutb.falun.se/christer/__portal/tree.jpg

[Riyad Kalla]

Christer,
I think we are getting our wires crossed. I’m not clear what your specific question was in the first post or what I can help you with. My job isn’t to help you resolve every single compilation/validation error in your project (only because it’s out of the scope of what I”m here to do)… I’m just trying to figure out how to answer the original question you had.

[christerljung]

sorry, i just want to get the hole thing working, after struggling alot in the dark, and trying differrent tools and ide:s , im beginning to see the light with myeclipse.

My question is:
Why does the application stop working after a full deploy? The only thing that changes is the size and dates of the classfiles.

Sometimes i got a feeling tha Tomcat just doesnt like what myeclipse is sending over?

(I can probably solve the errors by myself, but im not gonna waist time on that if it isnt the real problem).

Thanks
/Christer

[Riyad Kalla]

My question is:
Why does the application stop working after a full deploy? The only thing that changes is the size and dates of the classfiles.

If you are deploying to a running app server, this can cause a problem as the App Server can sometimes try and reload a web application in the middle of MyEclipse actually deploying it. This is most noticable with huge projects cause they can take a while to deploy. Ways to work around this problem are:
1) Only deploy to the app server when it’s stopped
2) Use packaged deployments
**3) Preferred Way: Use an exploded deployment, then your changes are deployed *as* the files are saved.

Sometimes i got a feeling tha Tomcat just doesnt like what myeclipse is sending over?

If you watch the messages from Tomcat in the console, sometimes it can help you uncover what is going on. Something like “Redeployment failed due to BLAHBLAH.JAR being locked” or something like that. But the steps above should help you get around this.

[christerljung]

I got rid of the problem after cleaning my errrors. It seem strange anyway because the servlet that previosly failed, has no involvment with the files that had errors.

Anyway, Now i have problem with jsp debugging the ide stops for breakpoints in javacode but not in jspcode, why?

[Riyad Kalla]

It could depend on a lot of things:

1) The app server you are using does not support JSR-45 (debugging spec)
2) You aren’t running your app server with a VM version 1.4 or later
3) You aren’t compiling your JSP pages with debugging symbols
4) You aren’t running your app server in debug mode, but instead in Run mode
5) You are running your app server externally from MyEclipse

Try upgrading to Tomcat 5.5.17 and see if debugging works then. Be sure to use a relatively new VM, I would suggest 1.5.0_08 release to run both MyEclipse and Tomcat. Also make sure you are launching Tomcat from MyEclipse and it is set to start in Debug mode.

[Author]

Posts