[
https://issues.apache.org/jira/browse/WICKET-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098329#comment-14098329
]
ASF subversion and git services commented on WICKET-5452:
---------------------------------------------------------
Commit dfdcea562b5541009dd4cd7586407e2dff18dcd7 in wicket's branch
refs/heads/master from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=dfdcea5 ]
WICKET-5452 Make Wicket-Atmosphere testable - AtmosphereTester
Remove custom executors - they are no needed because of
TesterBroadcaster#executeBlockingWrite(AtmosphereResource, Entry)
(cherry picked from commit 2a52b360bf964a162cf8e76d94ad3d42ae17fd88)
> Make Wicket-Atmosphere testable - AtmosphereTester
> --------------------------------------------------
>
> Key: WICKET-5452
> URL: https://issues.apache.org/jira/browse/WICKET-5452
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-atmosphere
> Affects Versions: 6.12.0
> Reporter: Zala Goupil
> Assignee: Martin Grigorov
>
> Presently, when a wicket-tester based unit test executes such a line:
> Application.get().getEventBus().post(new Event(), pageUuid);
> it throws a NullPointerException.
> I have two requests:
> - please, get rid of this Exception, indeed.
> - then make the generated HTML testable, just like wicket-tester allows to
> test Ajax responses.
> That would be the killer-feature of the wicket-atmosphere framework, IMHO.
> Regards,
> Pierre
--
This message was sent by Atlassian JIRA
(v6.2#6252)
