[ http://issues.apache.org/jira/browse/HIVEMIND-137?page=all ]
Knut Wannheden resolved HIVEMIND-137:
-------------------------------------
Fix Version: 1.2
Resolution: Fixed
> Explicit default values for attribute elements within a schema
> --------------------------------------------------------------
>
> Key: HIVEMIND-137
> URL: http://issues.apache.org/jira/browse/HIVEMIND-137
> Project: HiveMind
> Type: Improvement
> Components: framework
> Versions: 1.1
> Reporter: Stefan Liebig
> Fix For: 1.2
>
> If you want to specify default values for <attribute>s within a schema like:
> <attribute name="count" translator="int,min=5,max=10,default=5"/>
> and you use the <conversion> to convert the contribution´s data into a
> mapping class,
> an non-existend "count" within a contribution will not be defaulted, although
> it has been
> specified that it should. To get the desired behaviour you have to use
> <rule>s with
> "skip-if-null=false" which is often "breaking a butterfly on a wheel".
> How about adding a "default" attribute to the <attribute> element, which will
> be used
> when the attribute is not specified?
> This would ease the implementations of translators, because the do not have to
> worry about the specification of default values.
> And much more important the default handling would be configurable and
> readable
> by "contributors". It would not be necessary to hard code the defaults.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
