[
https://issues.apache.org/jira/browse/TAPESTRY-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Kuhnert resolved TAPESTRY-1656.
-------------------------------------
Resolution: Fixed
Fix Version/s: 4.1.3
Assignee: Jesse Kuhnert
Added listener/parameters parameters to component. Note: calling
updateComponents() from within this listener won't work because of how the
client side widget does the request...So - if you want to be able to do that
you are still better off using the @EventListener approach.
> InlineEditBox needs a listener parameter
> ----------------------------------------
>
> Key: TAPESTRY-1656
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1656
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 4.1.2
> Environment: tapestry 4.1.2, java 1.5.0_07, tomcat 5.5.16, osx 10.4.10
> Reporter: Julian Wood
> Assignee: Jesse Kuhnert
> Priority: Minor
> Fix For: 4.1.3
>
>
> InlineEditBox doesn't really support a good way to get at the change made, so
> that a database can be updated with that change, for instance.
> It automatically sends a request with the change to the server app, but there
> is no hook on this call, and no way to add additional parameters required to
> determine what needs to change.
> You can add an eventListener, but you need to do a bunch of (hacky type) work
> to get the change information submitted, and this means that two (or 3 if you
> submit a second form) requests are sent to the server on each change.
> There is more information in this thread on the mailing list:
> http://www.nabble.com/InlineEditBox-questions-tf4106862.html
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
