[Daryl Peddle]

I am experiencing many of the issues that others are with the latest release (3.8.1GA) of the myEclipse plug-in.

Most commonly JSP issues (validation) even when validation is turned off the jsp editor still tries to validate jsps. With very large jsps this made it next to impossible to work as I had to wait for Eclipse to finish it’s validation after every change I made (not even after saving).

I am also experiencing build issues where the processor pegs at 100% and never returns during an automatic build. Manual builds or cleans cause an OutOfMemory Exception.

After installing the “QuickFix” all of my projects that were “Web Projects” are now recognized as Java Projects, thus the only feature that was working well (deployment) is no longer available.

I also noticed that I can no longer open JSPs. (Good fix for the validation problems) I get an “Unable to create part:” error.

I liked your product up until the last release, but I am going to have to disable the plug-in until some of these issues are resolved as I can no longer work.

[Daryl Peddle]

After rolling back the “QuickFix” my projects are now recognized again as J2EE projects and can be deployed. I can also edit jsps again, but I am back to square 1 with the validation / OurOfMemory issues.

[marsden]

I am having the same problems. The biggest problem I am having is the JSP validation even after I have turned it off. I applied the quick-fix too and wasn’t able to deploy my web applications anymore. I removed the quick fix and I can use that feature again.

Since I have upgraded (and I use that term with reservations) to 3, I have been spending a significant amount of time just fighting eclipse and myeclipse just to get my work done.

I am just about ready to disable it too and wait a while until 3 is more mature. I think it has potential so I won’t ask for my $30 back yet.

[Scott Anderson]

Guys,

I’m sorry to hear you feel frustrated with the quickfixes. They are simply an effort to be responsive to issues without forcing them to wait for a full build cycle. However, the problems you’re reporting sound like the quick fixes might not have been properly installed. In an effort to make the fixes as small as possible, we did not ship the entire plugin for each plugin contained, but simply the “delta”. The breaks you’re reporting sound like you completely overwrote the existing plugins with the ones in the quickfix, rather than applying them in such a way as they only overwrite the files contained in the fix and left all others in tact. I believe the install instructions detail this distinction, but perhaps they’re not explicit enough.

By the way, the validation / OutofMemory problem with JSP compilation is fixed internally and will be available as part of 3.8.2 in a couple of weeks. Until then, for large workspaces we recommend disabling JSP validation. However, the first quickfix is needed so that the disablement setting survives an Eclipse restart.

If you’re interested, the full installs on the server now have all the quickfixes pre-applied. To test them in a way that won’t disrupt your current environment I’d suggest installing both Eclipse 3.0 and the latest MyEclipse build in a separate location and trying them out with a new workspace. Once you’re happy with the configuration you can simply use the new install to open your current workspace.

[Daryl Peddle]

My installation was done according to the instructions below.

using WinRar to extract to “<MyEclipse Install>/eclipse/plugins” overwriting only files that were newer (in the archive)

To install it, exit Eclipse and unzip the quick fix archive directly into <myeclipse-inst-dir>/eclipse/plugins. You should choose to overwrite files, when prompted. Please note, the quickfix contains only the subsets of several plugins that changed, not the complete plugin so please don’t choose an extraction method that overwrites the entire plugin directory. On Windows, simply unzipping with WinZip or using the XP file explorer to copy the folders into the plugins directory will “do the right thing”.

I made a backup of the plugin directory first (so that I could roll back if needed)

I have tried this process 3 times, on the 3rd time I chose not to start eclipse using the -clean arg, and my projects were still recognized as J2EE so they were recognized by the deployment (also my deployment icons remained icons. They were just text on previous attempts), but I stinn cannot edit JSPs.

[Patryn]

I too have this problems. (win XP, latest Quickfixes)
That has nothing at all to do with wrong quick fix installation.
I tried several way, first quick fix, than the full download again with integrated fixes.
A lot of jsp pages cannot be opened. (this cannot create part stuff)
When i can open a complex page, there are several problems.
– Not all beans are properly recognized.
– there seems to be several threads waiting on keyboard input, sometimes the input gets completely shuffled, all input generates long wait times, close and open editor hels – the worst drawback
– sometimes the context strg-tab and strg-click stuff dont work anymore, close and open editor helps
– context-strg-click on includes says, the file isnt there, webroot, but compile say, its ok (minor anoyance)

Now i have to deactivate myeclipse and hope on further fixes instead of new versions with new features.

—
André

[sferrazzi]

Yes, me too.
I have to deactivate myeclipse and hope on further fixes instead of new versions with new features… 🙁

