onApplicationStart
# luceed
David Rogers
10/10/2024, 9:02 PMonApplicationStart
David Rogers
10/10/2024, 9:03 PM Copy code
component {
public function onApplicationStart() {
// runs
createObject("java", "java.lang.System").out.println("!!!!!!!!!! on app start");
}
}David Rogers
10/10/2024, 9:03 PM Copy code
component {
application.foo = 42;
public function onApplicationStart() {
// does not run
createObject("java", "java.lang.System").out.println("!!!!!!!!!! on app start");
}
}David Rogers
10/10/2024, 9:04 PMDoes writing to the application scope from the psuedoconstructor mean "don't run onApplicationStart"?
s
sknowlton
10/11/2024, 1:08 AMiiiiinteresting
sknowlton
10/11/2024, 1:08 AMI wonder if this happens in ACF as well?
r
Rodney
10/11/2024, 12:18 PMThe pseudo constructor runs on every request. The onApplicationStart method runs on the first request after server start up or after the application timeout. Application.foo should not be set in the pseudo constructor and will probably throw an error. It might be silently throwing an error which is then causing onApplicationStart not to fire.
d
David Rogers
10/11/2024, 12:46 PMHm. In this case, the associated index.cfm runs, and
application.foor
Rodney
10/11/2024, 12:48 PMI can see it working if that value was added after the application started. I'd call it a bug if it worked on server start, but I don't know when the pseudo scope gets processed within the lifecycle events.
Rodney
10/11/2024, 12:50 PMEither way it's bad practice to set an application scoped variable in the pseudo scope because that will run on every request.
d
David Rogers
10/11/2024, 12:59 PMYes some kind of bug, or behavior difference from acf at least.
2 Views