You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Hugo Palma (JIRA)" <ji...@apache.org> on 2010/03/20 02:10:27 UTC
[jira] Created: (TAP5-1064) Support for Scala properties
Support for Scala properties
----------------------------
Key: TAP5-1064
URL: https://issues.apache.org/jira/browse/TAP5-1064
Project: Tapestry 5
Issue Type: New Feature
Components: tapestry-ioc
Affects Versions: 5.1.0.7
Reporter: Hugo Palma
Attachments: TAP5-1064.patch
As discussed in the dev list (http://markmail.org/thread/upzrocwkkppzmfv2)
It would be great if Tapestry was able to discover Scala properties and not force Scala users to annotate all the properties with the scala.reflect.BeanProperty or BeanInfo annotations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1064) Extend PropertyAccess to understand
Scala style properties (which use a different naming convention than
JavaBeans)
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1064:
---------------------------------------
Assignee: Howard M. Lewis Ship
Summary: Extend PropertyAccess to understand Scala style properties (which use a different naming convention than JavaBeans) (was: Support for Scala properties)
> Extend PropertyAccess to understand Scala style properties (which use a different naming convention than JavaBeans)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1064
> URL: https://issues.apache.org/jira/browse/TAP5-1064
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.1.0.7
> Reporter: Hugo Palma
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.0
>
> Attachments: TAP5-1064.patch
>
>
> As discussed in the dev list (http://markmail.org/thread/upzrocwkkppzmfv2)
> It would be great if Tapestry was able to discover Scala properties and not force Scala users to annotate all the properties with the scala.reflect.BeanProperty or BeanInfo annotations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-1064) Extend PropertyAccess to understand
Scala style properties (which use a different naming convention than
JavaBeans)
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1064.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.2.0
> Extend PropertyAccess to understand Scala style properties (which use a different naming convention than JavaBeans)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1064
> URL: https://issues.apache.org/jira/browse/TAP5-1064
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.1.0.7
> Reporter: Hugo Palma
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.0
>
> Attachments: TAP5-1064.patch
>
>
> As discussed in the dev list (http://markmail.org/thread/upzrocwkkppzmfv2)
> It would be great if Tapestry was able to discover Scala properties and not force Scala users to annotate all the properties with the scala.reflect.BeanProperty or BeanInfo annotations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1064) Support for Scala properties
Posted by "Hugo Palma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hugo Palma updated TAP5-1064:
-----------------------------
Attachment: TAP5-1064.patch
I'm attaching a patch with an implementation for this request with unit tests.
> Support for Scala properties
> ----------------------------
>
> Key: TAP5-1064
> URL: https://issues.apache.org/jira/browse/TAP5-1064
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.1.0.7
> Reporter: Hugo Palma
> Attachments: TAP5-1064.patch
>
>
> As discussed in the dev list (http://markmail.org/thread/upzrocwkkppzmfv2)
> It would be great if Tapestry was able to discover Scala properties and not force Scala users to annotate all the properties with the scala.reflect.BeanProperty or BeanInfo annotations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-1064) Extend PropertyAccess to understand
Scala style properties (which use a different naming convention than
JavaBeans)
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1064.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.2.0
> Extend PropertyAccess to understand Scala style properties (which use a different naming convention than JavaBeans)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1064
> URL: https://issues.apache.org/jira/browse/TAP5-1064
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.1.0.7
> Reporter: Hugo Palma
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.0
>
> Attachments: TAP5-1064.patch
>
>
> As discussed in the dev list (http://markmail.org/thread/upzrocwkkppzmfv2)
> It would be great if Tapestry was able to discover Scala properties and not force Scala users to annotate all the properties with the scala.reflect.BeanProperty or BeanInfo annotations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1064) Extend PropertyAccess to understand
Scala style properties (which use a different naming convention than
JavaBeans)
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1064:
---------------------------------------
Assignee: Howard M. Lewis Ship
Summary: Extend PropertyAccess to understand Scala style properties (which use a different naming convention than JavaBeans) (was: Support for Scala properties)
> Extend PropertyAccess to understand Scala style properties (which use a different naming convention than JavaBeans)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1064
> URL: https://issues.apache.org/jira/browse/TAP5-1064
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.1.0.7
> Reporter: Hugo Palma
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.0
>
> Attachments: TAP5-1064.patch
>
>
> As discussed in the dev list (http://markmail.org/thread/upzrocwkkppzmfv2)
> It would be great if Tapestry was able to discover Scala properties and not force Scala users to annotate all the properties with the scala.reflect.BeanProperty or BeanInfo annotations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1064) Support for Scala properties
Posted by "Hugo Palma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hugo Palma updated TAP5-1064:
-----------------------------
Attachment: TAP5-1064.patch
I'm attaching a patch with an implementation for this request with unit tests.
> Support for Scala properties
> ----------------------------
>
> Key: TAP5-1064
> URL: https://issues.apache.org/jira/browse/TAP5-1064
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.1.0.7
> Reporter: Hugo Palma
> Attachments: TAP5-1064.patch
>
>
> As discussed in the dev list (http://markmail.org/thread/upzrocwkkppzmfv2)
> It would be great if Tapestry was able to discover Scala properties and not force Scala users to annotate all the properties with the scala.reflect.BeanProperty or BeanInfo annotations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.