Bug 536670 (RHQ-997)

Summary: add new allowsEmptyValue boolean option to property definitions
Product: [Other] RHQ Project Reporter: Ian Springer <ian.springer>
Component: ConfigurationAssignee: Ian Springer <ian.springer>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 1.1CC: ccrouch, cwelton
Target Milestone: ---Keywords: FutureFeature, Improvement
Target Release: ---   
Hardware: All   
OS: All   
URL: http://jira.rhq-project.org/browse/RHQ-997
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-17 12:05:52 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 585306    

Description Ian Springer 2008-10-19 14:01:00 EDT
In 95% of cases, a plugin writer is going to want to consider empty string values for properties to be invalid. But there will be some cases where they want to allow empty strings for certain properties. To support these cases, add a allowsEmptyValue boolean option to PropertyDefinitionSimple that defaults to false.
Comment 1 Red Hat Bugzilla 2009-11-10 16:21:16 EST
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-997
Comment 2 wes hayutin 2010-02-16 12:10:16 EST
mass add of key word FutureFeature to help track