[jira] [Commented] (TAP5-1741) Parsing template which contains Chinese (Maybe other double bytes) words throws MalformedByteSequenceException: Invalid byte 3 of 3-byte UTF-8 sequence.

[ https://issues.apache.org/jira/browse/TAP5-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13538698#comment-13538698 ] Robert Zeigler commented on TAP5-1741: -- Still potentially a problem in current

[jira] [Closed] (TAP5-1850) Impossible to override the ComponentMessagesSource service, by using the ServiceOverride service

[ https://issues.apache.org/jira/browse/TAP5-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1850. Resolution: Won't Fix Impossible to override the ComponentMessagesSource service, by using the

[jira] [Commented] (TAP5-1850) Impossible to override the ComponentMessagesSource service, by using the ServiceOverride service

[ https://issues.apache.org/jira/browse/TAP5-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13538699#comment-13538699 ] Robert Zeigler commented on TAP5-1850: -- Closing this since there is a viable solution

[jira] [Commented] (TAP5-1925) Rename t:remove to t:annotation

[ https://issues.apache.org/jira/browse/TAP5-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269132#comment-13269132 ] Robert Zeigler commented on TAP5-1925: -- Your proposed renaming assumes that the only

[jira] [Commented] (TAP5-841) DateField selects wrong date if client is in a different timezone than the server

[ https://issues.apache.org/jira/browse/TAP5-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13107843#comment-13107843 ] Robert Zeigler commented on TAP5-841: - For one, the patch you provided doesn't support

[jira] [Commented] (TAP5-841) DateField selects wrong date if client is in a different timezone than the server

[ https://issues.apache.org/jira/browse/TAP5-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13107870#comment-13107870 ] Robert Zeigler commented on TAP5-841: - It was the comment in the patch: // this

[jira] [Closed] (TAP5-1652) template expansion no longer trims whitespace off the right side of the expansion

[ https://issues.apache.org/jira/browse/TAP5-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1652. Resolution: Fixed Fix Version/s: 5.3 template expansion no longer trims whitespace off the

[jira] [Closed] (TAP5-1633) Hardcoded value for Dismiss All in AlertManager

[ https://issues.apache.org/jira/browse/TAP5-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1633. Resolution: Fixed Fix Version/s: 5.3 Implemented as a parameter that uses the message

[jira] [Assigned] (TAP5-1633) Hardcoded value for Dismiss All in AlertManager

[ https://issues.apache.org/jira/browse/TAP5-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1633: Assignee: Robert Zeigler Hardcoded value for Dismiss All in AlertManager

[jira] [Assigned] (TAP5-1640) Introduce a way to define a custom duration for alert messages that have Duration.TRANSIENT

[ https://issues.apache.org/jira/browse/TAP5-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1640: Assignee: Robert Zeigler Introduce a way to define a custom duration for alert messages

[jira] [Closed] (TAP5-1409) datefield - cannot select same day in different month

[ https://issues.apache.org/jira/browse/TAP5-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1409. Resolution: Fixed datefield - cannot select same day in different month

[jira] [Reopened] (TAP5-1408) datefield popup does not have option to cancel

[ https://issues.apache.org/jira/browse/TAP5-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reopened TAP5-1408: -- From 1409: This fix is great but it introduced a different bug. When one clicks on the month name

[jira] [Closed] (TAP5-1408) datefield popup does not have option to cancel

[ https://issues.apache.org/jira/browse/TAP5-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1408. Resolution: Fixed Fixed, with test. datefield popup does not have option to cancel

[jira] [Assigned] (TAP5-841) DateField selects wrong date if client is in a different timezone than the server

[ https://issues.apache.org/jira/browse/TAP5-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-841: --- Assignee: Robert Zeigler DateField selects wrong date if client is in a different timezone

[jira] [Reopened] (TAP5-161) Devise test stategy for DateField and other DHTML/JS intensive components

[ https://issues.apache.org/jira/browse/TAP5-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reopened TAP5-161: - Assignee: Robert Zeigler Re-open to update fix status. Devise test stategy for DateField and

[jira] [Commented] (TAP5-841) DateField selects wrong date if client is in a different timezone than the server

[ https://issues.apache.org/jira/browse/TAP5-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13096329#comment-13096329 ] Robert Zeigler commented on TAP5-841: - I haven't tried the fix yet, so no comment on the

[jira] [Reopened] (TAP5-1409) datefield - cannot select same day in different month

[ https://issues.apache.org/jira/browse/TAP5-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reopened TAP5-1409: -- Re-opened to address month popup issue. datefield - cannot select same day in different month

[jira] [Updated] (TAP5-1448) Example for org.apache.tapestry5.corelib.components.Errors uses invalid xml

[ https://issues.apache.org/jira/browse/TAP5-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler updated TAP5-1448: - Summary: Example for org.apache.tapestry5.corelib.components.Errors uses invalid xml (was: buggy

[jira] [Closed] (TAP5-1448) Example for org.apache.tapestry5.corelib.components.Errors uses invalid xml

[ https://issues.apache.org/jira/browse/TAP5-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1448. Resolution: Fixed Fix Version/s: 5.3 Example for

[jira] [Closed] (TAP5-1620) Tml parsing expression error

[ https://issues.apache.org/jira/browse/TAP5-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1620. Resolution: Fixed Fix Version/s: 5.3 Tml parsing expression error

[jira] [Commented] (TAP5-1620) Tml parsing expression error

[ https://issues.apache.org/jira/browse/TAP5-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094005#comment-13094005 ] Robert Zeigler commented on TAP5-1620: -- So... if you use a reluctant search, then

[jira] [Assigned] (TAP5-1620) Tml parsing expression error

[ https://issues.apache.org/jira/browse/TAP5-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1620: Assignee: Robert Zeigler Tml parsing expression error

[jira] [Commented] (TAP5-1620) Tml parsing expression error

[ https://issues.apache.org/jira/browse/TAP5-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092060#comment-13092060 ] Robert Zeigler commented on TAP5-1620: -- Looks like my fix for maps in template

[jira] [Commented] (TAP5-1616) PeriodicExecutor service prevents running T5.3 on GAE

[ https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13091126#comment-13091126 ] Robert Zeigler commented on TAP5-1616: -- Also in favor of a separate GAE-compatibility

[jira] [Updated] (TAP5-840) Support character references in tml files with HTML 5 Doctype

[ https://issues.apache.org/jira/browse/TAP5-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler updated TAP5-840: Affects Version/s: 5.2.6 5.3 5.1.0.5 Support

[jira] [Closed] (TAP5-1619) When using the HTML5 doctype (!DOCTYPE html), the standard HTML entities should be usable

[ https://issues.apache.org/jira/browse/TAP5-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1619. Resolution: Duplicate Duplicate of TAP5-840 When using the HTML5 doctype (!DOCTYPE html), the

[jira] [Commented] (TAP5-1616) PeriodicExecutor service prevents running T5.3 on GAE

[ https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13091331#comment-13091331 ] Robert Zeigler commented on TAP5-1616: -- Hm, I think the main issues with soft

[jira] [Commented] (TAP5-1616) PeriodicExecutor service prevents running T5.3 on GAE

[ https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13091422#comment-13091422 ] Robert Zeigler commented on TAP5-1616: -- #1) I guess that's personal preference. I

[jira] [Commented] (TAP5-1340) HibernateEntityValueEncoder shouldn't throw an exception when the entity being encoded isn't persisted yet

[ https://issues.apache.org/jira/browse/TAP5-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088849#comment-13088849 ] Robert Zeigler commented on TAP5-1340: -- ValueEncoders aren't a chain, so there's no

[jira] [Assigned] (TAP5-1448) buggy example for org.apache.tapestry5.corelib.components.Errors

[ https://issues.apache.org/jira/browse/TAP5-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1448: Assignee: Robert Zeigler buggy example for org.apache.tapestry5.corelib.components.Errors

[jira] [Commented] (TAP5-411) A persistence strategy to provide page specific state

[ https://issues.apache.org/jira/browse/TAP5-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13086854#comment-13086854 ] Robert Zeigler commented on TAP5-411: - I think the issue is still valid. The addition

[jira] [Updated] (TAP5-411) A persistence strategy to provide page state that persists until the user navigates away from the page

[ https://issues.apache.org/jira/browse/TAP5-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler updated TAP5-411: Summary: A persistence strategy to provide page state that persists until the user navigates away

[jira] [Updated] (TAP5-1570) More javascript events for zones

[ https://issues.apache.org/jira/browse/TAP5-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler updated TAP5-1570: - Issue Type: Improvement (was: Bug) This isn't really a bug. It's not that Tapestry isn't

[jira] [Commented] (TAP5-1504) on GAE Tapestry will crash on startup if tapestry-upload is on the classpath.

[ https://issues.apache.org/jira/browse/TAP5-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13087159#comment-13087159 ] Robert Zeigler commented on TAP5-1504: -- So, on GAE, with your custom implementation of

[jira] [Reopened] (TAP5-1605) Template parsing of expansions can't handle map expressions

[ https://issues.apache.org/jira/browse/TAP5-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reopened TAP5-1605: -- re-open to set the fix version. Template parsing of expansions can't handle map expressions

[jira] [Closed] (TAP5-1605) Template parsing of expansions can't handle map expressions

[ https://issues.apache.org/jira/browse/TAP5-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1605. Resolution: Fixed Fix Version/s: 5.3 Template parsing of expansions can't handle map

[jira] [Commented] (TAP5-1558) FormFragment should allow more fine grained control over when to be considered invisible

[ https://issues.apache.org/jira/browse/TAP5-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13086340#comment-13086340 ] Robert Zeigler commented on TAP5-1558: -- Current behavior in 5.3, using the same tab

[jira] [Closed] (TAP5-1558) FormFragment should allow more fine grained control over when to be considered invisible

[ https://issues.apache.org/jira/browse/TAP5-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1558. Resolution: Fixed Fix Version/s: 5.3 Users can override the default behavior by supplying a

[jira] [Closed] (TAP5-1605) Template parsing of expansions can't handle map expressions

[ https://issues.apache.org/jira/browse/TAP5-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1605. Template parsing of expansions can't handle map expressions

[jira] [Resolved] (TAP5-1605) Template parsing of expansions can't handle map expressions

[ https://issues.apache.org/jira/browse/TAP5-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler resolved TAP5-1605. -- Resolution: Fixed Template parsing of expansions can't handle map expressions

[jira] [Assigned] (TAP5-1558) FormFragment should allow more fine grained control over when to be considered invisible

[ https://issues.apache.org/jira/browse/TAP5-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1558: Assignee: Robert Zeigler FormFragment should allow more fine grained control over when to

[jira] [Commented] (TAP5-1605) Template parsing of expansions can't handle map expressions

[ https://issues.apache.org/jira/browse/TAP5-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13083188#comment-13083188 ] Robert Zeigler commented on TAP5-1605: -- I'm considering replacing the existing regex

[jira] [Commented] (TAP5-1605) Template parsing of expansions can't handle map expressions

[ https://issues.apache.org/jira/browse/TAP5-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13083263#comment-13083263 ] Robert Zeigler commented on TAP5-1605: -- Thinking about this some more... really just

[jira] [Created] (TAP5-1605) Template parsing of expansions can't handle map expressions

Template parsing of expansions can't handle map expressions --- Key: TAP5-1605 URL: https://issues.apache.org/jira/browse/TAP5-1605 Project: Tapestry 5 Issue Type: Bug

[jira] [Assigned] (TAP5-1605) Template parsing of expansions can't handle map expressions

[ https://issues.apache.org/jira/browse/TAP5-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1605: Assignee: Robert Zeigler Template parsing of expansions can't handle map expressions

[jira] [Commented] (TAP5-938) Expose ability to render a portion of a page (a Block, Component, etc.) without using internal services

[ https://issues.apache.org/jira/browse/TAP5-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13081836#comment-13081836 ] Robert Zeigler commented on TAP5-938: - It seems useful for complex ajax scenarios.

[jira] [Resolved] (TAP5-1408) datefield popup does not have option to cancel

[ https://issues.apache.org/jira/browse/TAP5-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler resolved TAP5-1408. -- Resolution: Fixed Fix Version/s: 5.3 datefield popup does not have option to cancel

[jira] [Commented] (TAP5-1408) datefield popup does not have option to cancel

[ https://issues.apache.org/jira/browse/TAP5-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13072107#comment-13072107 ] Robert Zeigler commented on TAP5-1408: -- Went with the ability to click anywhere

[jira] [Closed] (TAP5-1408) datefield popup does not have option to cancel

[ https://issues.apache.org/jira/browse/TAP5-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1408. datefield popup does not have option to cancel --

[jira] [Resolved] (TAP5-1409) datefield - cannot select same day in different month

[ https://issues.apache.org/jira/browse/TAP5-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler resolved TAP5-1409. -- Resolution: Fixed Fix Version/s: 5.3 Datepicker now separates the concepts of the

[jira] [Closed] (TAP5-1409) datefield - cannot select same day in different month

[ https://issues.apache.org/jira/browse/TAP5-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1409. datefield - cannot select same day in different month

[jira] [Commented] (TAP5-1549) ParameterWorker forces evaluation of defaultXXX methods, even if the parameter is bound

[ https://issues.apache.org/jira/browse/TAP5-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060974#comment-13060974 ] Robert Zeigler commented on TAP5-1549: -- Heh. I forgot to mark this as In Progress. :)

[jira] [Commented] (TAP5-1565) OrderedConfiguration should have methods to make it easy to add elements in sequential order

[ https://issues.apache.org/jira/browse/TAP5-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057959#comment-13057959 ] Robert Zeigler commented on TAP5-1565: -- It probably has the potential to break some

[jira] [Commented] (TAP5-1409) datefield - cannot select same day in different month

[ https://issues.apache.org/jira/browse/TAP5-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057472#comment-13057472 ] Robert Zeigler commented on TAP5-1409: -- But no test cases on the patch. :) I'll be

[jira] [Assigned] (TAP5-1549) ParameterWorker forces evaluation of defaultXXX methods, even if the parameter is bound

[ https://issues.apache.org/jira/browse/TAP5-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1549: Assignee: Robert Zeigler ParameterWorker forces evaluation of defaultXXX methods, even if

[jira] [Assigned] (TAP5-1558) FormFragment should allow more fine grained control over when to be considered invisible

[ https://issues.apache.org/jira/browse/TAP5-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1558: Assignee: Robert Zeigler FormFragment should allow more fine grained control over when to

[jira] [Created] (TAP5-1558) FormFragment should allow more fine grained control over when to be considered invisible

FormFragment should allow more fine grained control over when to be considered invisible -- Key: TAP5-1558 URL: https://issues.apache.org/jira/browse/TAP5-1558

[jira] [Assigned] (TAP5-1551) FormFragment change visibility/hide and remove event listeners should call event.stop() to prevent container fragments from also being hidden

[ https://issues.apache.org/jira/browse/TAP5-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1551: Assignee: Robert Zeigler FormFragment change visibility/hide and remove event listeners

[jira] [Resolved] (TAP5-1551) FormFragment change visibility/hide and remove event listeners should call event.stop() to prevent container fragments from also being hidden

[ https://issues.apache.org/jira/browse/TAP5-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler resolved TAP5-1551. -- Resolution: Fixed Fix Version/s: 5.2.6 5.3.1 FormFragment change

[jira] [Closed] (TAP5-1551) FormFragment change visibility/hide and remove event listeners should call event.stop() to prevent container fragments from also being hidden

[ https://issues.apache.org/jira/browse/TAP5-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1551. FormFragment change visibility/hide and remove event listeners should call event.stop() to prevent

[jira] [Closed] (TAP5-1546) TranslatorSource incorrectly annotated with @UsesConfiguration when it should now be @UsesMappedConfiguration (as of 5.2)

[ https://issues.apache.org/jira/browse/TAP5-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1546. TranslatorSource incorrectly annotated with @UsesConfiguration when it should now be

[jira] [Created] (TAP5-1551) FormFragment change visibility/hide and remove event listeners should call event.stop() to prevent container fragments from also being hidden

FormFragment change visibility/hide and remove event listeners should call event.stop() to prevent container fragments from also being hidden -

[jira] [Created] (TAP5-1548) Property expressions fails when using a supertype that implements an interface with a matching method

Property expressions fails when using a supertype that implements an interface with a matching method - Key: TAP5-1548 URL:

[jira] [Updated] (TAP5-1548) Property expressions fails when using a supertype that implements an interface with a matching method

[ https://issues.apache.org/jira/browse/TAP5-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler updated TAP5-1548: - Attachment: generics.bug1demo.tgz Simple project that illustrates the bug. I originally thought

[jira] [Created] (TAP5-1549) ParameterWorker forces evaluation of defaultXXX methods, even if the parameter is bound

ParameterWorker forces evaluation of defaultXXX methods, even if the parameter is bound --- Key: TAP5-1549 URL: https://issues.apache.org/jira/browse/TAP5-1549

[jira] [Assigned] (TAP5-1546) TranslatorSource incorrectly annotated with @UsesConfiguration when it should now be @UsesMappedConfiguration (as of 5.2)

[ https://issues.apache.org/jira/browse/TAP5-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1546: Assignee: Robert Zeigler TranslatorSource incorrectly annotated with @UsesConfiguration

[jira] [Created] (TAP5-1546) TranslatorSource incorrectly annotated with @UsesConfiguration when it should now be @UsesMappedConfiguration (as of 5.2)

TranslatorSource incorrectly annotated with @UsesConfiguration when it should now be @UsesMappedConfiguration (as of 5.2) - Key: TAP5-1546

[jira] [Assigned] (TAP5-1409) datefield - cannot select same day in different month

[ https://issues.apache.org/jira/browse/TAP5-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1409: Assignee: Robert Zeigler datefield - cannot select same day in different month

[jira] [Assigned] (TAP5-1408) datefield popup does not have option to cancel

[ https://issues.apache.org/jira/browse/TAP5-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1408: Assignee: Robert Zeigler datefield popup does not have option to cancel

[jira] [Resolved] (TAP5-1496) Link components should support easily adding request parameters to the generated link

[ https://issues.apache.org/jira/browse/TAP5-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler resolved TAP5-1496. -- Resolution: Fixed Fix Version/s: 5.3.0 Fixed. New parameter name is parameters rather

[jira] [Updated] (TAP5-1495) Tapestry's property expression language should support map creation

[ https://issues.apache.org/jira/browse/TAP5-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler updated TAP5-1495: - Summary: Tapestry's property expression language should support map creation (was: tapestry

[jira] [Resolved] (TAP5-1495) Tapestry's property expression language should support map creation

[ https://issues.apache.org/jira/browse/TAP5-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler resolved TAP5-1495. -- Resolution: Fixed Fix Version/s: 5.3.0 Final map syntax: {a: b, c: d} Tapestry's

[jira] [Commented] (TAP5-1495) tapestry expressions should support a map creation

[ https://issues.apache.org/jira/browse/TAP5-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015188#comment-13015188 ] Robert Zeigler commented on TAP5-1495: -- Fair enough. For the record, I thought of the

[jira] [Commented] (TAP5-1494) PageRenderLinkSource should provide an addParameter(String, Object) method that uses ValueEncoder to coerce the Object to string automatically

[ https://issues.apache.org/jira/browse/TAP5-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015037#comment-13015037 ] Robert Zeigler commented on TAP5-1494: -- Heh. Nice. My bad... I noticed the gap while

[jira] [Commented] (TAP5-1495) tapestry expressions should support a map creation

[ https://issues.apache.org/jira/browse/TAP5-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015042#comment-13015042 ] Robert Zeigler commented on TAP5-1495: -- Igor: By that argument, what's the use case

[jira] [Commented] (TAP5-1493) Property expressions on properties that are covariant on a base class use the type of the base class property, not the covariant subclass

[ https://issues.apache.org/jira/browse/TAP5-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13014813#comment-13014813 ] Robert Zeigler commented on TAP5-1493: -- Just ran into exactly this problem this week.

[jira] [Commented] (TAP5-1493) Property expressions on properties that are covariant on a base class use the type of the base class property, not the covariant subclass

[ https://issues.apache.org/jira/browse/TAP5-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13014949#comment-13014949 ] Robert Zeigler commented on TAP5-1493: -- JVM 6u24, 64 bit. But running on mac.

[jira] [Assigned] (TAP5-1494) PageRenderLinkSource should provide an addParameter(String, Object) method that uses ValueEncoder to coerce the Object to string automatically

[ https://issues.apache.org/jira/browse/TAP5-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1494: Assignee: Robert Zeigler PageRenderLinkSource should provide an addParameter(String,

[jira] [Created] (TAP5-1495) tapestry expressions should support a map creation

tapestry expressions should support a map creation -- Key: TAP5-1495 URL: https://issues.apache.org/jira/browse/TAP5-1495 Project: Tapestry 5 Issue Type: Improvement Components:

[jira] [Assigned] (TAP5-1495) tapestry expressions should support a map creation

[ https://issues.apache.org/jira/browse/TAP5-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1495: Assignee: Robert Zeigler tapestry expressions should support a map creation

[jira] [Assigned] (TAP5-1496) Link components should support easily adding request parameters to the generated link

[ https://issues.apache.org/jira/browse/TAP5-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-1496: Assignee: Robert Zeigler Link components should support easily adding request parameters

[jira] [Created] (TAP5-1496) Link components should support easily adding request parameters to the generated link

Link components should support easily adding request parameters to the generated link - Key: TAP5-1496 URL: https://issues.apache.org/jira/browse/TAP5-1496 Project:

[jira] Commented: (TAP5-1324) Quickstart should setup a basic Hibernate application using HSQL

[ https://issues.apache.org/jira/browse/TAP5-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12924544#action_12924544 ] Robert Zeigler commented on TAP5-1324: -- I'm with Mark. Don't do away with the simple

[jira] Updated: (TAP5-1125) Upload component should be enhanced to work with Ajax

[ https://issues.apache.org/jira/browse/TAP5-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler updated TAP5-1125: - Issue Type: Improvement (was: Bug) Upload component should be enhanced to work with Ajax

[jira] Closed: (TAP5-1025) SetupRender phase method is invoked inconsistently from request to request

[ https://issues.apache.org/jira/browse/TAP5-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-1025. Resolution: Invalid SetupRender phase method is invoked inconsistently from request to request

[jira] Commented: (TAP5-703) Improvement where to save tml files

[ https://issues.apache.org/jira/browse/TAP5-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799602#action_12799602 ] Robert Zeigler commented on TAP5-703: - This should actually be marked as fixed now... the

[jira] Commented: (TAP5-963) Allow access to static resources (css, js, jpg, jpeg, png, gif) inside the app package

[ https://issues.apache.org/jira/browse/TAP5-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12795936#action_12795936 ] Robert Zeigler commented on TAP5-963: - As a matter of fact, I can. I have apps with

[jira] Commented: (TAP5-963) Allow access to static resources (css, js, jpg, jpeg, png, gif) inside the app package

[ https://issues.apache.org/jira/browse/TAP5-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12795618#action_12795618 ] Robert Zeigler commented on TAP5-963: - Do we really want to open up all paths under

[jira] Resolved: (TAP5-815) Asset dispatcher allows any file inside the webapp visible and downloadable

[ https://issues.apache.org/jira/browse/TAP5-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler resolved TAP5-815. - Resolution: Fixed :Fixed for real this time. META-INF and WEB-INF protected, .tml files

[jira] Commented: (TAP5-815) Asset dispatcher allows any file inside the webapp visible and downloadable

[ https://issues.apache.org/jira/browse/TAP5-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789621#action_12789621 ] Robert Zeigler commented on TAP5-815: - Tricky devil. There are still some issues in the

[jira] Reopened: (TAP5-815) Asset dispatcher allows any file inside the webapp visible and downloadable

[ https://issues.apache.org/jira/browse/TAP5-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reopened TAP5-815: - Asset dispatcher allows any file inside the webapp visible and downloadable

[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-tabpanelfocusedCommentId=12788890#action_12788890 ] Robert Zeigler commented on TAP5-909: - 0) Applying getters/setters is NOT a workaround.

[jira] Commented: (TAP5-815) Asset dispatcher allows any file inside the webapp visible and downloadable

[ https://issues.apache.org/jira/browse/TAP5-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12775085#action_12775085 ] Robert Zeigler commented on TAP5-815: - Hey Chris, I just committed the

[jira] Commented: (TAP5-815) Asset dispatcher allows any file inside the webapp visible and downloadable

[ https://issues.apache.org/jira/browse/TAP5-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12774046#action_12774046 ] Robert Zeigler commented on TAP5-815: - Pretty sure Alex was referring to the

[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] 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] Commented: (TAP5-815) Asset dispatcher allows any file inside the webapp visible and downloadable

[ https://issues.apache.org/jira/browse/TAP5-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12748050#action_12748050 ] Robert Zeigler commented on TAP5-815: - Ulrich, Just allow access to Assets really

[jira] Updated: (TAP5-48) Let Tapestry - Hibernate connect to multiple databases

[ https://issues.apache.org/jira/browse/TAP5-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler updated TAP5-48: --- Fix Version/s: (was: 5.1) Let Tapestry - Hibernate connect to multiple databases

[jira] Updated: (TAP5-69) Add annotation, @Contribute, to allow service contributor methods to be arbitrary named

[ https://issues.apache.org/jira/browse/TAP5-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler updated TAP5-69: --- Fix Version/s: (was: 5.1) Add annotation, @Contribute, to allow service contributor methods to be

[jira] Updated: (TAP5-710) Documentation about use of asset: and context: to reference assets directly from a template file has errors (See TAP5-214)

[ https://issues.apache.org/jira/browse/TAP5-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler updated TAP5-710: Fix Version/s: (was: 5.1) Documentation about use of asset: and context: to reference assets

  1   2   >