You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org> on 2005/09/22 20:54:29 UTC
[jira] Created: (TAPESTRY-661) Add Meta annotation, for defining meta data
Add Meta annotation, for defining meta data
-------------------------------------------
Key: TAPESTRY-661
URL: http://issues.apache.org/jira/browse/TAPESTRY-661
Project: Tapestry
Type: Bug
Components: Annotations
Versions: 4.0
Reporter: Howard M. Lewis Ship
Assigned to: Howard M. Lewis Ship
Fix For: 4.0
Currently, we have @InjectMeta, which is useful for reading meta data, and (often) converting it to an appropriate type.
However, the meta data itself must still be defined inside an XML file (with the page or component spec overriding the containing application or library spec).
This means that meta data can't be inherited (except by placing a default value in the library spec) and XML is still needed for this one thing, even though everything else can be defined using pure code and annotations.
--
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Closed: (TAPESTRY-661) Add @Meta annotation, for defining meta data
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-661?page=all ]
Howard M. Lewis Ship closed TAPESTRY-661:
-----------------------------------------
Resolution: Fixed
> Add @Meta annotation, for defining meta data
> --------------------------------------------
>
> Key: TAPESTRY-661
> URL: http://issues.apache.org/jira/browse/TAPESTRY-661
> Project: Tapestry
> Type: Bug
> Components: Annotations
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 4.0
>
> Currently, we have @InjectMeta, which is useful for reading meta data, and (often) converting it to an appropriate type.
> However, the meta data itself must still be defined inside an XML file (with the page or component spec overriding the containing application or library spec).
> This means that meta data can't be inherited (except by placing a default value in the library spec) and XML is still needed for this one thing, even though everything else can be defined using pure code and annotations.
--
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Updated: (TAPESTRY-661) Add @Meta annotation, for defining meta data
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-661?page=all ]
Howard M. Lewis Ship updated TAPESTRY-661:
------------------------------------------
Summary: Add @Meta annotation, for defining meta data (was: Add Meta annotation, for defining meta data)
> Add @Meta annotation, for defining meta data
> --------------------------------------------
>
> Key: TAPESTRY-661
> URL: http://issues.apache.org/jira/browse/TAPESTRY-661
> Project: Tapestry
> Type: Bug
> Components: Annotations
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 4.0
>
> Currently, we have @InjectMeta, which is useful for reading meta data, and (often) converting it to an appropriate type.
> However, the meta data itself must still be defined inside an XML file (with the page or component spec overriding the containing application or library spec).
> This means that meta data can't be inherited (except by placing a default value in the library spec) and XML is still needed for this one thing, even though everything else can be defined using pure code and annotations.
--
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org