tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Closed: (TAP5-307) The SubmitNotifier mixin should trigger its events when rendering as well as when the form submission is being processed
Date Tue, 28 Oct 2008 16:35:44 GMT

     [ https://issues.apache.org/jira/browse/TAP5-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

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

    Resolution: Invalid
      Assignee: Howard M. Lewis Ship

In retrospect, SubmitNotifier is doing what it should, and a new component, not mixin, is
needed for the situation I was attempting to address.

> The SubmitNotifier mixin should trigger its events when rendering as well as when the
form submission is being processed
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-307
>                 URL: https://issues.apache.org/jira/browse/TAP5-307
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> In my case, I want to put a value into the Environment before rendering some components,
and remove it from the Environment after and I have to use a whole mismash of stuff to do
it because SubmitNotifier only triggers its event during form submission.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message