This program is free software; you can redistribute it and/or modify
+it under the terms of version 3 of the GNU Lesser General Public
+License or later as published by the Free Software Foundation.
+
Program author:
Svjatoslav Agejenko
@@ -171,6 +216,9 @@ for the JavaScript code in this tag.
@@ -182,69 +230,134 @@ automatically visualizing its structure.
-JavaInspect is a Java library that you can embed into your Java
-project with a few lines of Maven configuration and then visualize any
-part of your Java program structure with few simple JavaInspect API
-calls at application runtime.
+JavaInspect is a Java library that primarily uses Java reflection to
+discover and visualize any part of Java program provided that
+classes to be visualised are available in the classpath.
-JavaInspect uses Java reflection to discover class relations and
-structure and produces GraphViz dot file that describes your
-application. Then launches GraphViz to generate bitmap graph in PNG
-format on your Desktop directory.
+JavaInspect currently has no GUI, configuration files, embedded
+scripting support, direct Maven or Ant integration. The only way to
+instuct Javainspect what to do is by using its Java API.
-
-
-
-
2 Current status
-
-This is simple utility, quickly written. Tested on GNU Linux (can be
-relatively simply ported to other operating systems too). So far I
-used it for my own needs. There might be bugs and missing
-features. Feedback and code contributions are welcome.
+To get JavaInspect into same classpath with your projecs I so far came
+up with 2 solutions:
-
-
-
-
3 Example graphs
-
+
+
Add JavaInspect library in your project as a dependency.
+
+
Create new Java project for the purpose visualizing your other
+projects and include JavaInspect and your projecs binary artifacts
+(Jar's) into new project classpath. Built binary Jar's (with no
+source code) are sufficient because JavaInspect operates via
+reflection.
+
+
+
-Example visualization of Sixth project: architecture graphs.
+After discovering application structure and optionally filtering out
+unimportant parts, JavaInspect produces GraphViz dot file that
+describes data to be visualized. Then launches GraphViz to generate
+bitmap graph in PNG format. By default on your Desktop directory.
-A very simple example:
+Note: GraphViz is developed and tested so far only on GNU/Linux.
+Currently the only way to control JavaInspect is by using Java
+API. Simple Java based control/configuration code needs to be written
+for each project. I usually put such code into directories devoted for
+JUnit tests. Because it needs not to be compiled/embedded into final
+product or project artifact I'm just willing to visualize.
+
+
+
+Control code in general does the following:
+
+
+
Create graph object.
+
+
Java reflection/classloaders does not provide mechanism for
+discovering all classes under given package. Therefore you need to
+declare at least some classes to be added to the graph by:
+
+
Manually adding individual classes to the graph.
+
+
and/or: Let GraphViz recursively scan and parse specified
+directories with Java source code files to discover class names.
+
+
For every class added to the graph, GraphViz will recursively
+inspect it and add all referecned classes to the graph as well.
+
+
+
+
Graphs easilly get very big and complex so optionally we filter
+important code using classname wildcards patterns based blacklist
+and/or whitelist.
+
+
Optionally we can tune some rendering parameters like:
+
+
Possibility to remove orphaned classes (classes with no
+references) from the graph.
+
+
Specify target directory for generated visualization
+files. (Default is user desktop directory)
+
+
Keep intermediate GraphViz dot file for later inspection.
+
+
+
+
Render graph.
+
+
-
-
4 Usage example 1
-
+
+
+
3.1 example 1: individually picked objects
+
This example demonstrates generating of class graph from hand picked
-classes.
+classes and visualizing GraphViz itself.
@@ -252,22 +365,31 @@ classes.
// Create graphfinalClassGraphgraph = newClassGraph();
-// While classes and objects can be immediately passed to ClassGraph
-// constructor as arguments, it is also possible to add them one by
-// one as in the following example.
+// Add some random object to the graph. GraphViz will detect Class from
+// the object.
+graph.add(graph);
-// Add some object to the graph.
-graph.addObject(graph);
+// Also add some random class to the graph.
+graph.add(Utils.class);
-// Add some class to the graph.
-graph.addClass(Utils.class);
+// Keep intermediary GraphViz DOT file for reference.
+graph.setKeepDotFile(true);
// Produce bitmap image titled "JavaInspect.png" to the user Desktop
-// directory and keep intermediary GraphViz DOT file for reference.
-graph.generateGraph("JavaInspect", true);
+// directory
+graph.generateGraph("JavaInspect");
+
+Note: if desired, more compact version of the above:
+
-Recursively scan current directory for Java source code and attempt to
-detect class names from there to be added to the graph.
-
-
+
+
3.2 example 2: scan java code, apply filters
+
-
graph.addProject(".");
+
// Create graph
+finalClassGraphgraph = newClassGraph();
+
+// Recursively scan current directory for Java source code and attempt
+// to detect class names from there to be added to the graph.
+graph.addProject(".");
// Blacklist example classes from being shown on the graph
-graph.getFilter().blacklistClassPattern(
- "eu.svjatoslav.inspector.java.structure.example.*");
+graph.blacklistClassPattern("eu.svjatoslav.inspector.java.structure.example.*");
// do not show single classes with no relationships on the graph
graph.hideOrphanedClasses();
@@ -316,9 +437,22 @@ Result:
-
-
6 Embedding JavaInspect in your Maven project
-
+
+
3.3 example 3: GraphViz embedded in another project
BUG: Should not hide references if there are too many of them to
-classes if referring classes are not visible anyway because of
-blacklist/whitelist rules. Basically reference counting should
-exclude not visible classes.
+
BUG: Should not hide references if there are too many of them to classes if
+referring classes are not visible anyway because of blacklist/whitelist rules.
+Basically reference counting should exclude not visible classes.
-
BUG: Current code is quite messy (because of lack of time) things
-were implemented ad-hoc. Needs cleanup/refactoring for better
-readability.
+
-
+