Meta annotation structure
-------------------------
Key: TAPESTRY-1213
URL: http://issues.apache.org/jira/browse/TAPESTRY-1213
Project: Tapestry
Issue Type: Improvement
Affects Versions: 4.1.1
Reporter: Ron Piterman
Priority: Minor
I had posted to the dev list the same issue with in regard of the binding
annotations, in regard of meta this is not so complicated, and has real
advantages:
I would like to propse:
depracate @Meta
create a
annotation interface @Metas (
@MetaValue[] value()
)
where @MetaValue is : String name(); String value()
the use case:
Meta names can be used as standalone constants.
Meta values can be used as standalone constants.
currently, one has to define two constants: one to inject the meta, one to set
its value, which is "unclean":
currently:
META_ROLE="role";
META_ROLE_USER="role=user"; or META_ROLE + "=user";
and
@Meta(META_ROLE_USER)
@InjectMeta(META_ROLE)
instead:
META_ROLE_USER="user";
@Metas( @MetaValue( name=META_ROLE, value=META_ROLE_USER ) )
and
@InjectMeta(... the same as above.
Ofcouse, the benefit is not straight forward, until one works with constants
from sources outside of the tapestry project.
The meta values may be defined outside the tapestry application( in the
backend) - and one can not use it in a straight forward manner. instead one has
to define an extra constant with the equals sign. Though this is not very
"tragic" it is not straightforward, and I consider it an ockwardty (english
spelling :( ) of the framework.
--
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]
