[
https://issues.apache.org/jira/browse/WICKET-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760687#action_12760687
]
Igor Vaynberg commented on WICKET-2494:
---------------------------------------
perhaps this is a good example where we can make component#add() nonfinal, and
let the border reroute add calls to the bodycontainer while adding an
border#addToBorder(component) method which will add components to the border
itself.
the problem is a lot of our code has workarounds that are there just for the
border and the impedance mismatch it creates in component hierarchies.
this is not doable for 1.4.x and there we have to live with the pain, but maybe
this is something we can address in 1.5. the only downside is that authors of
borders have to know to use #addToBorder instead of the regular #add, but i
think that is not too big a price to pay for having clean code with consistent
behavior. we can also use good exception messaging to make the users aware of
how to properly build borders.
> 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: 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.
