I run into this odd issue where the symbol's parent is incorrectly mapped when declare a java stored procedure is the package body. In the example, I was expected to see all the functions/procedure to be sibling of each other with the root symbol mapped to package body ABC. Instead all the functions/procedure declared after the top level java stored procedure call specification become child/children of that java call specification.
Java stored procedures are currently not supported, so RegExpParser incorrectly uses the following procedures as nested procedures.
I will improve regExpParser to support Java procedure.
First of all, thank you for a great extension.
I run into this odd issue where the symbol's parent is incorrectly mapped when declare a java stored procedure is the package body. In the example, I was expected to see all the functions/procedure to be sibling of each other with the root symbol mapped to package body ABC. Instead all the functions/procedure declared after the top level java stored procedure call specification become child/children of that java call specification.
The symbol list also show that the as well.