Bug 536670 (RHQ-997)

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

Description Ian Springer 2008-10-19 18:01:00 UTC

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 21:21:16 UTC

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-997

Comment 2 wes hayutin 2010-02-16 17:10:16 UTC

mass add of key word FutureFeature to help track