Details
-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA_P02
-
Fix Version/s: EE-3.3.0.GA_P03
-
Component/s: Push Library
-
Labels:None
-
Environment:any
Description
As part of the porting work for MOBI-1059 (Windows unified project) we will require a NotificationProvider implementation that will allow us to send notifications messages with the Windows Notification Service (WNS)
Issue Links
- is duplicated by
-
PUSH-284 Cloud Push for Windows Mobile
- Closed
Activity
Patrick Corless
created issue -
Ken Fyten
made changes -
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | Resolved [ 5 ] |
Assignee | Patrick Corless [ patrick.corless ] | |
Fix Version/s | EE-3.3.0.GA_P03 [ 11571 ] | |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
I've finished the integration work for WNS into icepush-ee. Users of the system must specify their applications SID and secrete via system properties or server context params. For example:
<context-param>
<param-name>com.icesoft.icepush.wns.packageSid</param-name>
<param-value>ms-app://myapp_SID</param-value>
</context-param>
<context-param>
<param-name>com.icesoft.icepush.wns.clientSecret</param-name>
<param-value>myapp_secrete</param-value>
</context-param>
The default notification method is a toast message with the following XAML.
{subject}<toast launch="">
<visual lang="en-US">
<binding template="ToastText03">
<text id="1">
</text>
{details}<text id="2">
</text>
</binding>
</visual>
</toast>
The subject and details params are filled with what ever subject and details that were specified in the PushNotification originator.