[
https://issues.apache.org/jira/browse/WICKET-6431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16105137#comment-16105137
]
Hendy Irawan edited comment on WICKET-6431 at 7/28/17 3:53 PM:
---------------------------------------------------------------
I noticed that in my complex page, the stateless component HTML IDs increase by
5 everytime, i.e. a0, then aa. Is this normal?
However, when I try a new virgin ID, the stateless component ID only increase
by 1.
Can you give a hint? If skipping IDs by 5 is not normal then perhaps I should
try to make it go back to increasing by 1 again before further actions.
I also get this, both in console and Wicket Ajax Debug, while trying to
target.add() a stateless component within a stateless page:
{code}
Wicket.Ajax.Call.processComponent: Component with id [[fileBorderb5]] was not
found while trying to perform markup update. Make sure you called
component.setOutputMarkupId(true) on the component whose markup you are trying
to update.
(next call:)
Wicket.Ajax.Call.processComponent: Component with id [[fileBorderb7]] was not
found while trying to perform markup update. Make sure you called
component.setOutputMarkupId(true) on the component whose markup you are trying
to update.
(consistent on every ajax call)
{code}
Suggestions very welcome.
was (Author: ceefour):
I noticed that in my complex page, the stateless component HTML IDs increase by
5 everytime, i.e. a0, then aa. Is this normal?
However, when I try a new virgin ID, the stateless component ID only increase
by 1.
Can you give a hint? If skipping IDs by 5 is not normal then perhaps I should
try to make it go back to increasing by 1 again before further actions.
I also get this, both in console and Wicket AJax Debug:
Wicket.Ajax.Call.processComponent: Component with id [[fileBorderb5]] was not
found while trying to perform markup update. Make sure you called
component.setOutputMarkupId(true) on the component whose markup you are trying
to update.
Wicket.Ajax.Call.processComponent: Component with id [[fileBorderb7]] was not
found while trying to perform markup update. Make sure you called
component.setOutputMarkupId(true) on the component whose markup you are trying
to update.
> In a stateful Page, Making AjaxButton stateless makes it not working
> --------------------------------------------------------------------
>
> Key: WICKET-6431
> URL: https://issues.apache.org/jira/browse/WICKET-6431
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.8.0
> Reporter: Hendy Irawan
> Attachments: wicketbug1.jpg
>
>
> Markup:
> {code:xml}
> <form wicket:id="navbarForm">
> <button wicket:id="logoutLink0">Keluar</button>
> </form>
> {code}
> Inside a **stateful** Page, This works:
> {code:java}
> final StatelessForm<Void> navbarForm = new StatelessForm<Void>("navbarForm") {
> @Override
> protected void onSubmit() {
> super.onSubmit();
> log.info("navbarForm onSubmit");
> }
> };
> navbarForm.add(new AjaxButton("logoutLink0", navbarForm) {
> @Override
> protected void onSubmit(AjaxRequestTarget target, Form<?> form) {
> log.info("Uw");
> super.onSubmit(target, form);
> log.info("Aw");
> }
> });
> {code}
> adding to the AjaxButton makes it not working:
> {code:java}
> @Override
> protected boolean getStatelessHint() {
> return true;
> }
> {code}
> By "not working" it means directly redirects to this page again, no onSubmit
> behavior is called (neither for the form nor the button).
> This is the HTTP request that gets sent when (made stateless) button is
> clicked:
> !wicketbug1.jpg|thumbnail!
> (show should attachment image, Jira bug?)
> So to my mind it seems that the sending page is behaving "correctly" (since
> it sends the form), but the receiving page is not reacting correctly, and
> seems to ignore submitted form.
> I observed similar behavior with StatelessLink, but I don't want to conflate
> issues. This could very well be my own fault.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
