tracker issue : CF-3688456

select a category, or use search below
(searches all categories and all time range)

Add onError method for CFC's

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Chris Hopkins / Chris Hopkins (Chris Hopkins)

Created: 12/31/2013

Components: Language, CF Component

Versions: 10.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: Final /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Platforms All

Vote Count: 3

Duplicate ID:	CF-3687747

Pretty self explanatory really, have a onError method for CFC's that acts in the same way as the global onError within the application.cfc but for just a singular CFC.

This feature request is quite useful on its own but could also serve as an extension of Steven Neiland's 'Baked in AOP' request:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3688456

Deployment Phase:	Release Candidate

External Customer Info:
External Company:  
External Customer Name: chris_hopkins_
External Customer Email:  
External Test Config: My Hardware and Environment details: N/A



+1. Agree that it could be considered in conjunction with a broader AOP solution, but this has merit as stand-alone work too. -- Adam
Vote by External U.
13779 | December 31, 2013 08:52:30 AM GMT
+1 What adam said, I see this as having merit in its own right. Did you put in feature request on (the other cfml engines) as well?
Vote by External U.
13780 | January 02, 2014 12:03:24 PM GMT
+1, It would be nice to have a cfc level onError that cascades to the application.cfc onError.
Vote by External U.
13781 | January 02, 2014 12:59:20 PM GMT
Passing bug to product management team for review (Comment added from ex-user id:vnigam)
Comment by Adobe D.
13775 | January 13, 2014 12:28:51 AM GMT
We will consider AOP as a larger feature for the next release
Comment by Rupesh K.
13776 | January 17, 2014 02:28:22 AM GMT
I'm not sure this should have been closed as a duplicate, as bug doesn't specifically address onError() except in the comments. Also, is onError() strictly an AOP concept, or would it have wider application?
Comment by External U.
13777 | December 04, 2014 09:57:40 AM GMT
Agreed. This is not a duplicate of the other ticket.
Comment by External U.
13778 | December 04, 2014 10:19:16 AM GMT