Exception occured before FW/1 was initialized It must implement interface cfide.orm.IEventHandler

137 views
Skip to first unread message

Jim O'Keefe

unread,
Nov 20, 2014, 2:12:08 PM11/20/14
to getx...@googlegroups.com
I get this error on start up using cf 11. "Exception occured before FW/1 was initialized It must implement interface cfide.orm.IEventHandler (Application)"
I looked at the interface and saw it now (as of cf11) includes 2 new functions, preFlush and postFlush. I added them to model.aop.GlobalEventHandler.cfc, and thinking myself very clever, refreshed the page. I still get the error, and I still get it after restarting everything: CF, web server, the OS.  Is there some other step I need to do to flush the old GlobalEventhandler? Has anyone else run into this?

Simon Bingham

unread,
Nov 21, 2014, 3:25:39 AM11/21/14
to getx...@googlegroups.com
Hi Jim,


If you are running Xindi in development mode you could try calling http://localhost/xindi/index.cfm?rebuild=true which will reload ORM. You might want to comment out the following lines in Application.cfc before doing so though - https://github.com/simonbingham/xindi/blob/master/Application.cfc#L32-L35.

Other than that I'm afraid I'm out of ideas.

Simon



 

On 20 November 2014 19:12, Jim O'Keefe <okj...@gmail.com> wrote:
I get this error on start up using cf 11. "Exception occured before FW/1 was initialized It must implement interface cfide.orm.IEventHandler (Application)"
I looked at the interface and saw it now (as of cf11) includes 2 new functions, preFlush and postFlush. I added them to model.aop.GlobalEventHandler.cfc, and thinking myself very clever, refreshed the page. I still get the error, and I still get it after restarting everything: CF, web server, the OS.  Is there some other step I need to do to flush the old GlobalEventhandler? Has anyone else run into this?

--
You received this message because you are subscribed to the Google Groups "Xindi CMS CFML" group.
To unsubscribe from this group and stop receiving emails from it, send an email to getxindi+u...@googlegroups.com.
To post to this group, send email to getx...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/getxindi/7c4f2b3a-92a5-4402-b388-a9c3cce3d853%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

Jim O'Keefe

unread,
Nov 22, 2014, 10:08:47 AM11/22/14
to getx...@googlegroups.com
Simon, thanks for your reply. The bugbase link seemed to be about the changes in iEventHandler from cf10 to cf11, which I had already taken into account. It could be that I screwed that up, but it was pretty simple - just 2 new functions following the existing format. It would be great if the error message said in what way you were not implementing the interface but you can't have everything. The ?rebuild=true I had also tried, along with restarting everything I could think of. What eventually worked was to back up the existing GlobalEventHandler, copy in the new iEventHandler, modify each function with {} and add back the code within the {} from the original GlobalEventHandler where applicable. It's a little unsatisfying in that I don't know what the original problem was, but I'm back in business.

Simon Bingham

unread,
Feb 24, 2015, 3:49:18 PM2/24/15
to getx...@googlegroups.com
Hi Jim,

I wanted to let you know that I finally got round to fixing this in Xindi (along with some other updates).


Thanks,

Simon
Reply all
Reply to author
Forward
0 new messages