6:39 p.m.
Incorrect classloading using Class.forName
------------------------------------------
Key: JBESB-466
URL: http://jira.jboss.com/jira/browse/JBESB-466
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.0 Maintenance Pack 1
Class.forName is used throughout the codebase but this does not work correctly when used
in app servers etc. Classes (and resources) should be looked using the thread context
classloader before anything else.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:30 p.m.
New subject: [JBoss JIRA] Resolved: (JBESB-466) Incorrect classloading using Class.forName
[ http://jira.jboss.com/jira/browse/JBESB-466?page=all ]
Bill Burke resolved JBESB-466.
------------------------------
Resolution: Done
Fixed..Don't know your procedure for closing. It is tested in the simple-scoped test
under qa/junit
Incorrect classloading using Class.forName
------------------------------------------
Key: JBESB-466
URL: http://jira.jboss.com/jira/browse/JBESB-466
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.0 Maintenance Pack 1
Class.forName is used throughout the codebase but this does not work correctly when used
in app servers etc. Classes (and resources) should be looked using the thread context
classloader before anything else.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:20 p.m.
New subject: [JBoss JIRA] Reopened: (JBESB-466) Incorrect classloading using Class.forName
[ http://jira.jboss.com/jira/browse/JBESB-466?page=all ]
Kevin Conner reopened JBESB-466:
--------------------------------
Resources have still to be done
Incorrect classloading using Class.forName
------------------------------------------
Key: JBESB-466
URL: http://jira.jboss.com/jira/browse/JBESB-466
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.0 Maintenance Pack 1
Class.forName is used throughout the codebase but this does not work correctly when used
in app servers etc. Classes (and resources) should be looked using the thread context
classloader before anything else.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:12 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-466) Incorrect classloading using Class.forName
[ http://jira.jboss.com/jira/browse/JBESB-466?page=comments#action_12356368 ]
Bill Burke commented on JBESB-466:
----------------------------------
SimpleDataSource didn't like this change. I switched it back to Class.forName() so
the unit test could pass.
Incorrect classloading using Class.forName
------------------------------------------
Key: JBESB-466
URL: http://jira.jboss.com/jira/browse/JBESB-466
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.0 Maintenance Pack 1
Class.forName is used throughout the codebase but this does not work correctly when used
in app servers etc. Classes (and resources) should be looked using the thread context
classloader before anything else.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:18 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-466) Incorrect classloading using Class.forName
[ http://jira.jboss.com/jira/browse/JBESB-466?page=comments#action_12356370 ]
Kevin Conner commented on JBESB-466:
------------------------------------
Okay, thanks. Will try with my helper class.
Incorrect classloading using Class.forName
------------------------------------------
Key: JBESB-466
URL: http://jira.jboss.com/jira/browse/JBESB-466
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.0 Maintenance Pack 1
Class.forName is used throughout the codebase but this does not work correctly when used
in app servers etc. Classes (and resources) should be looked using the thread context
classloader before anything else.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:22 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-466) Incorrect classloading using Class.forName
[ http://jira.jboss.com/jira/browse/JBESB-466?page=comments#action_12356391 ]
Mark Little commented on JBESB-466:
-----------------------------------
Is this an issue with SimpleDataSource that we need to track?
Incorrect classloading using Class.forName
------------------------------------------
Key: JBESB-466
URL: http://jira.jboss.com/jira/browse/JBESB-466
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.0 Maintenance Pack 1
Class.forName is used throughout the codebase but this does not work correctly when used
in app servers etc. Classes (and resources) should be looked using the thread context
classloader before anything else.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:54 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-466) Incorrect classloading using Class.forName
[ http://jira.jboss.com/jira/browse/JBESB-466?page=comments#action_12356503 ]
Kevin Conner commented on JBESB-466:
------------------------------------
Modified resource lookup to use helper class.
Incorrect classloading using Class.forName
------------------------------------------
Key: JBESB-466
URL: http://jira.jboss.com/jira/browse/JBESB-466
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.0 Maintenance Pack 1
Class.forName is used throughout the codebase but this does not work correctly when used
in app servers etc. Classes (and resources) should be looked using the thread context
classloader before anything else.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:01 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-466) Incorrect classloading using Class.forName
[ http://jira.jboss.com/jira/browse/JBESB-466?page=comments#action_12356504 ]
Kevin Conner commented on JBESB-466:
------------------------------------
Fix for SimpleDataSource has been checked into HEAD with revision 10318 and the MP1 branch
with revision 10319.
Incorrect classloading using Class.forName
------------------------------------------
Key: JBESB-466
URL: http://jira.jboss.com/jira/browse/JBESB-466
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.0 Maintenance Pack 1
Class.forName is used throughout the codebase but this does not work correctly when used
in app servers etc. Classes (and resources) should be looked using the thread context
classloader before anything else.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:01 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-466) Incorrect classloading using Class.forName
[ http://jira.jboss.com/jira/browse/JBESB-466?page=all ]
Kevin Conner closed JBESB-466.
------------------------------
Resolution: Done
Incorrect classloading using Class.forName
------------------------------------------
Key: JBESB-466
URL: http://jira.jboss.com/jira/browse/JBESB-466
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.0 Maintenance Pack 1
Class.forName is used throughout the codebase but this does not work correctly when used
in app servers etc. Classes (and resources) should be looked using the thread context
classloader before anything else.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:21 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-466) Incorrect classloading using Class.forName
[ http://jira.jboss.com/jira/browse/JBESB-466?page=comments#action_12360805 ]
Daniel Bevenius commented on JBESB-466:
---------------------------------------
I noticed that the method resolveComposerClass (line 274) in JmsGatewayListener still uses
Class.forName(). Is this intentional or should it be using ClassUtil.forName?
Incorrect classloading using Class.forName
------------------------------------------
Key: JBESB-466
URL: http://jira.jboss.com/jira/browse/JBESB-466
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2 Milestone Release 1
Class.forName is used throughout the codebase but this does not work correctly when used
in app servers etc. Classes (and resources) should be looked using the thread context
classloader before anything else.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:32 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-466) Incorrect classloading using Class.forName
[ http://jira.jboss.com/jira/browse/JBESB-466?page=comments#action_12360812 ]
Kevin Conner commented on JBESB-466:
------------------------------------
Nope, it should be using ClassUtil. It looks like this was reintroduced with a code
merge.
There is another instance of this in the MessageComposer.Factory class so we should do
another check for class/resource usage.
Incorrect classloading using Class.forName
------------------------------------------
Key: JBESB-466
URL: http://jira.jboss.com/jira/browse/JBESB-466
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2 Milestone Release 1
Class.forName is used throughout the codebase but this does not work correctly when used
in app servers etc. Classes (and resources) should be looked using the thread context
classloader before anything else.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6213
days inactive
6261
days old
10 comments
4 participants
participants (4)
-
Bill Burke (JIRA) -
Daniel Bevenius (JIRA)
-
Kevin Conner (JIRA)
-
Mark Little (JIRA)