Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
readme.txt | 2010-04-20 | 2.9 kB | |
Calltrace2Seq.zip | 2010-04-20 | 8.0 MB | |
Totals: 2 Items | 8.0 MB | 0 |
************************************************************************************ * Copyright 2009 Syed Ali Jafar Naqvi * * * * This file is part of Java Call Tracer. * * * * Java Call Tracer is free software: you can redistribute it and/or modify * * it under the terms of the Lesser GNU General Public License as published by * * the Free Software Foundation, either version 3 of the License, or * * (at your option) any later version. * * * * Java Call Tracer is distributed in the hope that it will be useful, * * but WITHOUT ANY WARRANTY; without even the implied warranty of * * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * * Lesser GNU General Public License for more details. * * * * You should have received a copy of the Lesser GNU General Public License * * along with Java Call Tracer. If not, see <http://www.gnu.org/licenses/>. * ************************************************************************************ Program Arguments ----------------- INPUTXMLFILE-C:\\test.xml OUTPUTFOLDER-C:\\ OUTPUTFILENAME-out Using the Calltrace2Seq tool ---------------------------- Once you have generated a XML output using the calltracer tool you can use the Calltrace2Seq tool to convert it to a UML sequence diagram. Incase your java program has a single thread the output of the calltracer tool will have just one thread element. You need to just take out the thread element, put it into a file and feed it to the Calltrace2Seq tool. You can choose to change the value of the id attribute of the thread element to a more legible value. The id element is used to name the sequence diagram by the Calltrace2Seq tool. Incase your java program has multiple threads, you will find that the generated output has multiple Thread elements. Each thread element has the call trace coresponding to a thread of the program. You can either choose to take each thread element and convert it to a UML sequence diagram individually or you can use two or more thread elements to generate one UML sequence diagram. In the former case just take the thread element you are interested in, put it into a file and feed it to the Calltrace2Seq tool. In the later case just add a wrapper element around the thread elements and add an id attribute to the wrapper element and give a legible name. Then put the entire thing in a file and feed it to the Calltrace2Seq tool. Please note that the output generated by the calltracer tool has some header information that will not allow it (the output) to be used directly as an input to the Calltrace2Seq tool. You can either copy the thread elements, as described above, into another file and feed it to the Calltrace2Seq tool or remove the header from the output file and use it directly.