[Riyad Kalla]

– Not all beans are properly recognized.

This is a known problem that is actually a PIA result of every taglib library doing something different instead of just using jsp:useBean for defining beans. We have fixed this in the current internal build.

– there seems to be several threads waiting on keyboard input, sometimes the input gets completely shuffled, all input generates long wait times, close and open editor hels – the worst drawback

Please explain this in more detail so we can get it fixed. Can you tell us what keystrokes you are using and what is happening? Does it seem “lagged” by about 3-seconds or so? If so this is a known refresh issue that we have addressed internally.

– sometimes the context strg-tab and strg-click stuff dont work anymore, close and open editor helps

I didn’t understand the action you were referring to here, can you clarify?

– context-strg-click on includes says, the file isnt there, webroot, but compile say, its ok (minor anoyance)

Again I don’t follow, please provide more detail.

Guys 3.8.2 is going to be almost a bugfix-only release along with a huge effort on optimization (Speedups, memory usage, etc.) so we really want to collect all the annoying bugs now and get them fixed as soon as possible. We hate these bugs too and are MORE mad then you that this release caught so many users off gaurd. We’ve got some serious work to do to gain back everyone’s trust and we know it. We have not and will not falter on our commitment to good software and giving our customers what they want; I can promise you that.

[Scott Anderson]

A lot of jsp pages cannot be opened. (this cannot create part stuff)

There is a known problem that will be addressed in 3.8.2 regarding opening JSP pages that exist in *plain Java* (not MyEclipse Web projects) that include taglibs or other JSPs. Do these problematic JSP’s exist in plain Java projects?

[Patryn]

Thanks for your efforts.

The JSPs are in a normal Web-Project with WebRoot properly configured.
In an other thread i wrote some trys in detail.

To the keystokes…i type fast some text, for instance “<%= blablub %>”, in the meanwhile the validator has a lot of stuff to do, reorganize the tree for the outline (great tool) several times, the file is in CVS, diff it, compile it, update context and so on. Whats the result:
I get an shuffled input, may be %<blabllu= %>, if i get only that, i have luck, but the whole editor lags than like hell, undo isnt possible any more, the cursor jumps around with further input and so on.

Then i have to close and reopen the file, repair the place.
That happens quite often.

Context strg-tab doesnt do it than, this code-completion or how you call it.
Or the strg-leftMouse, jump to code, also out of order than.

For the include, i use <%@ include file=”/templates/blablub.jsp”/>, the compiler says, its OK, but strg-left mouse (jumps to code) says, there is no source file.

OK now? Sorry for my funny english 😉

—
André

[Riyad Kalla]

Andre,
Do you use quick-diff by chance? I have never seen the behavior you are talking about, BUT I did keep quick-diff turned off because its so resource intensive.

Can you try and turn it off and see if that helps?

[Patryn]

Yes i had that active, now is weekend, but monday i will see if deactivating helps.
ThX

—
André

[Patryn]

With deactivationg i obtain a better behavior, but again sometimes the input gets scrambled and i have to clode and open the editor.
Now i can work a litte bit better.
Main problem remains, following bean context isnt recognized:

<jsp:useBean id=”generator” type=”hox.corem.servlets.Generator” scope=”application”
/><jsp:useBean id=”context” type=”hox.corem.servlets.Context” scope=”request”
/>

But the jars are included and older versions of myeclipse or lomboz make that. Strange strange.

—
André

[jhettenh]

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. It’ll complete after a half hour or more, but any mass changes (e.g. an “update state” operation using the VSS plugin) that triggers the JSP index operation will slow it to a crawl again.

The application uses almost all of my memory (virtual too) during this time, but little processing power. The CPU does spike shortly before the application becomes responsive again. It almost seems as if the application is stuck in a loop during these periods.

Of course, our web application is a little different due to the Broadvision components. We have tags linked to native class files, hundreds of JSP files, and even files labeled JSP but are actually server-side javascript. So that is probably a contributing factor to some of the problems I experiece. I love the product and just got my team to purchase it, but it’s rather unusable in the 3.8+ state. I hope the 3.8.2 works out.

Regards,
JH

[Riyad Kalla]

Andre,
What is your MyEclipse Build ID (Window > Prefs > MyEclipse)… this is the first time I’ve seen you comment about this problem with useBean. Can you explain in more detail where the hox.corem.servlets.Context class comes from? Is the JAR in your Build Path? Is it an external JAR or a JAR in your project? Where is it in your project? Can you give me a sample page of code that exihibits this behavior so I can reproduce it?

[Author]

Posts