[
https://issues.apache.org/jira/browse/WICKET-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760831#action_12760831
]
Flavius commented on WICKET-2494:
---------------------------------
That's a good point, Igor (regarding WICKET-2027).
Juergen, I like your idea and I think that would work for me. I could
instantiate BaseBorder instead of Border. That would keep everything in 1.4.x
working as is and it would essentially solve my dilemma. I presume then that
BaseBorder would not visit the components in the Border (or it's children) on a
form submission.
Thinking out loud, what about a member var in Border called
visitComponentsOnFormSubmit or something like that?
Add a method like
public Border setVisitComponentsOnFormSubmit(boolean visitComponents) {
this.visitComponentsOnFormSubmit = visitComponents;
return this;
}
Then the Border can check this flag to see if it should visit the Border's
components.
Either way, I think this works. Thanks guys, for your help.
> Outside form components problem
> -------------------------------
>
> Key: WICKET-2494
> URL: https://issues.apache.org/jira/browse/WICKET-2494
> Project: Wicket
> Issue Type: Sub-task
> Components: wicket
> Affects Versions: 1.4.2
> Reporter: Pedro Santos
> Assignee: Juergen Donnerstag
> Attachments: BorderVisit.zip, patch.txt
>
>
> "It would be nice if any component can listen to form's event that signals
> form components to update their models"
> -There are some components that implemented they input logic using the
> request parameter (default FormComponet behavior). When Wicket bring those
> components outside the from to his processing, we get some problems: they
> will not receive the user input on page by request parameter map.
> Currently on the user mailing list we can see some case:
> http://markmail.org/search/list:org.apache.wicket.users#query:list%3Aorg.apache.wicket.users%20date%3A200909%20from%3A%22Flavius%22+page:1+mid:ykgrynnsyqaum22o+state:results
> If we execute the project sent ed by Flavius, we can see that the request has
> no parameter to the DropDownChoice component "project", that is on the page
> and outside the form. The component get his convertInput and updateModel
> called by the form process. The convertInput call getInputAsArray, that calls:
> String[] values = getRequest().getParameters(getInputName());
> and get null.
> To resolve that problem on wicket trunk, I'm sending a path that remove from
> the form processing, calls to components outside him(Flavius, maybe you want
> to apply on your workspace Wicket). But this is only an option. I think
> Wicket need review the way to process the form:
> 1- add inputs from outside form components to request
> 2 - remove outside form components from his processing
> 3 - any other option
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
