>> [snip]
>>
>> Another possible solution is that the component always overwrites the
>> values in the html template.
>>
>> Examples:
>>
>> Use the value of the component
>>
>> <input type="submit" jsfid="submitForm" value="Button 1" />
>>
>> <component jsfid="submitForm" extends="commandButton">
>> <attributes>
>> <set name="value" value="#{bundle.SubmitName}" />
>> <set name="action" value="whatever" />
>> </attributes>
>> </component>
>>
>>
>> Use the value of the template
>>
>> <input type="submit" jsfid="submitForm" value="Button 1" />
>>
>> <component jsfid="submitForm" extends="commandButton">
>> <attributes>
>> <set name="action" value="whatever" />
>> </attributes>
>> </component>
>>
>>
>> With this solution no new attribute is needed and in most (all?) cases it
>> should work as expected.
>>
>
> The key point here: what is the inheritence hierarchy. In another words,
> what is on the top of the hierarchy: html snippet or the widget referenced
> by jsfid. if we keep in mind the paradign of OOP, class inherits and
> overrides the super-class, but not vice-versa.
But it's the decision of the subclass whether it uses the own value or the
value of the superclass. There is no change in the inheritance hierarchy,
only the meaning of the HTML snippet changes.
See the html values as defaults that are used if the superclass doesn't
specify a value.
> So,
>
> In my case, it looks like:
>
> | snippet
> |-- submitForm
> |--commandButton
>
> In your case:
>
> | submitForm
> |--snippet
> |--commandButton
>
> The advantage of your proposal is avoiding to change the current DTD with
> introducing allowOverriding attribute.
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
