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.
<toast launch="">
<visual lang="en-US">
<binding template="ToastText03">
<text id="1">

</text>
<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.

A future enhancement would be to add configuration support for different notification types such as tiles and badges. The notification type and template choice could be specified via the extensions attribute which is part of the original PushNotification message.

One further configuration note, WNS access token request are defaulted to the URL https://login.live.com/accesstoken.srf. It is also possible to set a different access token if needed via the server context params or command line using the property key
com.icesoft.icepush.wns.accessToken.url.

Resolved via svn repo commit rvn# 38588 - PUSH-322 addition of WNSNotificationProvider for Windows Notification Service (WNS).

This was committed on 6/11/2014.