I haven't thought of that. Thanks, that's another altenative.
However, I'll like yo see whether there's a solution using session
messages, because I think of them as a nicer alternative. If i don't
find a way of achieving this, I'll use the parameter option.
thanks,
Esteban
Pedro Santos escribió:
- app sends him an email with a generated link
can this link encode an parameter like:isActivationFromEmail ?
so:
loginPageOrActivationPage.add(new Label("id","User account
activated").setVisible(getPageParameters().get("isActivationFromEmail"));
On Mon, Oct 19, 2009 at 4:24 PM, Esteban Masoero
<emaso...@getsense.com.ar>wrote:
Sadly, you are not right, because I tried what you suggested and the error
kept appearing. Anyway, I just wanted to know whether the solution I used
was the proper one for this occasion. I didn't say that I'm using wicket
1.3.7. Maybe that has something to do with it?
Thanks,
Esteban
Vytautas Racelis escribió:
Well, Component.info takes WebPage as reporter. Session.info reporter is
null.
As i understand this will be rendered in session scope instead of single
page.
But i may be wrong :)
Esteban Masoero wrote:
But as I see in org.apache.wicket.Component.info(String), that method
already adds that message to the session. Wouldn't be the same?
Vytautas Racelis escribió:
Hi,
maybe getSession().info <http://this.info/>(""User account activated");
would help
On Mon, Oct 19, 2009 at 8:08 PM, Esteban Masoero
<emaso...@getsense.com.ar>wrote:
Hi:
We've implemented the classic registration process:
- user registers
- app sends him an email with a generated link
- user clicks that link, which it's oppened in a new window/tab
- The UserActivationPage that responds to that link request does:
this.info(""User account activated");
setResponsePage(LoginPage.class);
(so the user can log in for the first time)
The problem is that the message is only shown when the link is oppened
in
the same window/tab the user has previously registered. After trying a
few
things, we ended up doing
this.getPageSettings().setAutomaticMultiWindowSupport(false); in
MyApplication, which seems to work (we think is related to wicket using
the
same session, but we're not sure).
However, we're not sure whether it's the best way of solving this. Any
other ideas or comments?
Thanks,
Esteban
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
