In our Catalog.cfc event handler we run a private event called “setSpotPriceAndActionButtons” in the same handler as follows:
runEvent( event='catalog.setSpotPriceAndActionButtons', private=true );
This has always worked fine in CB 4.2, but just noticed that in CB 4.3 it throws the following error:
Type: expression
Messages: Component [handlers.Catalog] has no accessible Member with name [setSpotPriceAndActionButtons] enable [trigger data member] in admininistrator to also invoke getters and setters
Relevant Tag Context here:
`
Template:
C:\dev\apps\coldbox-4.3.0\system\web\services\HandlerService.cfc
LINE: 176: // Store action metadata
177: arguments.ehBean.setActionMetadata(
178: getMetadata( oEventHandler[ arguments.ehBean.getMethod() ] )
179: );
180:
Template: C:\dev\apps\coldbox-4.3.0\system\web\Controller.cfc
LINE: 500: ehBean.setIsPrivate( arguments.private );
501: // Now get the correct handler to execute
502: oHandler = services.handlerService.getHandler( ehBean, oRequestContext );
503: // Validate again this is not a view dispatch as the handler might exist but not the action
504: if( ehBean.getViewDispatch() ){ return; }
Template: C:\dev\apps\coldbox-4.3.0\system\web\Controller.cfc
LINE: 423: // relay if no event caching activated or no caching needed
424: if( !getSetting( “eventCaching” ) OR !arguments.cache ){
425: return _runEvent( argumentCollection=arguments );
426: }
427:
Template: C:\dev\apps\coldbox-4.3.0\system\FrameworkSupertype.cfc
LINE: 376: cacheProvider=“template”
377: ){
378: return controller.runEvent( argumentCollection=arguments );
379: }
380:
Template: C:\dev\apps\bold\app\handlers\Catalog.cfc
LINE: 65:
66: // set the Spot’s Price and Action Buttons
67: runEvent( event=‘catalog.setSpotPriceAndActionButtons’, private=true );
68: }
69: }
`
Changing the event to public lets it run fine. We’ve changed no code, only the version of ColdBox.
Did something change in the way we run private events or is this a bug?
Thanks,
Andrew