History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: FC-1386
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: Michael Sharman
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FarCry Core Framework

Setting bObjectBroker doesn't remove object from cache

Created: 30/Jun/08 02:58 PM   Updated: 12/Oct/08 06:00 PM
Component/s: FourQ & ORM
Affects Version/s: FarCry 5.0 (Fortress)
Fix Version/s: FarCry 5.1

Time Tracking:
Not Specified

Environment:
Mac OSX
ColdFusion 8


 Description  « Hide
The following object should not be cachable as "bObjectBroker" is set to false:

<cfcomponent displayname="Products" name="Products" extends="farcry.core.packages.types.types" output="false" buseintree="true" bObjectBroker="false" objectbrokermaxobjects="50" lObjectBrokerWebskins="display*">

However it does appear to be caching, meaning you need to remove all references to objectbroker as follows:

<cfcomponent displayname="Products" name="Products" extends="farcry.core.packages.types.types" output="false" buseintree="true">

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Geoff Bowers - 11/Aug/08 02:06 PM
Can we confirm this is happening and get a confirmation on how the component metadata is supposed to affect the broker.

I would have thought that bobjectbroker="false" should basically remove the component completely from the broker.

Matthew Bryant - 12/Oct/08 06:00 PM
updateapp will now flush the entire objectbroker and reset all objects according to bObjectBroker status.