Well, that's what I did, indeed. But it wasn't enough. I've found a way, I
need more deep testing of it, but for the moment it looks OK.
Regards,
Pierre
On Mon, Feb 24, 2014 at 9:07 AM, Martin Grigorov wrote:
> Hi,
>
> You should have started a page before sending websocket requests to it, as
Hi,
You should have started a page before sending websocket requests to it, as
in the real usage.
By using tester.startPage(thePage) Wicket will store the page in
MockPageManager and later you can find it by its id.
Martin Grigorov
Wicket Training and Consulting
On Sat, Feb 22, 2014 at 5:13 PM,
Hi,
In fact, it is this code:
Session.get().getPageManager().getPage(pageId);
(excerpt from DefaultMapperContext#getPageInstance(final int pageId))
which returns null: the Session.get().getPageManager() contains no pages
when I'm in my Atmosphere context.
Any thoughts, please?
Kind regards,
P
Good evening,
I'm trying to implement the unit test functionality of Wicket-Atmosphere.
I'm stuck on a silly thing.
I have this code in the class AtmosphereRequestHandler:
@Override
public void respond(final IRequestCycle requestCycle)
{
final Page page = (Page)Application.ge
