What steps will reproduce the problem? 1. Create a simple application which utilizes Xerces as described in Xerces tutorial: http://www.totheriver.com/learn/xml/xmltutorial.html#6.1.1 2. Execute it together with jTracert
What is the expected output? What do you see instead?
jTracert should analyze the application and build the sequence diagrams. Instead we get a null pointer exception as shown below:
java.lang.NullPointerException at com.google.code.jtracert.traceBuilder.impl.MethodCallTraceBuilderImpl.leave(MethodCallTraceBuilderImpl.java:323) at com.google.code.jtracert.samples.Xerces.main(Unknown Source)
Please use labels and text to provide additional information.
GNU/Linux java version "1.6.0_07" Java(TM) SE Runtime Environment (build 1.6.0_07-b06) Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
Comment #1
Posted on Feb 9, 2009 by Happy PandaSample application 'xerces' is now added to SVN
Comment #2
Posted on Feb 10, 2009 by Happy PandaThe problem is actually not concerned with Xerces.
jTracert incorrectly analyzes constructors - when one constructor calls the other one, or parent constructor. We cannot insert custom code before parent constructor call, so this can be a problem.
Priority raised to Critical.
Comment #3
Posted on Feb 10, 2009 by Happy PandaI've created a separate branch for fixing this defect, since it may require significant changes and may take a lot of time. http://code.google.com/p/jtracert/source/browse/#svn/branches/issue9
Comment #4
Posted on Feb 17, 2009 by Happy PandaFixed in svn revision r126 ( issue9 branch )
Comment #5
Posted on Mar 4, 2009 by Happy PandaFixed in jTracert version 0.0.5
Status: Verified
Labels:
Type-Defect
Priority-Critical
Component-Logic