[ http://issues.apache.org/jira/browse/BEEHIVE-450?page=history ] Krista Baker closed BEEHIVE-450: --------------------------------
Verified that the type is now enumerated and only accepts the following values: html4-loose, html4-loose-quirks, and xhtml1-transitional. An error is given if the value is not one of the above. > beehive-netui-config.xml <doctype> element should be an enum > ------------------------------------------------------------ > > Key: BEEHIVE-450 > URL: http://issues.apache.org/jira/browse/BEEHIVE-450 > Project: Beehive > Type: Bug > Components: NetUI > Reporter: Krista Baker > Assignee: Krista Baker > Fix For: V1 > > beehive-netui-config.xml > The <doctype> element should be an enum. > Current behavior example: > <jsp-tag-config> > <doctype>xhtml</doctype> > </jsp-tag-config> > Actual Result: The rendered jsp uses the html4 document header without the > dtd reference. > Expected Result: The doctype item should be enumerated and throw an exception > on deployment if the value does not match either of the expected values. > (xhtml1-transitional or html4-loose) > Similar (truncated) exception thrown when the <id-javascript> element has an > INVALID value: > Throwable: > org.apache.beehive.netui.util.config.ConfigInitializationException: I > nvalid NetUI configuration file. > line 15: string value 'INVALID' is not a valid enumeration value for > 'type o > f id-javascript element in jsp-tag-config in namespace > http://beehive.apache.org > /netui/2004/server/config' ([EMAIL PROTECTED]) > Stack Trace: > org.apache.beehive.netui.util.config.ConfigInitializationException: Invalid > NetU > I configuration file. > line 15: string value 'INVALID' is not a valid enumeration value for > 'type o > f id-javascript element in jsp-tag-config in namespace > http://beehive.apache.org > /netui/2004/server/config' ([EMAIL PROTECTED]) > at > org.apache.beehive.netui.util.config.ConfigUtil.internalInit(ConfigUt > il.java:149) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
