Re: Showing session-stored messages in another window/tab

2009-10-19 Thread Esteban Masoero
I'm now calling getSession().info(). However, the message doesn't show up. After debugging for a while I noticed that when de LogjnPage is created, the message I added is there, and is perfectly rendered (I reached the method org.apache.wicket.markup.html.basic.Label.onComponentTagBody(MarkupS

Re: Showing session-stored messages in another window/tab

2009-10-19 Thread Igor Vaynberg
you should call getsession().info() as mentioned in this thread. when you call info() on a component, that messages is scoped to the owning page. when you call getsession().info() the message is scoped to the session and is kept there until rendered. -igor On Mon, Oct 19, 2009 at 12:12 PM, Esteb

Re: Showing session-stored messages in another window/tab

2009-10-19 Thread Esteban Masoero
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 escr

Re: Showing session-stored messages in another window/tab

2009-10-19 Thread Esteban Masoero
I want it to be shown in the LoginPage, because the activation page does not show anything, it only activates the user. I tried something like: LoginPage page = new LoginPage(); page.info("User account activated"); setResponsePage(page); but it didn't work. Anyway, as I know, in order to leave

Re: Showing session-stored messages in another window/tab

2009-10-19 Thread Pedro Santos
- 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

Re: Showing session-stored messages in another window/tab

2009-10-19 Thread Igor Vaynberg
you want the message to show on the loginpage or on the activation page? -igor On Mon, Oct 19, 2009 at 10:08 AM, Esteban Masoero wrote: > Hi: > > We've implemented the classic registration process: > - user registers > - app sends him an email with a generated link > - user clicks that link, whi

Re: Showing session-stored messages in another window/tab

2009-10-19 Thread Esteban Masoero
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 Vytauta

Re: Showing session-stored messages in another window/tab

2009-10-19 Thread Vytautas Racelis
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 me

Re: Showing session-stored messages in another window/tab

2009-10-19 Thread Esteban Masoero
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 (""User account activated"); would help On Mon, Oct 19, 2009 at 8:08 PM, Esteban Maso

Re: Showing session-stored messages in another window/tab

2009-10-19 Thread Vytautas Racelis
Hi, maybe getSession().info (""User account activated"); would help On Mon, Oct 19, 2009 at 8:08 PM, Esteban Masoero wrote: > Hi: > > We've implemented the classic registration process: > - user registers > - app sends him an email with a generated link > - user clicks that li

Showing session-stored messages in another window/tab

2009-10-19 Thread Esteban Masoero
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"); setRespo