This works: <cfset myQuery = queryNew("id,code","Integer,Varchar", [ [1,"02-15/10C >=40ft/1"], [2,"02-15/10C >=40ft/2"] ])> <cfset variables.thisCombination='02-15/10C >=40ft/2'> <cfquery name="qry" dbtype="query" > select id from myQuery where code=<cfqueryparam cfsqltype="varchar" value="#variables.thisCombination#"> </cfquery> <cfdump var="#qry#" > so the issue is probably not with the QoQ   ... View more

Are you on CFML Slack (https://cfml.slack.com)? If not, I would recommend that you join. The discussions there suggest that ColdFusion 2025 does not yet support Windows Server 2025. Those who have tried it have reported errors. Of particular note, Adobe's Priyank Shrivastava said, "Windows 2025 is not yet supported OS. We are working on it and will soon add this as supported OS."  ... View more

Here then is the this.javaSettings test I talked about in my last post: 1.   Confirm default POI version My environment is ColdFusion 2025 Update 3. Like ColdFusion 2023 Update 15 it has POI 5.4.1. To confirm this, launch a CFM page containing the code <cfoutput>#createObject("java", "org.apache.poi.Version").getVersion()#</cfoutput> The output is: 5.4.1   2. Create the test component, excel.cfc Its location under wwwroot is /shared/cf/excel.cfc (to emulate the path @skallaje had used). Its code is <cfcomponent> <cffunction name="getPOIversion" returntype="string" output="false"> <cfset var version = createObject( "java", "org.apache.poi.Version").getVersion()> <cfreturn "The POI version is " & version> </cffunction> </cfcomponent>   3. Download POI 3.17 libraries and deploy them for testing Go to the POI library archive and download the file poi-bin-3.17-20170915.zip. Unpack it and you'll get the folder poi-3.17. Create the new directory my_POI_library directly under wwwroot. Copy or move the folder poi-3.17 into my_POI_library.   4. Create the Application.cfc containing the appropriate this.javaSettings configuration The file Application.cfc is to be located in /shared/cf/. Its code is: <!--- This is the Application.cfc file for a ColdFusion application. It defines application-wide settings and event handlers. ---> <cfcomponent> <!--- Application-wide settings, defined in the THIS scope. ---> <cfset this.name = "MyCFApplication"> <cfset this.sessionManagement = true> <cfset this.sessionTimeout = createTimeSpan(0, 0, 30, 0)> <cfset this.applicationTimeout = createTimeSpan(1, 0, 0, 0)> <cfset this.javaSettings = {loadPaths = ["\my_POI_library\poi-3.17\"], loadColdFusionClassPath = true, reloadOnChange= true}> <cffunction name="onApplicationStart" returntype="boolean"> <cfreturn true> </cffunction> <cffunction name="onSessionStart"> </cffunction> <cffunction name="onRequestStart"> <cfargument name="thePage" required="true"> <cfreturn true> </cffunction> <cffunction name="oncfcRequest" returnType="string"> <cfargument type="string" name="cfcName"> <cfargument type="string" name="method"> <cfargument type="struct" name="args"> <cfinvoke returnvariable="local.version" component="#arguments.cfcName#" method="#arguments.method#"> <cfreturn local.version> </cffunction> <cffunction name="onRequestEnd"> <cfargument name="thePage" required="true"> </cffunction> <cffunction name="onApplicationEnd"> <cfargument name="applicationScope" required="true"> </cffunction> <cffunction name="onSessionEnd"> <cfargument name="sessionScope" required="true"> <cfargument name="applicationScope" required="true"> </cffunction> </cfcomponent> 5. Restart ColdFusion.   6.  Make an HTTP request to the getPOIversion method of excel.cfc In my test, I simply make the request by launching http://127.0.0.1:8500/shared/cf/excel.cfc?method=getPOIversion in a browser.   The output: The POI version is 3.17 ... View more

 I called "hello.cfm" from my browser and I noticed that Application.cfc's onCFCRequest() gets fired only if the "test.cfc" is present within the "test" folder because that is where Application.cfc is present. It doesn't get fired if I were to place "test.cfc" within a folder called "shared" outside of "test". The excel.cfc (mentioned in the original post) is present outside of my application, in a folder called "shared/cf". It is in that folder because 2 other ColdFusion applications make of use of shared stuff including excel.cfc from that folder. By @skallaje   @skallaje , I think you've got us barking up the wrong tree. There are no issues with ColdFusion's this.javaSettings. I shall demonstrate it conclusively in a moment. It means that the issue you're facing is the result of a mistake in your paths, settings or code.   The first likely mistake could be in your paths. You say, "The excel.cfc (mentioned in the original post) is present outside of my application." This statement contains a clue. Your application is essentially defined by its Application.cfc file. If excel.cfc is outside the application, it won't be able to "see" the this.javaSettings in Application.cfc.   From your original description, I had taken it for granted that the Application.cfc file containing the this.javaSettings code is in the same directory as the component excel.cfc. That is, in your cf directory. So, you should place it -- or move it -- there. Alternatively, place it one directory up, in /shared.   The second likely mistake could be in your code. You write, "I created a folder called "test". Added a bare minimum, skeletal "Application.cfc" in it.". Does the "test" folder include the directory /shared? That is not clear from your test-request, $.post("/shared/test.cfc?method=addNumbers" Also, could you share the code of the skeletal Application.cfc?    I shall provide in the next post a test involving ColdFusion's this.javaSettings. The test is constructed to be as close to your scenario as possible. It shows that, in spite of what we at first thought, ColdFusion's this.javaSettings actually works as expected. That is:  When the context is an HTTP CFC request, ColdFusion does not default to loading the application's default libraries. It will load your custom libraries instead, if the requested CFC has access to the Application.cfc that defines this.javaSettings. ColdFusion does not treat an HTTP request as a new, independent request context. It treats it as it would any internal createObject() instantiation. The key is that the class loader will honour the this.javaSettings configuration of the Application.cfc file that is in effect.  ... View more