I'm having a severe repeatable problem in that every time that I open my web module, it corrupts the project and causes numerous IDEA exceptions (47331, 47323 for example).
Try deleting your iws file -- that will reset the state of the project view and seems to prevent the exeptions on startup. Unfortunately, it's sitll impossible to open a folder with problematic JSP files in it (not sure if all or only some cause the problem).
--Mike
I'm having a severe repeatable problem in that every time that I open my web module, it corrupts the project and causes numerous IDEA exceptions (47331, 47323 for example).
DM> I'm having a severe repeatable problem in that every time that I DM> open my web module, it corrupts the project and causes numerous IDEA DM> exceptions (47331, 47323 for example).
Build: Sorry, I should have mentioned that. I was having the problem with 3326 and am still having it with 3339.
Deleting the IWS file did reset the project view.
There is nothing that is actually wrong with my JSP files, so if IDEA is having problems parsing them - and especially if this failure to parse them is causing these kinds of crashes - then this is an absolutely and completely unacceptable problem.
How do I know that there's nothing wrong with the JSP files? System has been in production for months with very few problems.
Donald, it would be cool to take a look at the particular file causing the crash. In other words is there a file that causes the system to crash being opened in editor?
In my case I can not open web module as well. I have no idea which file causes the crash. It is a NPE and it prevents me from expanding the tree so I can not click in any JSPs
java.awt.event.MouseEvent[MOUSE_PRESSED,(45,972),button=1,modifiers=Button1,extModifiers=Button1,clickCount=1] on frame0 java.lang.NullPointerException at com.intellij.psi.impl.source.tree.TreeUtil.addChildren(TreeUtil.java:185) at com.intellij.psi.impl.source.jsp.JspxParsing.parseJsp(JspxParsing.java:32) at com.intellij.psi.impl.source.tree.JspElementType$1.parseContents(JspElementType.java:12) at com.intellij.psi.impl.source.tree.ChameleonElement.transform(ChameleonElement.java:12) at com.intellij.psi.impl.source.parsing.ChameleonTransforming.transform(ChameleonTransforming.java:0) at com.intellij.psi.impl.source.tree.ChameleonElement.getTransformedLastOrSelf(ChameleonElement.java:31) at com.intellij.psi.impl.source.tree.SharedImplUtil.getLastChild(SharedImplUtil.java:13) at com.intellij.psi.impl.source.TreeWrapperPsiElement.getLastChild(TreeWrapperPsiElement.java:91) at com.intellij.psi.impl.source.jsp.JspJavaTextGenerator.(JspJavaTextGenerator.ja
"Maxim Shafirov (JetBrains)" ]]> wrote in message news:c8a8a1bfb9338c72872088f88e3@news.jetbrains.com...
Donald, it would be cool to take a look at the particular file causing the crash. In other words is there a file that causes the system to crash being opened in editor?
It's so bad that I'm going to have to give up on 3339 and go back to 3316. How can I find a copy of that? I tried editing the URL by hand, but I get a "File Not Found" error.
This issue caused by some unparsable file in your project. So you can try to find the file and send it to us.
Such a problem could be caused by number of reasons in html parsing so more files you submit more cases we have to fix. We've fixed one of our html insects (one from file that was posted by Mike) but I'm afraid there could be other cases. Anyway please try our next EAP build and if you still have problems try to find the cause file and send it to me directly (ik at intellij com) (preferable) or to this thread.
IK
Alex Roytman wrote:
In my case I can not open web module as well. I have no idea which file causes the crash. It is a NPE and it prevents me from expanding the tree so I can not click in any JSPs
java.awt.event.MouseEvent[MOUSE_PRESSED,(45,972),button=1,modifiers=Button1,extModifiers=Button1,clickCount=1] on frame0 java.lang.NullPointerException at com.intellij.psi.impl.source.tree.TreeUtil.addChildren(TreeUtil.java:185) at com.intellij.psi.impl.source.jsp.JspxParsing.parseJsp(JspxParsing.java:32) at com.intellij.psi.impl.source.tree.JspElementType$1.parseContents(JspElementType.java:12) at com.intellij.psi.impl.source.tree.ChameleonElement.transform(ChameleonElement.java:12) at com.intellij.psi.impl.source.parsing.ChameleonTransforming.transform(ChameleonTransforming.java:0) at com.intellij.psi.impl.source.tree.ChameleonElement.getTransformedLastOrSelf(ChameleonElement.java:31) at com.intellij.psi.impl.source.tree.SharedImplUtil.getLastChild(SharedImplUtil.java:13) at com.intellij.psi.impl.source.TreeWrapperPsiElement.getLastChild(TreeWrapperPsiElement.java:91) at com.intellij.psi.impl.source.jsp.JspJavaTextGenerator.<init>(JspJavaTextGenerator.ja
this problem occurs on all included files... If I work with JSP fragments as includes files these kind of errors occur. (Appears with Sitemesh decorator jsp fragments and include JSPs) Also, when opening the project's webapp folder, the tree shows a "loading..." string as the top entry of the webapp folder not disappearing anymore. After this, no more work on JSPs or other files is possible cause no more files could be opened.
Ok. Actually before next EAP any extra closed HTML tag can break code, though Project View parse all files in your project and there could be only one file which break parser and make IDEA unusable. After next EAP will be available please try it and if we fail to work with your project try to understand which file break parsing and send it to me.
Thanks, IK
Donald McLean wrote:
I also have quite a few JSP include files. I would be happy to provide them if you wish.
I was able to temporarily work around the problem by remapping all of my JSP files to be text files.
Ok. Actually before next EAP any extra closed HTML tag can break code, though Project View parse all files in your project and there could be only one file which break parser and make IDEA unusable. After next EAP will be available please try it and if we fail to work with your project try to understand which file break parsing and send it to me.
I think this is the same problem that makes #3339 unusable for me as well. Is it be possible to find the offending file by changing a logging setting? Or if this isn't possible right now, could you add that information in the next EAP?
It's a crude solution, but for those of us with lots of bad HTML in JSP files (ok, bad JSP files, too :( ), turning off JSP support by moving the .jsp extension from the JSP file type to the text file type seems to be the best solution until the next build is released. Just remember to turn it back on when we get the next build (hopefully soon? :) ).
Not in current build :(. In next eap you'll get text of your file on such a crush.
Well, something must have gone wrong here. It still crashes with the exact same error message but shows neither the name nor the contents of the problematic file and it's quite hard to make out which it is because the exception pops up no matter what file I open.
Try deleting your iws file -- that will reset the state of the project view
and seems to prevent the exeptions on startup. Unfortunately, it's sitll
impossible to open a folder with problematic JSP files in it (not sure if
all or only some cause the problem).
--Mike
Hello Donald,
DM> I'm having a severe repeatable problem in that every time that I
DM> open my web module, it corrupts the project and causes numerous IDEA
DM> exceptions (47331, 47323 for example).
Can you please say build number?
--
Alexey Efimov, Java Developer
Tops BI
http://www.topsbi.ru
Build: Sorry, I should have mentioned that. I was having the problem with 3326 and am still having it with 3339.
Deleting the IWS file did reset the project view.
There is nothing that is actually wrong with my JSP files, so if IDEA is having problems parsing them - and especially if this failure to parse them is causing these kinds of crashes - then this is an absolutely and completely unacceptable problem.
How do I know that there's nothing wrong with the JSP files? System has been in production for months with very few problems.
Donald
Donald,
it would be cool to take a look at the particular file causing the crash.
In other words is there a file that causes the system to crash being opened
in editor?
-
Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"
Maxim,
Everything crashes when I try to look at the web module in the project view. I don't even get the opportunity to bring a file up in the editor.
Donald
In my case I can not open web module as well. I have no idea which file
causes the crash. It is a NPE and it prevents me from expanding the tree so
I can not click in any JSPs
java.awt.event.MouseEvent[MOUSE_PRESSED,(45,972),button=1,modifiers=Button1,extModifiers=Button1,clickCount=1]
on frame0
java.lang.NullPointerException
at
com.intellij.psi.impl.source.tree.TreeUtil.addChildren(TreeUtil.java:185)
at
com.intellij.psi.impl.source.jsp.JspxParsing.parseJsp(JspxParsing.java:32)
at
com.intellij.psi.impl.source.tree.JspElementType$1.parseContents(JspElementType.java:12)
at
com.intellij.psi.impl.source.tree.ChameleonElement.transform(ChameleonElement.java:12)
at
com.intellij.psi.impl.source.parsing.ChameleonTransforming.transform(ChameleonTransforming.java:0)
at
com.intellij.psi.impl.source.tree.ChameleonElement.getTransformedLastOrSelf(ChameleonElement.java:31)
at
com.intellij.psi.impl.source.tree.SharedImplUtil.getLastChild(SharedImplUtil.java:13)
at
com.intellij.psi.impl.source.TreeWrapperPsiElement.getLastChild(TreeWrapperPsiElement.java:91)
at
com.intellij.psi.impl.source.jsp.JspJavaTextGenerator.(JspJavaTextGenerator.ja "Maxim Shafirov (JetBrains)" ]]> wrote in message
news:c8a8a1bfb9338c72872088f88e3@news.jetbrains.com...
>
>
It's so bad that I'm going to have to give up on 3339 and go back to 3316. How can I find a copy of that? I tried editing the URL by hand, but I get a "File Not Found" error.
I'd hate to have to go all the way back to 4.5.
Donald
This issue caused by some unparsable file in your project. So you can
try to find the file and send it to us.
Such a problem could be caused by number of reasons in html parsing so
more files you submit more cases we have to fix. We've fixed one of our
html insects (one from file that was posted by Mike) but I'm afraid
there could be other cases. Anyway please try our next EAP build and if
you still have problems try to find the cause file and send it to me
directly (ik at intellij com) (preferable) or to this thread.
IK
Alex Roytman wrote:
Igor,
this problem occurs on all included files...
If I work with JSP fragments as includes files these kind of errors occur. (Appears with Sitemesh decorator jsp fragments and include JSPs)
Also, when opening the project's webapp folder, the tree shows a "loading..." string as the top entry of the webapp folder not disappearing anymore.
After this, no more work on JSPs or other files is possible cause no more files could be opened.
Hope that helps traceing the bug...
Rainer
I also have quite a few JSP include files. I would be happy to provide them if you wish.
I was able to temporarily work around the problem by remapping all of my JSP files to be text files.
Donald
Ok. Actually before next EAP any extra closed HTML tag can break code,
though Project View parse all files in your project and there could be
only one file which break parser and make IDEA unusable. After next EAP
will be available please try it and if we fail to work with your project
try to understand which file break parsing and send it to me.
Thanks,
IK
Donald McLean wrote:
Igor Kuralenok (JetBrains) wrote:
I think this is the same problem that makes #3339 unusable for me as well.
Is it be possible to find the offending file by changing a logging setting?
Or if this isn't possible right now, could you add that information in the
next EAP?
Sascha
It's a crude solution, but for those of us with lots of bad HTML in JSP files
(ok, bad JSP files, too :( ), turning off JSP support by moving the .jsp
extension from the JSP file type to the text file type seems to be the best
solution until the next build is released. Just remember to turn it back
on when we get the next build (hopefully soon? :) ).
--Mike
Sascha Weinreuter wrote:
Not in current build :(. In next eap you'll get text of your file on
such a crush.
IK
Igor Kuralenok (JetBrains) wrote:
Well, something must have gone wrong here. It still crashes with the exact
same error message but shows neither the name nor the contents of the
problematic file and it's quite hard to make out which it is because the
exception pops up no matter what file I open.
Sascha