Red Hat DIRECTORY SERVER 7.1 - GATEWAY CUSTOMIZATION Informations techniques Page 156

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 186
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 155
Using the Profiler to Troubleshoot Performance Problems
Page 156 Identity Manager 7.1 Update 1 Release Notes
Java filters are given in terms of method patterns, and they are expressed in patterns that include or
exclude based on canonical method name. Where a canonical method name is:
fully-qualified-class-name.method-name
(
parameter-type-1, parameter-type-2, ...
)
Here are a few examples:
To exclude all constructors, enable the Exclude box and add the following filter:
*.<init>(*)
To exclude all constructors with a single
org.w3c.dom.Element
parameter, enable the
Exclude box and add the following filter:
*.<init>(org.w3c.dom.Element)
To exclude all Identity Manager classes, enable the Exclude box and add the following
filters:
"com.waveset.*"
"com.sun.idm.*"
To instrument your custom code only, disable the Exclude box, remove the initial
*
include
filter, and then add the following filter:
"com.yourcompany.*"
If necessary, you can instrument other JARs by modifying the following lines in
build.xml
as
appropriate. For example,
NOTE For constructors, method-name is
<init>
.
NOTE The last two examples are currently equivalent because the filters are
applied only to your custom classes and Identity Manager classes.
<instrument todir="${lighthouse-dir-profiler}/WEB-INF"
verbose="${instrumentor.verbose}" includeMethods="${profiler.includes}"
excludeMethods="${profiler.excludes}">
<fileset dir="${lighthouse-dir}/WEB-INF">
<include name="lib/idm*.jar"/>
<include name="classes/**/*.class"/>
</fileset>
</instrument>
Vue de la page 155
1 2 ... 151 152 153 154 155 156 157 158 159 160 161 ... 185 186

Commentaires sur ces manuels

Pas de commentaire