<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to patches</title><link href="https://sourceforge.net/p/jrat/patches/" rel="alternate"/><link href="https://sourceforge.net/p/jrat/patches/feed.atom" rel="self"/><id>https://sourceforge.net/p/jrat/patches/</id><updated>2008-07-09T22:31:21Z</updated><subtitle>Recent changes to patches</subtitle><entry><title>jrat and XSL</title><link href="https://sourceforge.net/p/jrat/patches/2/" rel="alternate"/><published>2008-07-09T22:31:21Z</published><updated>2008-07-09T22:31:21Z</updated><author><name>Shaun Addison</name><uri>https://sourceforge.net/u/shaunaddison/</uri></author><id>https://sourceforge.net32c83755f4d44b39dbec2e062bf80d0f0e0123e9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I was using JRat to profile a JEE application in weblogic. I struck issues with an XSL-FO component. It appears to define classes with no explicit class name. Whilst the java.lang.ClassLoader class has deprecated&lt;br /&gt;
the defineClass method without a name the other defineClass methods seem to allow a null to be passed: "name - The expected binary name of the class, or null if not known" It seems to the be case for JDK 1.5 and 6. &lt;/p&gt;
&lt;p&gt;This was causing JRat some NPEs around the JVMTI stuff. I patched the JVMTI classes to check for the null and after this it worked fine. This issue was listed under the JRat forum:&lt;br /&gt;
failed to transform : null      ernitingoel     0   2008-06-04 18:56&lt;/p&gt;
&lt;p&gt;Also under Weblogic it appears you need to always exclude weblogic.management.* This will resolve another issue on the forum:&lt;br /&gt;
Stack Dump with BEA     nobody      0   2007-11-29 00:03&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>small fixes and minor enhancement</title><link href="https://sourceforge.net/p/jrat/patches/1/" rel="alternate"/><published>2004-06-10T11:19:50Z</published><updated>2004-06-10T11:19:50Z</updated><author><name>Bill Jdap</name><uri>https://sourceforge.net/u/billjdap/</uri></author><id>https://sourceforge.net5dc9c0459548615996149aacec0d5e82160161ec</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi all,&lt;/p&gt;
&lt;p&gt;This tool was very useful for me, but I found some &lt;br /&gt;
small problems and fixed them. Attached Patch was &lt;br /&gt;
generated from Eclipse 3.0M9 and should be applyable&lt;br /&gt;
to the 'src' folder of the jrat2 project.&lt;/p&gt;
&lt;p&gt;Regards &lt;br /&gt;
Bill Jdap&lt;/p&gt;
&lt;p&gt;Patch includes :&lt;/p&gt;
&lt;p&gt;Change in ...core.RuntimeContextImpl&lt;br /&gt;
- Added new property "jrat.baseDir" to define a base&lt;br /&gt;
directory for jrat output.&lt;/p&gt;
&lt;p&gt;Change in ...core.spi.ViewerXmlHandler&lt;br /&gt;
- only create a new viewerFactory in first&lt;br /&gt;
startElement if not already set.&lt;/p&gt;
&lt;p&gt;Change in ...provide.tree.StackNode&lt;br /&gt;
- added maxConcurrentThreads to output as attribute 'mct'&lt;br /&gt;
- changed method printChildren(..) to allow&lt;br /&gt;
modifications to children&lt;br /&gt;
even after first flush. The variable 'children' was&lt;br /&gt;
set to an unmodifiable&lt;br /&gt;
Map, but just using a copy of the current value for&lt;br /&gt;
iterating over the&lt;br /&gt;
children also gives necessary thread safeness.&lt;/p&gt;
&lt;p&gt;Change in ...provider.tree.ui.StackTableModel&lt;br /&gt;
- added additional column "Thread" showing the max&lt;br /&gt;
concurrent threads&lt;/p&gt;
&lt;p&gt;Change in&lt;br /&gt;
...provider.tree.ui.TreeOutputXmlViewerFactory    &lt;br /&gt;
- fixed order of min and max duration in&lt;br /&gt;
startElement() (see Bug 859597)&lt;br /&gt;
- added reading of maxConcurrentThreads from attribute&lt;br /&gt;
'mct'&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>