Loading Profile...
Twitter, 
Facebook, or email.
I have a pretty big ejb application comprising of more than 20 modules. I recorded the application for use cases and am playing back in chronon debugger on eclipse. I went to the concerned method and clicked on "run to method". Chronon opened one more editor view for the same class but as a non-compilable unit. So, I am able to view the chronon recorded information but not able to navigate methods, etc., Why is this happening?
PS:- My entire project is build using Maven.
Current line / Java Class is not shown as a compilation unit
Official Responses
-
EMPLOYEE
I’m happy
With the release of Chronon 1.6 we have now added the ability to specify 'Source Lookup' paths.
This should solve your issue and allow you to point Chronon to the correct projects to look for source code.
More about the release here:
http://eblog.chrononsystems.com/chron...
More about the features here:
-
ok, so here is the reason for the issue:
Since you made the recording external to eclipse, when Chronon tries to open it, it doesnt see a build path, which is usually assigned by a 'launch configuration' when you record from within eclipse.
So seeing no build path, Chronon doesnt have a choice but to fall back to the 'search' method of looking for the file. Maybe if you closed the top most project 'nlt', which is not a true java project and just contains the other projects, the search api will be able to select an actual compilation unit by looking at a 'Java Project' instead of just a 'Project'.
Note that we will have provide some gui so that you can choose the 'source lookup path' for an external recording in a future update.
-
Chronon looks for the classname using the 'Build Path' of a java project (as shown in the project>preferences>Java Build Path).
Failing to find a file there, it literally does a 'search' in the workspace for a file for that class.
Looking at your project, the folders inside it dont seem to marked as 'src' folders. It seems that is what is causing the issue.Comment -
-
I actually would like to know a little more about your setup so we can solve this for you in the next update.
If the file is not in the build path, how do you get eclipse to see it as a 'compilation unit' in the first place? -
-
Mine is a maven project. My main pom.xml generates an ejb and includes multiple other modues with their own dedicated pom.xml. Since I am currently browsing the entire project with the help of Maven plugin, I guess eclipse is indeed not identifying the build setup correctly.- view 1 more comment
-
-
I think this would be the only solution in my scenario.
-
-
for now, yes. But given your use case, we will work on updating the plugin so that you dont have to do this.
-
-
-
-
Can you post a screenshot with the 'GeneralService.java' on the left hand side in focus. So I can see how eclipse recognizes it as a compilation unit, by looking at the breadcrumb bar.
-
-
Here you go..
-
-
ok, so here is the reason for the issue:
Since you made the recording external to eclipse, when Chronon tries to open it, it doesnt see a build path, which is usually assigned by a 'launch configuration' when you record from within eclipse.
So seeing no build path, Chronon doesnt have a choice but to fall back to the 'search' method of looking for the file. Maybe if you closed the top most project 'nlt', which is not a true java project and just contains the other projects, the search api will be able to select an actual compilation unit by looking at a 'Java Project' instead of just a 'Project'.
Note that we will have provide some gui so that you can choose the 'source lookup path' for an external recording in a future update. -
-
EMPLOYEE
I’m happy
With the release of Chronon 1.6 we have now added the ability to specify 'Source Lookup' paths.
This should solve your issue and allow you to point Chronon to the correct projects to look for source code.
More about the release here:
http://eblog.chrononsystems.com/chron...
More about the features here:
-
