You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/01/23 02:07:59 UTC

[jira] Created: (TAP5-461) It is very common to map the value attribute of a type annotation as a meta-data property; it would be nice if there was an easy way to do this, via contributing the annotation type and meta-data key

It is very common to map the value attribute of a type annotation as a meta-data property; it would be nice if there was an easy way to do this, via contributing the annotation type and meta-data key
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: TAP5-461
                 URL: https://issues.apache.org/jira/browse/TAP5-461
             Project: Tapestry 5
          Issue Type: New Feature
          Components: tapestry-core
    Affects Versions: 5.1.0.0
            Reporter: Howard M. Lewis Ship


In other words, if we have Moe, Larry and Curly and they all look like this:

public class MoeWorker implements ComponentClassTransformWorker
{
    public void transform(ClassTransformation transformation, MutableComponentModel model)
    {
        Moe annotation = transformation.getAnnotation(Moe.class);

        if (annotation != null)
            model.setMeta("meta-data.moe", annotation.value());
    }
}


It would be nice if we could just make a contribution:

configuration.add("meta-data.moe", Moe.class);

For each of Moe, Larry and Curly instead. This would apply only when the annotation has a single attribute whose type is String.


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


[jira] Assigned: (TAP5-461) It is very common to map the value attribute of a type annotation as a meta-data property; it would be nice if there was an easy way to do this, via contributing the annotation type and meta-data key

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAP5-461:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> It is very common to map the value attribute of a type annotation as a meta-data property; it would be nice if there was an easy way to do this, via contributing the annotation type and meta-data key
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-461
>                 URL: https://issues.apache.org/jira/browse/TAP5-461
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> In other words, if we have Moe, Larry and Curly and they all look like this:
> public class MoeWorker implements ComponentClassTransformWorker
> {
>     public void transform(ClassTransformation transformation, MutableComponentModel model)
>     {
>         Moe annotation = transformation.getAnnotation(Moe.class);
>         if (annotation != null)
>             model.setMeta("meta-data.moe", annotation.value());
>     }
> }
> It would be nice if we could just make a contribution:
> configuration.add("meta-data.moe", Moe.class);
> For each of Moe, Larry and Curly instead. This would apply only when the annotation has a single attribute whose type is String.

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


[jira] Closed: (TAP5-461) Create a service that fits into the ComponentClassTransformWorker chain and can be configured to extract component meta-data from class annotations

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-461.
-------------------------------------

    Resolution: Fixed

Final API doesn't quite match the description (which was just a first pass) but should be pretty clear from the API and from  the examples in TapestryModule.

> Create a service that fits into the ComponentClassTransformWorker chain and can be configured to extract component meta-data from class annotations
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-461
>                 URL: https://issues.apache.org/jira/browse/TAP5-461
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> In other words, if we have Moe, Larry and Curly and they all look like this:
> public class MoeWorker implements ComponentClassTransformWorker
> {
>     public void transform(ClassTransformation transformation, MutableComponentModel model)
>     {
>         Moe annotation = transformation.getAnnotation(Moe.class);
>         if (annotation != null)
>             model.setMeta("meta-data.moe", annotation.value());
>     }
> }
> It would be nice if we could just make a contribution:
> configuration.add("meta-data.moe", Moe.class);
> For each of Moe, Larry and Curly instead. This would apply only when the annotation has a single attribute whose type is String.

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


[jira] Updated: (TAP5-461) Create a service that fits into the ComponentClassTransformWorker chain and can be configured to extract component meta-data from class annotations

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-461:
--------------------------------------

    Summary: Create a service that fits into the ComponentClassTransformWorker chain and can be configured to extract component meta-data from class annotations  (was: It is very common to map the value attribute of a type annotation as a meta-data property; it would be nice if there was an easy way to do this, via contributing the annotation type and meta-data key)

> Create a service that fits into the ComponentClassTransformWorker chain and can be configured to extract component meta-data from class annotations
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-461
>                 URL: https://issues.apache.org/jira/browse/TAP5-461
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> In other words, if we have Moe, Larry and Curly and they all look like this:
> public class MoeWorker implements ComponentClassTransformWorker
> {
>     public void transform(ClassTransformation transformation, MutableComponentModel model)
>     {
>         Moe annotation = transformation.getAnnotation(Moe.class);
>         if (annotation != null)
>             model.setMeta("meta-data.moe", annotation.value());
>     }
> }
> It would be nice if we could just make a contribution:
> configuration.add("meta-data.moe", Moe.class);
> For each of Moe, Larry and Curly instead. This would apply only when the annotation has a single attribute whose type is String.

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


[jira] Updated: (TAP5-461) Create a service that fits into the ComponentClassTransformWorker chain and can be configured to extract component meta-data from class annotations

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-461:
--------------------------------------

    Summary: Create a service that fits into the ComponentClassTransformWorker chain and can be configured to extract component meta-data from class annotations  (was: It is very common to map the value attribute of a type annotation as a meta-data property; it would be nice if there was an easy way to do this, via contributing the annotation type and meta-data key)

