Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

createDynamicProxy() won't find interfaces from jars in the lib folder

Description

See the attached file. Unzip it and place the jar in your lib folder. Start up Lucee 5 and drop the .cfm and .cfc files in your webroot and run the index.cfm. The createObject call works fine showing that the jar is loaded and Lucee can find the classes inside of it. However, the createDynamicProxy() fails with the following error now matter where I stick the jar file.

Message class jline.console.completer.Completer is invalid or doesn't exist Cause java.lang.ClassNotFoundException

I tested this on Lucee Express version 5.0.0.235-RC

Environment

None

Attachments

1
  • 26 Apr 2016, 04:39 pm

Activity

Show:

Michael Offner 18 May 2016 at 06:30

Michael Offner 12 May 2016 at 17:03

a solution could be to make the proxy created independent from the core, so it is not necessary to load as part of the core classloader

Michael Offner 12 May 2016 at 13:49

createDynamicProxy creates a class that must "see" the core and the classes it wrap at the same time.
We will find a solution, but atm i have no idea how to do this.

Brad Wood 12 May 2016 at 13:43

How is it that createObject() works then and finds the classes from the jar but createDynamicProxy doesn't? Does this mean that anyone using dynamic Java proxies in their apps will be unable to use Lucee 5?

Michael Offner 12 May 2016 at 12:35

this is completely related to OSGi classes that can see the core cannot see the classes from outside (systemclassloader), atm i have no clue how to solve this

Fixed

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 26 April 2016 at 16:41
Updated 6 hours ago
Resolved 18 May 2016 at 06:31

Flag notifications