Extending core parts of the system

When going an create an interceptor dir in my extensions dir, I then created a Security.cfc I found that this is not being extended as I thought.

Is there a list of what can and can’t be extended or overwritten with our own extensions?

Regards,

Andrew Scott

http://www.andyscott.id.au/

You say "extend", but do you actually mean extend in the OO "is a"
sense with the "extends" attribute or do you just mean the ability to
deploy your own security interceptor with modified behavior.
The interceptor portions of your ColdBox config references the
interceptor CFC by its full path, so if you are still pointing to
"coldbox.system.interceptors.security" (or whatever) then sure CB is
going to ignore other CFC's laying around with the name
security.cfc.

As far as actually extending the core security interceptor, I've never
tried it, but I'm sure it is probably possible if your security.cfc
extends "coldbox.system.interceptors.security" and you point your
config file to the appropriate path to your version and override the
methods you want.

Or alternatively, you could just make a copy of the core security
interceptor and modify it as much as you want.

Thanks!

~Brad

Thanks Brad I worked that out long after I posted this, it was kind of silly
of me to not realise that to begin with.

Regards,
Andrew Scott
http://www.andyscott.id.au/

From: coldbox@googlegroups.com [mailto:coldbox@googlegroups.com] On
Behalf Of brad@bradwood.com
Sent: Saturday, 30 October 2010 5:19 AM
To: ColdBox Platform
Subject: [coldbox:0] Re: Extending core parts of the system

You say "extend", but do you actually mean extend in the OO "is a"
sense with the "extends" attribute or do you just mean the ability to

deploy

your own security interceptor with modified behavior.
The interceptor portions of your ColdBox config references the interceptor
CFC by its full path, so if you are still pointing to
"coldbox.system.interceptors.security" (or whatever) then sure CB is going
to ignore other CFC's laying around with the name security.cfc.

As far as actually extending the core security interceptor, I've never

tried it,

but I'm sure it is probably possible if your security.cfc extends
"coldbox.system.interceptors.security" and you point your config file to

the

appropriate path to your version and override the methods you want.

Or alternatively, you could just make a copy of the core security

interceptor

I am bumping this because it was not fully answered.

We all know that we can put things into the extensions folder in our
application, or where the convention is set too. But there is no
documentation or knowledged on what can and can't be extended (Yes in the OO
sense), for example to try and fix this VirtualDirectory Issue I wish to
modify the system.web.controller.cfc but the changes I have made are not
working.

Line debugging this indicates that not much of the core features can be
extended in this manner.

Regards,
Andrew Scott
http://www.andyscott.id.au/

From: coldbox@googlegroups.com [mailto:coldbox@googlegroups.com] On
Behalf Of brad@bradwood.com
Sent: Saturday, 30 October 2010 5:19 AM
To: ColdBox Platform
Subject: [coldbox:0] Re: Extending core parts of the system

You say "extend", but do you actually mean extend in the OO "is a"
sense with the "extends" attribute or do you just mean the ability to

deploy

your own security interceptor with modified behavior.
The interceptor portions of your ColdBox config references the interceptor
CFC by its full path, so if you are still pointing to
"coldbox.system.interceptors.security" (or whatever) then sure CB is going
to ignore other CFC's laying around with the name security.cfc.

As far as actually extending the core security interceptor, I've never

tried it,

but I'm sure it is probably possible if your security.cfc extends
"coldbox.system.interceptors.security" and you point your config file to

the

appropriate path to your version and override the methods you want.

Or alternatively, you could just make a copy of the core security

interceptor