A call to PropertyEditorManager.findEditor() uses a global JVM lock, basically:
public static synchronized PropertyEditor findEditor(Class targetType) {
... // lots of expensive class loading and exception handling stuff goes here
}
Anyway, I've been using org/jboss/util/propertyeditor/PropertyEditors.java to render a page (convert some objects -> printable values) and it doesn't work too hot under load, especially with multiple threads. I'll probably rewrite what I worked on, but I'm curious if this class, say for doing service.xml deployments it's a performance concern.
