Skip to:

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

Set cfclasses in a package

Description

Copied from: https://issues.jboss.org/browse/RAILO-2868

Currently the Java classes in cfclasses are in the default package.

It'd be great if they could be in a specific package, like "railo.cfclasses" for example, for the sake of low level diagnostics etc.

Comments from Railo ticket

Michael Offner added a comment - 22/Jan/14 11:04 PM
Changing the package pattern will affect a lot of related functionality, like the function componentlistpackage, fusion debug interface .... To be honest I see no benefit that is worth the trouble this change will bring. We already use packages for our classes, what is not happening with acf for example.

Igal . added a comment - 22/Jan/14 11:55 PM
external tools like Fusion Debug will benefit the most from such a change.

Michael Offner added a comment - 23/Jan/14 12:03 AM
You get it wrong. Railo has a interface for fusion debug, changing the pattern, means rewrite that interface at well. For nearly all users the cfclasses folder is of no interest. Is still can see no benefit in having addional packages. It was important not to have a flat structure like acf, because this produces huge and slow indexes. So what is the benefit in that?

Igal . added a comment - 23/Jan/14 12:07 AM
I understood what you meant about the interface. my point is that tools that analyze the JVM will benefit the most from such a change as they will be able to easily separate the cfclasses objects from other objects in the JVM because they will all share the same unique prefix of "ralio.cfclasses" or something like that.
no sleep tonight?

Michael Offner added a comment - 23/Jan/14 2:11 AM
recognize Railo classes is very easy, that need no such package. My oldest daughter has chickenpox

Activity

Show:

Andrew Dixon 3 June 2015 at 08:33

- I've changed the report to you now as you reported it on the Railo board.

Andrew Dixon 3 June 2015 at 08:32

- I thought I had raised it as the same as the ticket from the Railo board. I have changed it down to "minor" now.

Michael Offner 3 June 2015 at 07:56

is there a specific reason this ticket is "critical" to you? For us this is only a "nice to have" with no real-world benefit.

Michael Offner 3 June 2015 at 07:44

the description of this ticket is missleading "Currently the Java classes in cfclasses are in the default package.". package produced by lucee are not in the default package, lets, say you have a cfm template at

<webroot>/susi/sorglos.cfm

Lucee is producing a class with name "sorglos" in the package "susi", so not in the default package.
what we talking about is that this class is not in the package "susi", instead it should be in the package "lucee.classes.susi"

Andrew Dixon 2 June 2015 at 18:06

Raised from forum discussion here: https://groups.google.com/forum/#!msg/lucee/PfNWq_EkqXM/6ho8vEC8x_kJ

Details

Assignee

Reporter

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

Priority

Created 2 June 2015 at 18:05
Updated 16 September 2015 at 23:35

Flag notifications