Opened 16 years ago
Closed 16 years ago
#3316 closed Bug (expired)
ConnectorHandler doesn`t work in Grails
Reported by: | Darran | Owned by: | |
---|---|---|---|
Priority: | Must have (possibly next milestone) | Milestone: | |
Component: | Server : Java | Version: | SVN (FCKeditor) - Retired |
Keywords: | Pending | Cc: |
Description
The ConnectorHandler can`t dynamically load a Connector class when the Connector class is part of the Grails app.
The line Class<?> clazz = Class.forName(className);
causes a ClassNotfoundException.
If this is changed to Class<?> clazz = Thread.currentThread().getContextClassLoader().loadClass(className);
it will work, see http://www.nabble.com/ClassNotFoundException-with-Class.forName-td18194398.html
for details.
Change History (8)
comment:1 Changed 16 years ago by
Priority: | Normal → High |
---|---|
Version: | FCKeditor 2.6.4 → SVN (FCKeditor) |
comment:2 follow-up: 3 Changed 16 years ago by
FYI I found this issue when creating a Connector from within a Grails app. I`ve not tested creating a Connector in Java then dropping the jar into the grails app.
comment:3 Changed 16 years ago by
Replying to Darran:
FYI I found this issue when creating a Connector from within a Grails app. I`ve not tested creating a Connector in Java then dropping the jar into the grails app.
I have already realized that. What I was refering it, is that I'd like you to check our other interfaces from within your app. They will probably fail too. I just want to make sure.
comment:4 Changed 16 years ago by
I'd like you to test you case with other interfaces as well. Without your participation a real test and verification is not possible.
comment:6 Changed 16 years ago by
Have you been able to reproduce this bug with the other interfaces?
comment:7 Changed 16 years ago by
Keywords: | Pending added; Connector ConnectorHandler removed |
---|
comment:8 Changed 16 years ago by
Resolution: | → expired |
---|---|
Status: | new → closed |
Hmm, that's bad. I somwhat assumed that this will fail sooner or later. Is this a known bug to Grails?
I guess, I have to write a CallUti which traverses standard class loader and then context class loader.
Please check whether other interfaces fail loading too. I guess so. As soon as you can confirm this, I can create a branch with a patch, let you double-check it and then merge back to trunk.