ColdBox Platform Google Group

Re: [coldbox:3538] Design / Architecture questions

2009-11-24T22:03:03Z

Thank you I will check it out.

I was looking through the docs and in the
[link] tutorial
in getUserByCredentials method a user object is created:

oUser = createObject ("component", "User").init ();

Where is the cfc for this?

Thanks

Re: [coldbox:3544] Re: Problem with Custom Interception Points and Beta 3

2009-11-24T21:17:17Z

Ah, gotcha. I was trying to figure out how it knew where the
interceptor was, like if it was just scanning the interceptors folder
and autoregistering, etc. Seemed deceptively simple and, indeed, it
was.

Thanks for the clarification Luis.

Re: [coldbox:3543] Re: Problem with Custom Interception Points and Beta 3

2009-11-24T20:03:04Z

Judah,

You still register the interceptor in your xml, so coldbox can create it for
you and configure it for you. The annotations are only to declare custom
interception points "interceptionPoint". So register it like normal, but
now you can omit the custominterceptionpoints element and use the

Re: [coldbox:3508] Re: Problem with Custom Interception Points and Beta 3

2009-11-24T19:24:57Z

I'm about to write my first interceptor and am using 3.0.0 Beta 3.
Could you provide an example of the new setup? Do you have to register
anything in the XML? And how do you pass properties to the interceptor
if you aren't using the XML but rather annotations?

Thanks,
Judah

Re: [coldbox:3535] FYI: Possible future problem with CB and built in Transfer support

2009-11-24T03:09:36Z

Awesome thanks.

--
Luis F. Majano
President
Ortus Solutions, Corp

ColdBox Platform: [link]
Linked In: [link]
Blog: [link]
IECFUG Manager: [link]

Re: [coldbox:3540] FYI: Possible future problem with CB and built in Transfer support

2009-11-24T00:32:37Z

A. Fantastic! It's working great. The ehcache manager threads are
"shutdown" once my interceptor checks if the TransferFactory is in the
coldbox cache, gets it if yes, and runs shutdown() on it on the two
new interception points.

B. Small bug though. In the advanced application template (no
inheritance), the "onApplicationEnd" function makes a reference to the

Re: [coldbox:3535] FYI: Possible future problem with CB and built in Transfer support

2009-11-23T20:46:03Z

Check the nightly build.

Two new interception points:

applicationEnd - shot by the Application.cfc application end
preReinit - shot by ColdBox before reinitializing.

Luis F. Majano
President
Ortus Solutions, Corp

ColdBox Platform: [link]
Linked In: [link]

Re: [coldbox:3535] FYI: Possible future problem with CB and built in Transfer support

2009-11-23T16:39:12Z

I will check on this. I beleive the solution is to fire a new
interceptor when the framework reinits. I will add this and let you
know where

--
Luis F. Majano
President
Ortus Solutions, Corp

ColdBox Platform: [link]
Linked In: [link]
Blog: [link]

Re: [coldbox:3536] Design / Architecture questions

2009-11-23T16:36:57Z

Please take a look at the coldbox dashboard application it uses frames.

--
Luis F. Majano
President
Ortus Solutions, Corp

ColdBox Platform: [link]
Linked In: [link]
Blog: [link]
IECFUG Manager: [link]

Re: [coldbox:3535] FYI: Possible future problem with CB and built in Transfer support

2009-11-23T14:53:02Z

The implementation Mark chose was "TransferFactory.shutdown()".

Is this currently possible: On reinit, hook into the existing cache,
check if Transfer is in there, call shutdown() on it, and proceed
with reiniting?

I'm still experimenting with different interception points but it
appears that, on reinit, a new cache is created and so the transfer

Design / Architecture questions

2009-11-22T15:17:26Z

Hi,

I'm a coldbox newbie and trying to refactor an existng (rather large)
app using coldbox.
I have 2 (for starters) questions :
1.is it OK to have cfincludes in a view?
2. Are there any examples of how to set up (call) the view when
dealing with frames? Do I set up the the layout to be the frame and

FYI: Possible future problem with CB and built in Transfer support

2009-11-22T20:44:30Z

Hi Luis,

A. Mark Mandel is working on a pluggable cache for Transfer with the
default being EHCache. I've been playing around with it and stumbled
onto a problem where every time I "reinit" my coldbox app, a new
instance of EHCache is created. If I "reinit" often enough, I run out
of memory.

Re: [coldbox:3533] ColdBox 3.0.0 requestcontext structure bug? DOH! - NEVER MIND

2009-11-22T19:38:32Z

You are eight however I is something we removed as we where not being
standard on this. We will add it to the docs as compatibility
upgrades. By the way if you like that approach you can create your own
decorator and update.

--
Luis F. Majano
President
Ortus Solutions, Corp

ColdBox Platform: [link]

ColdBox 3.0.0 requestcontext structure bug? DOH! - NEVER MIND

2009-11-21T12:15:02Z

Please ignore my last email! I got it figured out.

Although upgrading to 3.0 did break my custom tag, I did figure out
that I can simply use the following notation to get what I need:

request.cb_requestcontext.getV alue('page').name

THANKS!

ColdBox 3.0.0 requestcontext structure bug?

2009-11-21T11:59:44Z

I think I may have found a bug or at least something that needs
documentation for Coldbox 3.0.

I have a request context variable called "page". It is a structure
that holds html head info.

In version 2.6, I could use the following code (this is from a custom
tag):

request.cb_requestcontext.getV alue('page.title')