For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 9 replies, 4 voices, and was last updated 20 years, 10 months ago by
.
-
Posts
-
Bugreport on JSP Editor
===============Eclipse: v. 3.01
myEclipseIDE: v. 3.8.4While working with the JSP-Editor of myEclipseIDE I encountered a bug while typing in a hibernate / struts enabled project (The tutorial from the myEclipseIDE website):
Setting the cursor to a certain position in the JSP Code.
While I was typing, the text showed up in a “mirrored” way,
so that the word “hello” would look like “olleh”.The bug stayed even when closing and opening up this JSP again.
Only after restarting the whole workbench, the editor was working again.Is this a known bug?
Cheers,
BrummerIs this a known bug?
Yes this is a known bug and it has become extremely elusive for us to track down although we have narrowed it down to an exception occuring in the reconciler. We are going to look into fixing this (rare) bug for the 4.0 release if we can.
Brummer,
Do you have a file that you can use to consistently exhibit this behavior? That is, do you have a reproducable test case we can use to make the bug show itself? If we had that it would certainly help us track it down.
I am seeing this as well. It is worse because after I see this behavior, I can make changes to a jsp and the MyEclipseIDE environment (jsp editor) appears to believe that I have made changes. I can even close the editor, reopen it and see my changes.
When I deploy, I don’t see the changes to the JSP. I have even shut down the server (JBOSS 4.0sp1) and undeployed my ear, redeployed, and restarted the server. Still, not seeing the changes. Prior to this I cleared the jboss cache directories.
I decided to shutdown MyEclipseIDE completely and restart. I did so and then brought up the offending JSP. Surprisingly enough, none of my changes from the previous session had been saved as it appeared.
It appears, the only way to fix this problem with mirroring is to restart MyEclipseIDE which in my mind makes this a MAJOR bug.
I am running MyEclipseIDE 3.8.4 (Eclipse 3.0.2) on Windows XP SP2. I am compiling with the latest JDK 1.4 from sun and my runtime JRE is JDK 1.5_02, also from SUN. My machine is a Pentium 4 3.0+GHZ with a Gig of RAM.
J.D.
JD, I am adding your comments to the issue we are tracking this with and bump it’s priority.
Additionally we REALLY need to find a reproducable case for this, while I think it is completely clear that it has been confirmed this bug exists, we have yet to have one user be able to reproduce it consistently (as well as our testing team AND developers) such that we can see X, Y, Z steps create the problem, so that means the bug is here and go fix it.
So at this step we are no longer trying to confirm the bug, we are trying to discover where it lies. If you can help us with that we can get to the bottom of this faster with user’s help that are afflicted by the problem (I have not run into the bug yet believe it or not on either of my two setups on different computers).
@support-rkalla wrote:
JD, I am adding your comments to the issue we are tracking this with and bump it’s priority.
Additionally we REALLY need to find a reproducable case for this, while I think it is completely clear that it has been confirmed this bug exists, we have yet to have one user be able to reproduce it consistently (as well as our testing team AND developers) such that we can see X, Y, Z steps create the problem, so that means the bug is here and go fix it.
So at this step we are no longer trying to confirm the bug, we are trying to discover where it lies. If you can help us with that we can get to the bottom of this faster with user’s help that are afflicted by the problem (I have not run into the bug yet believe it or not on either of my two setups on different computers).
The only thing I did (and I don’t remember the exact keystrokes) was edit some HTML in a jsp. Very similar to the following…
<TABLE….>
<TBODY>
…
</TBODY>I was inserting a THEAD after the TABLE definition and before the TBODY. I started to backspace over the text when I got the popup with the cryptic error about the key command not existing or something like that. After this happened, I started seeing the mirroring and had to shutdown MyEclipseIDE to clean things up so I could edit and redeploy this jsp.
J.D.
Interesting, thank you JD, I will add this to our testing (or atleast help it to influence how we test).
What about <Script> tags? Any problems there?
@support-rkalla wrote:
Interesting, thank you JD, I will add this to our testing (or atleast help it to influence how we test).
What about <Script> tags? Any problems there?
I haven’t noticed anything with the <Script> tags but I will keep a look out. I think the error message from the dialog that pops up when this happens will be good information for your testers. If this happens again I will jot down the information from the error dialog and add it to this thread.
Good News
Alright this is some good news. One of our developers, Brian, was filled with a rage that burns like a 1000x suns last week and this weekend and actually dug down into the editors to figure out what is causing this problem and figured it out. We aren’t certain yet who’s fault the problem is, BUT the workaround is as follows:Workaround for Backwards Typing
The issue seems to go away IF the first thing you do when you start up MyEclipse is to make sure no editors are open (if they are, close all of them, and restart) then open up the Properties View (Window > Show View > Other > Basic > Properties) and make sure it is active or “ontop” where ever it is open. Now open up an HTML or JSP file with the Properties view still showing. Once you have done this, the interaction that was previously causing the “Backwards typing” will disappear for the remainder of your Eclipse session. The Properties view does not need to be active anymore once you have done this BUT you cannot close it.Targetted Release for Fix
We will be targetting the public 4.0 M1 release next week with a fix for the backwards typing that will no longer need the workaround given above. We appreciate all the patience and error reports and details everyone has filed that made this possible tofix.
