redirect (in case of
REDIRECT_TO_BUFFER).
If you use REDIRECT_TO_RENDER then those will be executed in the second
request.
With RestartResponseException you have more control with its RedirectPolicy
parameter.
>
> setResponsePage() just schedules rendering of a page (instance).
he second request.
setResponsePage() just schedules rendering of a page (instance).
If you want Wicket to not proceed then you need to throw
RestartResponseException(page[Class])
>
> --
> View this message in context: http://apache-wicket.1842946.
> n4.nabble.com/Calling-setRespo
doing a lot of initialization in onBeforeRender because of our
particular use case. Is this bad practice?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Calling-setResponsePage-during-Ajax-submit-tp4677132p4677138.html
Sent from the Users forum mailing list archi
It's an instance. Specifically in my case it looks like this:
this.setResponsePage(new FormsPage());
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Calling-setResponsePage-during-Ajax-submit-tp4677132p4677137.html
Sent from the Users forum mailing list archi
On Fri, Feb 17, 2017 at 1:32 PM, gmparker2000
wrote:
> Let me try to elaborate a bit more with some pseudo code:
>
> PageOne {
> onInitialize() {
> AjaxButton b = new AjaxButton(...) {
> onSubmit() {
> ...
> setResponsePage(PageB)
&
Let me try to elaborate a bit more with some pseudo code:
PageOne {
onInitialize() {
AjaxButton b = new AjaxButton(...) {
onSubmit() {
...
setResponsePage(PageB)
}
}
// initialize components for page one
TextField t = new TextField
Hi,
your situation looks pretty normal.
What do you mean by "are initialized (again)" - #onInitialize() is
called again?
What argument do you pass to #setResponsePage() ?
Have fun
Sven
On 17.02.2017 02:47, gmparker2000 wrote:
I have the following situation:
- ajax butt
I have the following situation:
- ajax button clicked
- request cycle begins
- the button's onSubmit method is called
- onSubmit method calls setResponsePage
- request cycle continues, *components are initialized*, etc
- request cycle ends with a response that contains an ajax-response red
jaxLink then you don't submit any data. You may try
> AjaxSubmitLink instead.
>
> Please give more information about "but setResponsePage is not working".
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Thu, May
Hi,
If you use AjaxLink then you don't submit any data. You may try
AjaxSubmitLink instead.
Please give more information about "but setResponsePage is not working".
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, May 19, 2016 at 10:11 AM
Hello Josh,
I am stuck in similar situation only. When I hit on the link, I want to show
feedback message if there are some mandatory fields unfilled otherwise I
want to redirect using setResponsePage. If i use AjaxLink then I get
feedback message properly but setResponsePage is not working. When
Created ticket https://issues.apache.org/jira/browse/WICKET-5797
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/setResponsePage-forward-solution-options-tp4668893p4668908.html
Sent from the Users forum mailing list archive at Nabble.com
Hi,
Option 3) is the correct way.
This question has been asked recently by someone else. Maybe we should add
a convenience method for this in Wicket.
Please create a ticket so we don't forget!
On Dec 24, 2014 5:31 PM, "prasad.bhandagi"
wrote:
> I am calling setResponsePag
I am calling setResponsePage(new StatefulPage()), which then redirects the
response, as the default Application level RenderStrategy is
REDIRECT_TO_BUFFER
Only for one scenario I need to forward the request instead of redirecting,
as I need to maintain the original URL for certaing marketing
Its its workaround , not correct fix.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/setResponsePage-with-AjaxButton-not-working-correctly-tp4668881p4668886.html
Sent from the Users forum mailing list archive at Nabble.com
y looks like a workaround!
But I cannot give you more proper solution in this case.
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/setResponsePage-with-AjaxButton-not-working-correctly-tp4668881p4668884.h
when
target.appendJavaScript("window.location='"+urlFor(CreateNewIssueMainPage.class,
params)+"'");
is used with AjaxButton its working, but not sure if its correct way.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/setResponsePa
itten in TestPage.java
>>
>> AjaxButton testButton = new AjaxButton("testButton", form)
>>{
>> private static final long serialVersionUID = 1L;
>>
>> @Override
>> protected void onSubmit(AjaxRequestTarget target, Form form)
&g
onSubmit(AjaxRequestTarget target, Form form)
> {
> setResponsePage(SecondPage.class, pageParams)
> }
> }
>
> When testButton is added inside then only it calls the onSubmit()
> method else not.
>
> and after adding it to tag, its not work
d onSubmit(AjaxRequestTarget target, Form form)
{
setResponsePage(SecondPage.class, pageParams)
}
}
When testButton is added inside then only it calls the onSubmit()
method else not.
and after adding it to tag, its not working for setResponsePage()
call, and shows below error i
werror-upon-running-project/
>
> but when when its changed to tomcat 7.0.52 then also i got the same error.
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Wicket6-setResponsePage-stackoverflow-error-tp4668538p4668571.html
> Sent fro
Got one link:
http://w3facility.org/question/stackoverflowerror-upon-running-project/
but when when its changed to tomcat 7.0.52 then also i got the same error.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket6-setResponsePage-stackoverflow-error
Hi Gabriel, yes we are already changed it to
*liferay-web-xml-enabled=false*
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket6-setResponsePage-stackoverflow-error-tp4668538p4668569.html
Sent from the Users forum mailing list archive at Nabble.com
cket.1842946.n4.nabble.com/Wicket6-setResponsePage-stackoverflow-error-tp4668538p4668566.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional c
;liferay-web-xml-enabled=false" in the liferay-plugin-package.properties
> file.
> I had to do that to have portlet work with liferay 6.1 and 6.2
> see :
>
> http://apache-wicket.1842946.n4.nabble.com/wicket-portlet-and-liferay-6-1-td4650001.html
>
> Also I'm not using PageP
0001.html
Also I'm not using PageParameters, but constructors :
setResponsePage(new MyClass(param1, param2, ...))
I also had to tweak a few files in the wicketstuff-portlet :
-PortletRequesMapper (to handle BookmarkableListenerInterfaceRequestHandler)
-WicketPorlet and ResponseStat (to
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Wicket6-setResponsePage-stackoverflow-error-tp4668538p4668551.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---
-setResponsePage-stackoverflow-error-tp4668538p4668551.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h
dated at
>
> https://issues.apache.org/bugzilla/show_bug.cgi?id=57256
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Wicket6-setResponsePage-stackoverflow-error-tp4668538p4668548.html
> Sent from the U
Its updated at
https://issues.apache.org/bugzilla/show_bug.cgi?id=57256
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket6-setResponsePage-stackoverflow-error-tp4668538p4668548.html
Sent from the Users forum mailing list archive at Nabble.com
29 AM, Milind wrote:
> Hi Martin,
>
> I am using tomcat-7.0.42, tested the same with tomcat-7.0.47/54/57 too
> still same issue happened.
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Wicket6-setResponsePage-stackoverflow-error-tp466
Hi Martin,
I am using tomcat-7.0.42, tested the same with tomcat-7.0.47/54/57 too
still same issue happened.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket6-setResponsePage-stackoverflow-error-tp4668538p4668543.html
Sent from the Users forum mailing list
> FORWARD
> INCLUDE
>
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Wicket6-setResponsePage-stackoverflow-error-tp4668538p4668541.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
>
this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket6-setResponsePage-stackoverflow-error-tp4668538p4668541.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users
I'm no expert but it looks as if your filter from Liferay is looping calls
into Wicket's filter and vice-versa.
What's your web.xml config?
On Tue, Nov 25, 2014 at 12:22 AM, Milind wrote:
> Hello,
>
> I am using Liferay "liferay-portal-6.2-ce-ga2" with
Hello,
I am using Liferay "liferay-portal-6.2-ce-ga2" with Wicket6 and when
setResponsePage(MyClass.class, params); is called it gives stackoverflow
error. Does anyone came across similar error?
http://www.liferay.com/community/forums/-/message_boards/message/45604006
<http://ww
Provider(new
> InternalError(e.getMessage();
>
> is this a good way?
>
>
> Mit freundlichen Grüßen
> Christoph Manig
>
> -Ursprüngliche Nachricht-
> Von: Manig, Christoph
> Gesendet: Dienstag, 22. April 2014 10:43
> An: users@wicket.apache.org
> Betre
: Dienstag, 22. April 2014 10:43
An: users@wicket.apache.org
Betreff: AjaxDownload setResponsePage
Hello,
Iam using AJAXDownload to download some data which will created on the fly,
while clicking an AjaxButton. Moreover Iam using an AbstractResourceStream. In
its getInputStream method, I get an byte
().getReportAsByteStream(slaReportModel.getTxtDatumVon(),slaReportModel.getTxtDatumBis()));
} catch (Exception e) {
log.error(ExceptionUtils.getStackTrace(e));
setResponsePage(new
InternalError(e.getMessage
effectively using a Class for something it's
> not designed for and you shouldn't have to cater for my quirky use of it.
> Having said that, I could easily create my own version - that does that any
> more, and be lighter weight... :)
>
> Although... #setResponsePage could at
it's not
designed for and you shouldn't have to cater for my quirky use of it. Having
said that, I could easily create my own version - that does that any more, and
be lighter weight... :)
Although... #setResponsePage could at least take a IRequestablePage, no? :)
Cheers,
Col.
Hi,
PageProvider is more an internal API. There is a ticket that it is complex
and needs some kind of simplification.
I don't want to expose it more to the user APIs.
How exactly you find it more convenient than the current #setResponsePage()
versions ?
It has constructors that accept render
Wicketeers,
Super-minor API thing...
I've started using PageProvider class within our frameworks, as it's a really
convenient class for detailing pages, etc. and avoid having to use Reflection
directly.
With this in mind, would it be possible to overload Component#setResponsePage
http://apache-wicket.1842946.n4.nabble.com/migrate-to-1-5-setResponsePage-problem-tp4659413p4659418.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For ad
rom wicket 1.4 to 1.5, all my "setResponsePage" calls
> get "red" in Eclipse. e.g:
>
> setResponsePage(WelcomePage.class, parameters);
>
> gets the error message:
> "The method setResponsePage(Class, PageParameters) in the type Component
> is not applicable
In trying to migrate from wicket 1.4 to 1.5, all my "setResponsePage" calls
get "red" in Eclipse. e.g:
setResponsePage(WelcomePage.class, parameters);
gets the error message:
"The method setResponsePage(Class, PageParameters) in the type Component
is not applicable
my pagepanel, the ajax request works;
>>>>> everything seems fine.
>>>>>
>>>>> Than I implemented an abstract method onSelect() to my panel to let an
>>>>> implementation do some custom thinks (the onRequest() of my internal
>>>>&
fine.
>>>>
>>>> Than I implemented an abstract method onSelect() to my panel to let an
>>>> implementation do some custom thinks (the onRequest() of my internal
>>>> behavior just delegates to abstract onSelect() of my panel)
>>>>
>&g
anel)
My first test... simply doing a:
add(new MyPanel("foo"){
public void onSelect(){
setResponsePage(some where)
}
)
but nothing happens...
Using AbstractAjaxDefaultBehavior overriding respond() and delegating to
onSelect() does not work, too.
Do I have to do
gt;>
>> Than I implemented an abstract method onSelect() to my panel to let an
>> implementation do some custom thinks (the onRequest() of my internal
>> behavior just delegates to abstract onSelect() of my panel)
>>
>> My first test... simply doin
abstract method onSelect() to my panel to let an
implementation do some custom thinks (the onRequest() of my internal
behavior just delegates to abstract onSelect() of my panel)
My first test... simply doing a:
add(new MyPanel("foo"){
public void onSelect(){
setResponsePage(
internal
behavior just delegates to abstract onSelect() of my panel)
My first test... simply doing a:
add(new MyPanel("foo"){
public void onSelect(){
setResponsePage(some where)
}
)
but nothing happens...
Using AbstractAjaxDefaultBehavior overriding respond() and delegating to
Hi Jeremy,
redirects via ajax work fine here. See wicket-examples' LinksPage.java
for an example.
Sven
On 04/16/2013 11:30 PM, Jeremy Levy wrote:
I'm using Wicket 6.6.0, in an AjaxSubmitLink when I do a
setResponsepage(myclass.class) or (throw new RedirectResponse) i get the
follo
n I do a
> setResponsepage(myclass.class) or (throw new RedirectResponse) i get the
> following error in the wicket ajax debug console:
>
> *ERROR: *
> Wicket.Ajax.Call.failure: Error while parsing response: Error: Invalid XML:
>
>
> The error console also includes the full HTML of th
I'm using Wicket 6.6.0, in an AjaxSubmitLink when I do a
setResponsepage(myclass.class) or (throw new RedirectResponse) i get the
following error in the wicket ajax debug console:
*ERROR: *
Wicket.Ajax.Call.failure: Error while parsing response: Error: Invalid
XML:
The error console
Moved the discussion of my issue to here since the problem is not really
setResponsePage, but the callback behavior and how it does not "re-read" the
model of the modal window:
http://apache-wicket.1842946.n4.nabble.com/ModalWindow-setWindowClosedCallback-has-access-to-old-model-or
() {
private static final long serialVersionUID = 1L;
public void onClose(AjaxRequestTarget target) {
modalWindowPage.getPage()
.setResponsePage(typeModel.getObject().equals(MyType.SECOND) ? new
SecongPage(parameters
on onClose (or whatever is called the method) do
onClose(AjaxResquestTarget target) {
setResponsePage(A or B).
}
On Thu, Mar 28, 2013 at 5:24 PM, grazia wrote:
> What if one wants to choose whether to redirect to page A or page B ?
> Once the windowClosedCallback is set at modal
-wicket.1842946.n4.nabble.com/close-a-modal-window-and-setResponsePage-tp2074789p4657629.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional
>ComponentNotFoundException when linkB is added to the tree after some
>interaction. So it will become nondeterministic - a russian roulette.
>
>I'll take a look at your new tickets once I have more time
>
>
>>
>> Bernard
>>
>>
>>
>>
e more time
>
> Bernard
>
>
>
> On Fri, 8 Feb 2013 09:09:34 +0100, you wrote:
>
> >Hi,
> >
> >It is OK.
> >But you can also just update some field/model in the current page
> instance.
> >
> >
> >On Fri, Feb 8, 2013 at 7:00 AM, snair
:00 AM, snair
>wrote:
>
>> Is it ok to call the same page using setResponsePage(), only calling a
>> different constructor, since the page now needs to display additional
>> information, which I will be passing into this new constructor? For
>> example, from PageA, ca
Hi,
It is OK.
But you can also just update some field/model in the current page instance.
On Fri, Feb 8, 2013 at 7:00 AM, snair wrote:
> Is it ok to call the same page using setResponsePage(), only calling a
> different constructor, since the page now needs to display additional
> in
Yes, as per the API for the component class:
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/Component.html#setResponsePage(java.lang.Class)
setResponsePage
public final void setResponsePage(Class cls)
Sets the page that will respond to this request
Type Parameters:
C
Thx for this post, it also helped me :)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/AjaxSubmitLink-setResponsePage-feedback-message-problem-on-new-page-tp1843719p4654214.html
Sent from the Users forum mailing list archive at Nabble.com
Hi,
Because you pass an instance of a page and this instance to be
reachable in the next request should be stored.
Use setResponsePage(Class) instead. Your page is stateless, so
instantiating a completely new instance in the next request should be
the same.
On Mon, Sep 3, 2012 at 9:19 AM, Gereon
Hi,
I have a bunch of stateless pages, each calling setStatelessHint(true) in
the constructor to indicate this. I've now noticed that when one of these
pages calls setResponsePage, the target page is always considered
stateful, since RequestCycle#setResponsePage explicitly resets the hint.
Hi Martin,
Following Andrea's comments from issue Wicket-4637, I modified the
NonResettingRestartException to fix the error I reported.
Here's the modified version:
public class NonResettingRestartException extends ReplaceHandlerException {
public NonResettingRestartException(final Class
Hi,
Issues WICKET-4636 and WICKET-4637 were created.
Bertrand
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
o have this functionality working in all cases.
>
> In conclusion, with Wicket 1.5.7, NonResettingRestartException works in a
> page constructor, but setResponsePage must be used in a link or form
> handler.
>
> So there is a workable alternative, but the difference in behavior de
ks in
a page constructor, but setResponsePage must be used in a link or form
handler.
So there is a workable alternative, but the difference in behavior
depending on where the exception is thrown is not so good. And maybe
other code paths are at risk of triggering this exception.
Part
Hi,
Here is my later response.
I see two ways to solve this:
1) Use setResponsePage(pageInstance) as I described in my previous response:
setMyCookie();
PageB pageB = new PageB();
pageB.info("some text");
setResponsePage(pageB);
This way the feedback is associated with a component (
Another way to solve this is to use:
setCookie();
PageB pageb = new PageB();
pageB.info(something);
setResponsePage(pageb)
On Fri, Jun 29, 2012 at 5:25 PM, Bertrand Guay-Paquet
wrote:
> Ok now I understand! What you suggest is more or less what I mentioned in
> the first
wrote
Hi Ian,
Thanks for your reply. By the way, I forgot to mention I'm using Wicket
1.5.7.
The (pseudo) code I wrote in my previous email is in Page2's
constructor. I tried both approaches and here are the results:
setResponsePage in page constructor:
-Cookie not set<=== Cookie SET
gt;
>> Regards,
>>
>> Ian
>>
>>
>> Bertrand Guay-Paquet wrote
>>> Hi Ian,
>>>
>>> Thanks for your reply. By the way, I forgot to mention I'm using Wicket
>>> 1.5.7.
>>>
>>> The (pseudo) code I wrote i
ected void onBeforeRender() {
if(doRedirect) {
setACookie();
Session.get().info("blah");
setResponsePage(Page1.class);
}
}
I know the cookie setting bit is fixed in WICKET-4358, so I'm not too
worried about that. It's really the session flash messages that I can&
The (pseudo) code I wrote in my previous email is in Page2's
constructor. I tried both approaches and here are the results:
setResponsePage in page constructor:
-Cookie not set<=== Cookie SET with patch from WICKET-4358
-Session message not displayed on Page1
setResponsePage in form onSubmit:
nks for your reply. By the way, I forgot to mention I'm using Wicket
> 1.5.7.
>
> The (pseudo) code I wrote in my previous email is in Page2's
> constructor. I tried both approaches and here are the results:
> setResponsePage in page constructor:
> -Cookie not set <
Hi Bertrand,
I'll write a more detailed answer to your mail later.
Until then you can try to workaround it by calling 'setResponsePage()'
in #onBeforeRender() instead.
On Fri, Jun 29, 2012 at 4:21 PM, Bertrand Guay-Paquet
wrote:
> Hi Ian,
>
> Thanks for your reply.
Hi Ian,
Thanks for your reply. By the way, I forgot to mention I'm using Wicket
1.5.7.
The (pseudo) code I wrote in my previous email is in Page2's
constructor. I tried both approaches and here are the results:
setResponsePage in page constructor:
-Cookie not set <=== Cookie S
experience between
setResponsePage(WebPage.class) and using a RestartResponseException (as
always, I am open to contradiction).
· If possible, can you move your code to a component onSubmit() method
(of Page2 or the previous page, if any)?
Regards,
Ian
Bertrand Guay-Paquet wrote
>
> Hi,
Hi,
I have 2 pages, each with a feedback panel. Page2 does the following:
setACookie();
Session.get().info("blah");
setResponsePage(Page1.class);
The problem I have is that "blah" is never displayed in the feedback
panel of Page1. I stepped in the request processing
:
> At Page1 in list I had class="current" and wicket:id="page1", they didn't
> show up
> in my intitial post
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Keep-css-changes-after-setResponsePage-tp4650206p4650207
At Page1 in list I had class="current" and wicket:id="page1", they didn't
show up
in my intitial post
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Keep-css-changes-after-setResponsePage-tp4650206p4650207.html
Sent from the Users foru
rent class from page1 li
target.addComponent(listContainer);
setResponsePage(Page1.class);
}
};
After I add the setResponsePage(), the css class changes are not visible
anymore. Is there a way to
make the chages to my list remain after calling setRe
Page.this.continueToOriginalDestination()) {
>>> PageParameters pp = new PageParameters();
>>> pp.add("page", "fleetlist");
>>> setResponsePage(new DesktopPage(pp));
>>
>>
>> There is a small but important differ
()) {
PageParameters pp = new PageParameters();
pp.add("page", "fleetlist");
setResponsePage(new DesktopPage(pp));
There is a small but important difference between
setResponsePage(Page) and setResponsePage(Class).
In most cases I'd recommend to use the
Target
> target) {
> EmobWebSession.get().setAuthenticatedUser(user);
>
> if (!LoginPage.this.continueToOriginalDestination()) {
> PageParameters pp = new PageParameters();
> pp.add("page", "fleetlist");
> setResponsePa
);
if (!LoginPage.this.continueToOriginalDestination()) {
PageParameters pp = new PageParameters();
pp.add("page", "fleetlist");
setResponsePage(new DesktopPage(pp));
}
}
this code leads me to the root context of the server... Oddly e
ind wrote:
> Hi,
>
> I have difficulties in using the setResponsePage in ajax call as Wicket
> seems to direct the
> call to a relative URL. As a result, the request is made to the root context
> an that gives me
> a 404.
>
> The scenario is as follows: I have a login
Please provide some code-samples to show us what you are doing.
If it's related to an older issue it would be great if you could give more
details (link to the issue).
Am 26.04.12 11:05 schrieb "Jürgen Lind" unter :
>Hi,
>
>I have difficulties in using the setResponsePag
Hi,
I have difficulties in using the setResponsePage in ajax call as Wicket seems
to direct the
call to a relative URL. As a result, the request is made to the root context an
that gives me
a 404.
The scenario is as follows: I have a login form and would like to provide user
feedback on
Take a look at WebPageRenderer#respond(): Inside Ajax requests it
responds with a redirect, which is then analyzed and performed by
wicket-ajax.js in the browser.
Sven
On 02/01/2012 09:43 PM, Richard W. Adams wrote:
I'm having a hard time understanding what happens when setResponsePage
I'm having a hard time understanding what happens when setResponsePage()
is called while processing an Ajax request. Does Wicket:
1. Render the response page's HTML & send it back through the Ajax
connection?
2. Tell the browser to make a new request (i.e., redirect) to the
-0700 (PDT), you wrote:
>
> >Hi,
> >
> >Geoff Hayman raised this issue previously here:
> >http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-setResponsePage-page-still-tries-to-render-HTML-before-redirect-td3819145.html
> >
> >but apparently go
On Sat, Nov 5, 2011 at 6:50 AM, wrote:
> Hi,
>
> To abort the construction of the page, you throw
> ResetResponseException or subclasses.
Yes,
RestartResponseException should be used instead of setResponsePage()
>
> Regards,
>
> Bernard
>
>
> On Fri, 4 Nov 201
Hi,
To abort the construction of the page, you throw
ResetResponseException or subclasses.
Regards,
Bernard
On Fri, 4 Nov 2011 19:12:34 -0700 (PDT), you wrote:
>Hi,
>
>Geoff Hayman raised this issue previously here:
>http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-setRespo
Hi,
Geoff Hayman raised this issue previously here:
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-setResponsePage-page-still-tries-to-render-HTML-before-redirect-td3819145.html
but apparently got no response (and Nabble won't let me reply to that for
some reason... conspiracy?)
I&#
http://localhost:8080/?0-1.IFormSubmitListener-signInPanel-signInForm
[HTTP/1.1 302 Found 8ms]
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/setResponsePage-is-not-working-in-SignInPanel-tp3823554p3823583.html
Sent from the Users forum mailing list archive at Nabbl
User button*
>
> *Button registerButton= new Button("register" )
> {
> public void onSubmit()
> {
>
>
> setResponsePage(AddNewCustomerPage.class);
>
1 - 100 of 285 matches
Mail list logo
