- This topic has 40 replies, 9 voices, and was last updated 20 years, 7 months ago by
.
-
Posts
-
I just had a huge project (jboss) that was mucking stuff up. Sorry. No problems so far, thanks.
I have not seen 1 time yet that the JSP index has run. Why was it so hard to turn this off?
Can you recap what you did? You turned off validation and now everythign works? Or you contacted someone at MyEclipse and they sent you a patch to apply?
Ulitmately I just want to make sure everything is working for you.
so far everything works. turning validation off had no effect until I got the patch from you guys. Once the patch was applied, no more problems…so far.
I’m not sure if this is the same problem, but my slow down / complete halt begins with “Updating JSP Index” operation. Whenever that message appears my machine slows to a crawl and any java applications (usually Firefox) stop.
If you’re using ME 3.8.2, there’s a quickfix available for that. Please see this thread for details:
http://myeclipseide.com/PNphpBB2+file-viewtopic-t-4223.htmlIs there already any news when the 3.8.3 version is released?
I still have problems editing JSP files, and quite frankly all of the people I know who use myeclipse on wildly different machines have these issues.
The symptoms are slow editting, blinking errors, errors that shouldn’t be there, letters that get mixed up when typing, e.g. when I type “foo.bar” on the screen I see “oo.fabr” or something, message boxes about unsupported commands when typing, and complete lock-ups of the editor. Certainly the last one is troublesome 🙁
I can give you all my specs again (see my other posts), but since it happens on every different kind of machine I know off, I hardly think these are really relevant. The only constants are Eclipse 3.01 and MyEclipse 3.8.2 (no 3.8.2 quickfix applied).
I can fully acknowledge that.
Does anyone of you developers really work with complex jsp projects?
If i see the features, then i would say yes, a lot of nice ideas.
If i see the permanent questions after the editor versions and quick fix versions (written several times often), the assonant disbelief in error reports, then i would say no.
Some errors are so apparent in the every day work, i cant belief you have reproduction problems.
A lot of guys truy your product here on my commendation from 3.8 and now i have some argumentation problems 😉 They all have strange problems in simple jsp mode.
The here described foo.bar-mix-up problem i reported ealier, you have never heard of that, now you have 😉But i have the other problems to and much more.
<jsp:include> is fully useless. It declares bugs and problems, that are not there, never where or where adjusted. You have no chance to get them away, only a new project helps…some time(s).I have the creation part problem every day, have send a test project, you cant reproduce. Here several guys run into that problem after 1 or 2 days, all develop jsp since years.
I have problems in the jsp page, that are not recognized, and the other way around…and so on.
Hmmm, you where quite better, you can make better, i know.
Nice product, but useless at this time for me.—
AndréMaybe it helps to give the average size of the projects I”m seeing the problems with:
They are all around 400 ~ 500 .jsp files, with around 20~30 jsp includes in use. Most pages have at least two includes in them (a top and bottom one). The amount of beans and other java classes in use varies between projects, but on average between 100 ~ 200. (I don’t think the last metric is relevant, but just in case).
I’m seeing the problems on projects that don’t use other technology than plain jsp with scriptlets only (no tag library of framework in use).
It is said that the 3.8.2 quickfix patch is only for projects having over 1500 .jsp files, but appearently it happens on smaller projects too.
I see, I’m sorry for misunderstanding that.
What does aprox. qualify as “big”? Is big around 100 or more?
The patch actually fixes an issue with the indexer still trying to do something it shouldn’t be doing… so it will help a project of any size, its just that people with larger projects are noticing the problem more than smaller projects.
Of course the computer hardware you are running plays a big part too. I’d suggest grabbing the quick fix, it will help anyway.
