Sending core/src/main/java/org/icefaces/application/PushMessage.java
Sending icepush/core/src/main/java/org/icepush/BlockingConnectionServer.java
Sending icepush/core/src/main/java/org/icepush/Browser.java
Sending icepush/core/src/main/java/org/icepush/ConfirmationTimeout.java
Sending icepush/core/src/main/java/org/icepush/InternalPushGroupManager.java
Sending icepush/core/src/main/java/org/icepush/LocalPushGroupManager.java
Sending icepush/core/src/main/java/org/icepush/NotificationEntry.java
Sending icepush/core/src/main/java/org/icepush/OutOfBandNotification.java
Sending icepush/core/src/main/java/org/icepush/PushConfiguration.java
Sending icepush/core/src/main/java/org/icepush/PushNotification.java
Sending icepush/core/src/main/javascript/application.js
Transmitting file data ...........
Committed revision 48664.

Sending eps/src/main/java/com/icesoft/push/Browser.java
Sending eps/src/main/java/com/icesoft/push/ConfirmationTimeout.java
Sending eps/src/main/java/com/icesoft/push/DynamicPushGroupManager.java
Sending eps/src/main/java/com/icesoft/push/InternalPushGroupManager.java
Sending eps/src/main/java/com/icesoft/push/LocalPushGroupManager.java
Sending eps/src/main/java/com/icesoft/push/RemotePushGroupManager.java
Sending eps/src/main/java/com/icesoft/push/StatusManager.java
Transmitting file data .......
Committed revision 45000.

The ability to force a Cloud Push Notification to be sent regardless of the client being active or not has been added at three levels:

1. At the server-side ICEfaces-level using the PushMessage class. The existing two constructors have been overloaded to include a new forced boolean parameter.
2. At the server-side ICEpush-level using the PushNotification class. The existing two constructors have been overloaded to include a new forced boolean parameter.
3. At the client-side ICEpush-level using the notify function. It now parses out a new forced option.

The server-side logic has been augmented to handle this new forced Cloud Push Notification feature. The ConfirmationTimeout ends up with the forced boolean. Previously, upon receiving a new listen.icepush request any outstanding ConfirmationTimeout for the matching Browser-ID would get cancelled. Now it only gets cancelled if the ConfirmationTimeout's isForced() method returns false. Once any ConfirmationTimeout is finished executing it will still cancel itself regardless of what isForced() returns.

Marking this one as FIXED.

Verified ICEfaces EE-4.1.0 r48686. Tomcat 8, android 6.0.1, ios 9.3.1.
The QA test application using the PushMessage class was updated and checked in.
The application has been updated on the Labs1 server.