Handling exception in Javaparser

Question

I am trying to handle the exception produced by Javaparser library due to token error. I used the following code.

String content=getTheSource();
    ByteArrayInputStream bin=new ByteArrayInputStream(content.getBytes());
    try
    {
        CompilationUnit cu=JavaParser.parse(bin);
    } catch (Exception e) {
        // TODO Auto-generated catch block
        //e.printStackTrace();
                    //my handling code here
    }finally{
        bin.close();
    }

However, the exception was never caught and I am getting a different exception generated from somewhere else. I got this exception:

Exception in thread "main" japa.parser.TokenMgrError: Lexical error at line 1, column 16. Encountered: "#" (35), after : "" at japa.parser.ASTParserTokenManager.getNextToken(ASTParserTokenManager.java:2247) at japa.parser.ASTParser.jj_ntk(ASTParser.java:9986) at japa.parser.ASTParser.ClassOrInterfaceBody(ASTParser.java:926) at japa.parser.ASTParser.ClassOrInterfaceDeclaration(ASTParser.java:604) at japa.parser.ASTParser.TypeDeclaration(ASTParser.java:524) at japa.parser.ASTParser.CompilationUnit(ASTParser.java:269) at japa.parser.JavaParser.parse(JavaParser.java:81) at japa.parser.JavaParser.parse(JavaParser.java:94) at misc.CompileTest.main(CompileTest.java:45)

Any idea, how to handle the exception? Thanks in advance

yup, I did. Just I had to catch TokenMgrError, but I was trying to catch an exception, and TokenMgrError is not a subclass of Exception. — Masud Rahman, Oct 20 '13 at 17:11
Ahh ok, I ended up finding a fork of the project that fixed my errors - https://github.com/before/javaparser — facetoe, Nov 01 '13 at 14:32

score 1 · Answer 1 · answered Dec 23 '16 at 14:00

As the name indicates, TokenMgrError is an error. So you have to catch an Error instead of Exception. If you want to catch both Error and Exception, you can use Throwable instead.

Originally, this error is throwed by JavaCC (TokenMgrError) which is used by Javaparser.

score 1 · Answer 2 · answered Aug 10 '17 at 15:28

1

From version 3 on, JavaParser will/should not throw this error anymore.

answered Aug 10 '17 at 15:28

Danny

161
1
6

Handling exception in Javaparser

2 Answers2