Details
-
Type:
Bug
-
Status:
Closed
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
Due to ClassCastExceptions after JBoss hot deploy issue, I am wondering if changing Class.forName() to Thread.currentThread().getContextClassLoader().loadClass() as recommended by JBoss and this should also work on normal case.
The problem is classes are getting cached and I am not sure if this will fix the problem but atleast it will eliminate this option.
Amad
Activity
Hi Amad,
this change is already present in the latest releases. Does it work for you?
- Jörg
Show
Jörg Schaible
added a comment - Hi Amad,
this change is already present in the latest releases. Does it work for you?
Jörg
Jörg Schaible
added a comment - Hi Amad,
this change is already present in the latest releases. Does it work for you?
Jörg
Latest code in CVS swaps tries to use the thread context loader BEFORE the standard mechanism. Try that and let me know if it works.
Sorry, the build server is down, so you'll have to build from CVS yourself.