[jira] Commented: (TAP5-539) utf-8 content in urls

[ https://issues.apache.org/jira/browse/TAP5-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770776#action_12770776 ] Kalle Korhonen commented on TAP5-539: - Allowing contributions to the safe characters or a

[jira] Updated: (TAP5-905) Properties should be any valid java identifier

[ https://issues.apache.org/jira/browse/TAP5-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manuel Sugawara updated TAP5-905: - Attachment: patch0.txt The attached patch allows tapestry to use valid java identifiers in properti

svn commit: r830396 [1/2] - in /tapestry/tapestry-site/trunk/src/site/xdoc: committers.xml index.xml news.xml

Author: hlship Date: Tue Oct 27 23:18:59 2009 New Revision: 830396 URL: http://svn.apache.org/viewvc?rev=830396&view=rev Log: Add Thiago to the PMC Modified: tapestry/tapestry-site/trunk/src/site/xdoc/committers.xml tapestry/tapestry-site/trunk/src/site/xdoc/index.xml tapestry/tapestr

[jira] Commented: (TAP5-909) Against PRIVATE modifier on fields

[ https://issues.apache.org/jira/browse/TAP5-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770691#action_12770691 ] Aleksandar Nikolov commented on TAP5-909: - Hm... Adding getters/setters is just work

[jira] Created: (TAP5-911) It is possible to have conflicts in ordering of JavaScript initialization on the client-side

It is possible to have conflicts in ordering of JavaScript initialization on the client-side Key: TAP5-911 URL: https://issues.apache.org/jira/browse/TAP5-911

svn commit: r830328 - in /tapestry/tapestry5/trunk/tapestry-beanvalidator/src: main/java/org/apache/tapestry5/beanvalidator/ main/java/org/apache/tapestry5/internal/beanvalidator/ test/java/org/apache

Author: drobiazko Date: Tue Oct 27 20:26:57 2009 New Revision: 830328 URL: http://svn.apache.org/viewvc?rev=830328&view=rev Log: TAP5-895: Tracking issue for Tapestry/JSR-303 integration Added: tapestry/tapestry5/trunk/tapestry-beanvalidator/src/main/java/org/apache/tapestry5/internal/beanva

[jira] Assigned: (TAP5-909) Against PRIVATE modifier on fields

[ https://issues.apache.org/jira/browse/TAP5-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-909: --- Assignee: Robert Zeigler > Against PRIVATE modifier on fields > ---

[jira] Commented: (TAP5-909) Against PRIVATE modifier on fields

[ https://issues.apache.org/jira/browse/TAP5-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770572#action_12770572 ] Robert Zeigler commented on TAP5-909: - Tapestry does a whole ton of bytecode-level enhanc

[jira] Closed: (TAP5-909) Against PRIVATE modifier on fields

[ https://issues.apache.org/jira/browse/TAP5-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-909. --- Resolution: Won't Fix > Against PRIVATE modifier on fields > -- > >

[jira] Created: (TAP5-910) Cookbook: defining a new enum as a component parameter, and adding the string -> enum type coercion for it

Cookbook: defining a new enum as a component parameter, and adding the string -> enum type coercion for it -- Key: TAP5-910 URL: https://issues.apache.org/jira

[jira] Created: (TAP5-909) Against PRIVATE modifier on fields

Against PRIVATE modifier on fields -- Key: TAP5-909 URL: https://issues.apache.org/jira/browse/TAP5-909 Project: Tapestry 5 Issue Type: Wish Components: tapestry-core Affects Versions: 5.0.18

[jira] Closed: (TAP5-906) t:disbled property of input components does not work correctly with property binding

[ https://issues.apache.org/jira/browse/TAP5-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Drobiazko closed TAP5-906. --- Resolution: Cannot Reproduce Fix Version/s: 5.1.0.5 I tried to reproduce the described behaviour