![]() View how it's connected to other calls in the Trace, then backtrack to its calling component and open its source file.Start with a SQL command of interest - like an INSERT.Let's say you want to know what code modifies data in the database. Drill down the execution details of code and SQL in the execution Trace.Ġ1:45 Or, you can use a bottom-up approach.Navigate to sources of classes and functions directly from the diagrams so you don't have to look for them manually.Start with the big picture of your software design and view all code components in the Dependency Map - Web Service endpoints, Java packages/classes/functions and SQL commands and their inter-dependencies.Select an AppMap from the list of all AppMaps found in the project folders, or search for an AppMap with a specific phrase in its name, for example "create owner".ĭouble click on an AppMap in the list, an interactive diagram viewer opens.Ġ1:25 Discover how the Pet Clinic application works in the AppMap diagrams. Or, press CTRL or COMMAND + SHIFT + A, then type "AppMaps" in the search box and pick the `AppMaps View" from the list. Here is an example for the Pet Clinic application that is used in this demo:Įnter fullscreen mode Exit fullscreen modeĠ1:10 When you run the Maven test phase, the AppMap recording agent will record AppMaps from the tests and save them in the $buildDir/appmap folder of the project, one AppMap per each recorded test case.Ġ1:17 Open the AppMaps view - click on the AppMaps tab in the UI. You should add all the Java packages of your project. The AppMap framework uses a file called appmap.yml to determine which code to map.Ġ0:20 Create a new file appmap.yml in the root folder of your project. When the IDE restarts, the AppMap plugin is installed and ready for viewing AppMaps.Ĭonfigure AppMap for the Pet Clinic recording ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |