G'day:
And then calling each request thus:
"G'day World @ {ts '2014-01-03 14:17:43'}"
MethodFailedException was thrown
So those requests are running as expected. Cool.
In the resultant log file, I get this:
"Severity","ThreadID","Date","Time","Application","Message"
"INFO","web-0","01/03/2014","14:18:55","","onApplicationStart() called"
"INFO","web-0","01/03/2014","14:18:55","","onSessionStart() called"
"INFO","web-0","01/03/2014","14:18:55","","onRequestStart() called"
"INFO","web-0","01/03/2014","14:18:55","","onRequestEnd() called"
"INFO","web-0","01/03/2014","14:19:00","","onRequestStart() called"
"INFO","web-0","01/03/2014","14:19:00","","onRequestEnd() called"
So onApplicationStart(), onSessionStart(), onRequestStart() and onRequestEnd() are called for each request. But none of onRequest(), onCfcRequest() or onError() (where applicable) are called.
Adobe's rationale as to why neither onRequest() nor onCfcRequest() are called is because a REST request is not calling the CFC directly, Which seems a bit specious to me, to be honest. But I suspect it's the rationale in Railo too?
Given that in reality the CFC is being called, even though not explicitly in the URL, does it really make sense to say "it's not being called, hence it's not a CFC request, hence onCfcRequest() doesn't get called"?
I don't see how my code should "care" via what mechanism the application server takes to arrive my code... the thing is the entry point to the request - as far as the codebase is concerned - is the CFC, surely?
I dunno. Maybe I'm missing something. Maybe there's a precedent set in which this is predictable behaviour, and it's just a gap in my knowledge here? This is entirely possible, as I only dabble with REST services.
Cheers!
--
Adam