[
https://jira.jboss.org/jira/browse/JBPM-1976?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-1976:
-----------------------------------
Fix Version/s: jBPM 3.2.5.SP6
Merging changes into SOA branch.
Bad usage of ClassLoader.loadClass() under JDK 6
------------------------------------------------
Key: JBPM-1976
URL:
https://jira.jboss.org/jira/browse/JBPM-1976
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.5 GA
Reporter: Alejandro Guizar
Assignee: Thomas Diesler
Fix For: jBPM 3.2.6 GA , jBPM 3.2.5.SP6
Any class name provided as a String parameter to methods in ClassLoader must be a binary
name as defined by the JLS (1). In particular, array syntax is not allowed, unless the
system property sun.lang.ClassLoader.allowArraySyntax is set to true.
Sun recommends (2) replacing
myClassLoader.loadClass(className);
with
Class.forName(className,false,myClassLoader);
The first form has plenty of occurrences in the jBPM codebase. No bug has come to my
attention with respect to array class loading. Anyhow, it is worthwhile to fix any
potential problem in advance as other JBoss projects have (3).
(1)
http://java.sun.com/javase/6/docs/api/java/lang/ClassLoader.html#name
(2)
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6516909
(3)
https://jira.jboss.org/jira/browse/JBREM-659 *
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2990
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira