Hi,

there's no *current* page when a REST request comes in.

Your page should always fetch the current state from a central shared place. It can use an Ajax timer to check for updates or just live with outdated data until the next page refresh.

Regards
Sven


Am 04.03.2015 um 12:12 schrieb jahandideh_iman:
I'm new to wicket and I must create a custom REST api for wicket.
I managed to create a IRequestMapper for accepting REST messages but the
problem is I can't find a way to have access to current page to update it
based on the message.
It seems wicket find the current page based on the pageID that is provided
in url, but I don't want to use this method. Is there any other methods?

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Accessing-Current-Page-In-Custom-Request-Mapper-tp4669833.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...@wicket.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to