shale-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary VanMatre (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SHALE-353) Add a new attribute allowOveride in order to prevent certain attributes from being altered when subclassing clay components
Date Sat, 31 Mar 2007 00:19:51 GMT

    [ https://issues.apache.org/struts/browse/SHALE-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40723
] 

Gary VanMatre commented on SHALE-353:
-------------------------------------

This is the first crack at trying to represent the Java final modifier in the clay metadata.
 I added a reserved clay XML component attribute called "org.apache.shale.clay.final" to mark
a top-level component definition as final.  Any other top-level component definitions that
attempt to extend another component definition that have been marked using the new final attribute
will ignore the extends and log a warning.  The new attribute doesn't require a value.

Clay manages composition using the element XML nodes that are nested under the component node
or element node.  Elements are an implicit extension of a top-level component.  Elements are
sorta like a Java anonymous inner class.  Elements can extends and override a top-level component
definition.  If an element tries to extend a top-level component definition marked as final,
the overrides will be ignored except the symbol overrides.

Clay html templates treat markup nodes as Clay XML elements.

I'm going to leave this ticket open pending more testing.  I could also use some help adding
to the resource bundle to Norwegian @Hermod :-)


> Add a new attribute allowOveride in order to prevent certain attributes from being altered
when subclassing clay components
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SHALE-353
>                 URL: https://issues.apache.org/struts/browse/SHALE-353
>             Project: Shale
>          Issue Type: New Feature
>          Components: Clay
>    Affects Versions: 1.0.4-SNAPSHOT
>            Reporter: Hermod Opstvedt
>         Assigned To: Gary VanMatre
>             Fix For: TBD
>
>
> In a setting where Clay components are distributed as reusable components, to for instance
have company wide standards for look&feel etc. it would be nice to able to lock down certain
attribute values so that when sombody subclasses the component they are restricted from overriding
attribute that has been flagged.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message