Bugzilla – Full Text Bug Listing
| Summary: | Add ability to disable SDEF cache during development | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Greg Amerson <gregory.amerson> | ||||
| Component: | Sapphire | Assignee: | Konstantin Komissarchik <konstantin> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | kamesh.sampath, konstantin | ||||
| Version: | unspecified | Keywords: | plan | ||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Greg Amerson
Suggested method would be to introduce support for a framework wide debug flag: -Dsapphire.debug=true If its true, then the SDEF cache could check this flag and if debug is on, it would not cache the definition, thus allowing for rapid development. Note that I would expect caching to be disabled only for sdef models (as opposed to disabling the overall caching system that is used for any kind of model). Tagging as a possible work item for Kamesh. I've getting back into SDEF development again and before I started I went ahead and made a patch for this. I'll attach my current patch. Created attachment 205256 [details]
patch attempt 1
Added a simple -D debug flag to look for to avoid cache check for SDEFs.
I generalized the system property by calling it "sapphire.dev.mode" and creating a public method to check its state. We will might want to attach other behaviors to dev mode besides disabling sdef cache. Please verify. Verified with latest CVS. Closing. Thanks. |