tracker issue : CF-4087803

select a category, or use search below
(searches all categories and all time range)
Title:

Allow third argument to createobject to be one or more locations of jars

| View in Tracker

Status/Resolution/Reason: To Fix//Investigate

Reporter/Name(from Bugbase): Luis Majano / Luis Majano (Luis Majano)

Created: 11/16/2015

Components: Java Integration

Versions: 11.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Trivial / Unknown

Locale/System: English / iOS All

Vote Count: 18

Lucee supports this already and we need it for CommandBox as well.  The third argument for createobject can be one or more paths where jar files can be classloaded.

createobject( "java" , class, paths )

classpath used to load the defined class, this can be a list of multiple paths (directories containing class files or jar files)

This can be easily done by creating an in memory network class loader and attach it to the context.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4087803

External Customer Info:
External Company:  
External Customer Name: Luis Majano
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

I didn't realize ACF did not already support this! Seems like a really good fundamental addition.
Vote by External U.
5325 | November 16, 2015 10:21:12 AM GMT
Please add this, the current ways are all to broad.
Vote by External U.
5326 | November 16, 2015 10:23:12 AM GMT
Sounds good. +1 Vote must be between 25 and 4000 characters
Vote by External U.
5327 | November 16, 2015 10:24:41 AM GMT
A lot of people use this feature in Lucee. It would be a great addition to Adobe CF. It's really important for people who want to package a library that contains jars that "just works" and doesn't require server config or application-level changes just to load a jar.
Vote by External U.
5328 | November 16, 2015 10:29:01 AM GMT
+1...................................
Vote by External U.
5329 | November 16, 2015 11:07:52 AM GMT
I could make use of this, I have run into cases where I had to use javaloader because I can't rely on the application specific settings for the classpath. It allows developers to write more modular code. Bonus feature would be to have a createClassLoader([jar,files], loadColdFusionClassPath) function that returned a and allow createObject to take either a classLoader instance or an array, that way the class loader could be reused if you have multiple createObject invocations that need to share the same classloader.
Vote by External U.
5330 | November 16, 2015 11:11:08 AM GMT
+1 This would be a great addition.
Vote by External U.
5331 | November 16, 2015 11:23:25 AM GMT
This definitely needs to be added in!
Vote by External U.
5332 | November 16, 2015 11:59:10 AM GMT
+1 - nice feature to add.....................
Vote by External U.
5333 | November 16, 2015 02:28:53 PM GMT
+1 to this and Pete's suggestion
Vote by External U.
5334 | November 16, 2015 03:43:41 PM GMT
+1111111111111111111111111
Vote by External U.
5335 | November 17, 2015 12:26:44 AM GMT
+1 - this would be extremely useful.
Vote by External U.
5336 | November 18, 2015 10:33:32 PM GMT
What is there to review?
Comment by External U.
5322 | February 27, 2016 12:26:07 AM GMT
Ok Adobe, why keep this in review. Either you implement it or not do it, but it has been under review since 2015.
Comment by Luis M.
5323 | February 21, 2017 12:06:38 AM GMT
Guys a ACF. Stop putting things under review that just site there.
Vote by George M.
5337 | October 12, 2017 01:09:45 PM GMT
George, this is under evaluation and in the toFix status in case you haven't noticed.
Comment by Vamseekrishna N.
5324 | October 12, 2017 02:51:00 PM GMT