Bug 114454

Summary:	Config params with incomplete / missing ParameterInfo objects.
Product:	[Retired] Red Hat Web Application Framework	Reporter:	Daniel Berrangé <berrange>
Component:	other	Assignee:	ccm-bugs-list
Status:	CLOSED RAWHIDE	QA Contact:	Jon Orris <jorris>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	nightly
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-02-05 15:22:27 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:	113496

Description Daniel Berrangé 2004-01-28 12:00:40 UTC

Description of problem:
A number of config params in Core / CMS have missing/incomplete 
parameter info data:



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. ccm-run com.arsdigita.london.util.ConfigPrinter ccm-core ccm-cms
2.

Actual results:
Warnings output:

util.ConfigPrinter - Info for parameter waf.runtime.jdbc_pool_size is
incomplete
util.ConfigPrinter - Info for parameter waf.runtime.jdbc_ping_interval
is incomplete
util.ConfigPrinter - Info for parameter waf.web.site_name is incomplete
util.ConfigPrinter - Info for parameter
waf.web.dispatcher_context_path is incomplete
util.ConfigPrinter - Info for parameter
waf.web.dispatcher_servlet_path is incomplete
util.ConfigPrinter - Info for parameter
waf.web.application_file_resolver is incomplete
util.ConfigPrinter - Info for parameter
waf.templating.stylesheet_paths is incomplete
util.ConfigPrinter - Info for parameter
waf.templating.stylesheet_resolver is incomplete
util.ConfigPrinter - Info for parameter
waf.mail.javamail.configuration is incomplete
util.ConfigPrinter - Parameter waf.lucene.location has no info
util.ConfigPrinter - Parameter waf.lucene.interval has no info
util.ConfigPrinter - Info for parameter waf.bebop.presentation_manager
is incomplete
util.ConfigPrinter - Info for parameter waf.bebop.base_page is incomplete
util.ConfigPrinter - Info for parameter waf.bebop.tidy_config_file is
incomplete
util.ConfigPrinter - Parameter waf.dispatcher.static_url_prefix has no
info
util.ConfigPrinter - Parameter waf.dispatcher.is_caching_active has no
info
util.ConfigPrinter - Parameter waf.dispatcher.default_expiry has no info
util.ConfigPrinter - Parameter waf.workflow.simple.alerts_enabled has
no info
util.ConfigPrinter - Parameter waf.workflow.simple.alerts_sender has
no info
util.ConfigPrinter - Info for parameter
com.arsdigita.cms.item_adapters is incomplete
util.ConfigPrinter - Info for parameter
com.arsdigita.cms.dhtml_editor_config is incomplete
util.ConfigPrinter - Info for parameter
com.arsdigita.cms.dhtml_editor_plugins is incomplete
util.ConfigPrinter - Info for parameter
com.arsdigita.cms.default_notification_time is incomplete

Expected results:
No warning messages

Additional info:

Comment 1 Richard Li 2004-01-28 23:27:17 UTC

The ConfigPrinter uses a strict definition of "complete" that I'm not
sure I agree with. Is it necessary to specify the format of, say,
waf.web.site_name AND an example?

Comment 2 Richard Li 2004-01-28 23:35:10 UTC

I take that back. That was a dumb comment.

Comment 3 Jon Orris 2004-02-05 15:22:27 UTC

Verified fix w/ ConfigPrinter