> Create a service that fits into the ComponentClassTransformWorker chain and can be configured to extract component meta-data from class annotations
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-461
>                 URL: https://issues.apache.org/jira/browse/TAP5-461
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> In other words, if we have Moe, Larry and Curly and they all look like this:
> public class MoeWorker implements ComponentClassTransformWorker
> {
>     public void transform(ClassTransformation transformation, MutableComponentModel model)
>     {
>         Moe annotation = transformation.getAnnotation(Moe.class);
>         if (annotation != null)
>             model.setMeta("meta-data.moe", annotation.value());
>     }
> }
> It would be nice if we could just make a contribution:
> configuration.add("meta-data.moe", Moe.class);
> For each of Moe, Larry and Curly instead. This would apply only when the annotation has a single attribute whose type is String.

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


[jira] Commented: (TAP5-461) It is very common to map the value attribute of a type annotation as a meta-data property; it would be nice if there was an easy way to do this, via contributing the annotation type and meta-data key

Posted by "Massimo Lusetti (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666452#action_12666452 ] 

Massimo Lusetti commented on TAP5-461:
--------------------------------------

Nice! I wanted this for a long time!

> It is very common to map the value attribute of a type annotation as a meta-data property; it would be nice if there was an easy way to do this, via contributing the annotation type and meta-data key
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-461
>                 URL: https://issues.apache.org/jira/browse/TAP5-461
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.0
>            Reporter: Howard M. Lewis Ship
>
> In other words, if we have Moe, Larry and Curly and they all look like this:
> public class MoeWorker implements ComponentClassTransformWorker
> {
>     public void transform(ClassTransformation transformation, MutableComponentModel model)
>     {
>         Moe annotation = transformation.getAnnotation(Moe.class);
>         if (annotation != null)
>             model.setMeta("meta-data.moe", annotation.value());
>     }
> }
> It would be nice if we could just make a contribution:
> configuration.add("meta-data.moe", Moe.class);
> For each of Moe, Larry and Curly instead. This would apply only when the annotation has a single attribute whose type is String.

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


[jira] Assigned: (TAP5-461) It is very common to map the value attribute of a type annotation as a meta-data property; it would be nice if there was an easy way to do this, via contributing the annotation type and meta-data key

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAP5-461:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> It is very common to map the value attribute of a type annotation as a meta-data property; it would be nice if there was an easy way to do this, via contributing the annotation type and meta-data key
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-461
>                 URL: https://issues.apache.org/jira/browse/TAP5-461
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> In other words, if we have Moe, Larry and Curly and they all look like this:
> public class MoeWorker implements ComponentClassTransformWorker
> {
>     public void transform(ClassTransformation transformation, MutableComponentModel model)
>     {
>         Moe annotation = transformation.getAnnotation(Moe.class);
>         if (annotation != null)
>             model.setMeta("meta-data.moe", annotation.value());
>     }
> }
> It would be nice if we could just make a contribution:
> configuration.add("meta-data.moe", Moe.class);
> For each of Moe, Larry and Curly instead. This would apply only when the annotation has a single attribute whose type is String.

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


[jira] Closed: (TAP5-461) Create a service that fits into the ComponentClassTransformWorker chain and can be configured to extract component meta-data from class annotations

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-461.
-------------------------------------

    Resolution: Fixed

Final API doesn't quite match the description (which was just a first pass) but should be pretty clear from the API and from  the examples in TapestryModule.

> Create a service that fits into the ComponentClassTransformWorker chain and can be configured to extract component meta-data from class annotations
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-461
>                 URL: https://issues.apache.org/jira/browse/TAP5-461
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> In other words, if we have Moe, Larry and Curly and they all look like this:
> public class MoeWorker implements ComponentClassTransformWorker
> {
>     public void transform(ClassTransformation transformation, MutableComponentModel model)
>     {
>         Moe annotation = transformation.getAnnotation(Moe.class);
>         if (annotation != null)
>             model.setMeta("meta-data.moe", annotation.value());
>     }
> }
> It would be nice if we could just make a contribution:
> configuration.add("meta-data.moe", Moe.class);
> For each of Moe, Larry and Curly instead. This would apply only when the annotation has a single attribute whose type is String.

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


[jira] Commented: (TAP5-461) It is very common to map the value attribute of a type annotation as a meta-data property; it would be nice if there was an easy way to do this, via contributing the annotation type and meta-data key

Posted by "Massimo Lusetti (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666452#action_12666452 ] 

Massimo Lusetti commented on TAP5-461:
--------------------------------------

Nice! I wanted this for a long time!

> It is very common to map the value attribute of a type annotation as a meta-data property; it would be nice if there was an easy way to do this, via contributing the annotation type and meta-data key
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-461
>                 URL: https://issues.apache.org/jira/browse/TAP5-461
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.0
>            Reporter: Howard M. Lewis Ship
>
> In other words, if we have Moe, Larry and Curly and they all look like this:
> public class MoeWorker implements ComponentClassTransformWorker
> {
>     public void transform(ClassTransformation transformation, MutableComponentModel model)
>     {
>         Moe annotation = transformation.getAnnotation(Moe.class);
>         if (annotation != null)
>             model.setMeta("meta-data.moe", annotation.value());
>     }
> }
> It would be nice if we could just make a contribution:
> configuration.add("meta-data.moe", Moe.class);
> For each of Moe, Larry and Curly instead. This would apply only when the annotation has a single attribute whose type is String.

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