Skip to:

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

cfajaxproxy throw error while try to access the component

Description

Trying to create a proxy for a particular cfc, using below code

<cfajaxproxy cfc="com.tester" jsclassname="events" />

Lucee throw error on 4.5.1.0.000.PNG, & Lucee5.2.5.5.PNG versions.

Environment

Lucee4.5 versions & 5 versions

Attachments

2
  • 12 Sept 2017, 06:54 am
  • 12 Sept 2017, 06:54 am

Activity

Show:

Samuel W. Knowlton 5 October 2018 at 19:36

Sorry to intrude on this ticket, but is cfajaxproxy now an extension? I see the github for it but I don't see it listed in the extension provider (and manually inputting the ID in the LUCEE_EXTENSIONS env didn't do anything).

When I use this tag on 5.3, I get

lucee.runtime.exp.TagNotSupported: tag AjaxProxy is not supported

The underlying Java class looks like it's meant to do this, but it hasn't changed since 2015 and there are current tickets about this tag - and the docs don't indicate that it's not supported. What am I missing?

Michael Offner 17 April 2018 at 18:13

Michael Offner 17 April 2018 at 18:09
Edited

just saw pull request was into master instead of 5.2, i will manually upadte 5.2 branch
https://github.com/lucee/Lucee/commit/3de00564212bf745708fbfffc527ef57700b3699

Pothys - MitrahSoft 3 April 2018 at 15:15

Yeah, throws error for absolute path, It's only work for relative path. Thanks for the info
Above Pull request fix the issue.
Please reopen this issue & added above pull if it's fine, I've added this into the extension also.
Pull Request: thttps://github.com/lucee/extension-ajax/pull/2

Craig Harshbarger 26 March 2018 at 19:21

I'm having this issue as well on 5.2.6.60

Fixed

Details

Assignee

Reporter

Priority

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

Sprint

Created 12 September 2017 at 06:55
Updated 5 October 2018 at 19:36
Resolved 22 November 2017 at 07:50

Flag notifications