 |
|
    |
 |
|
 |
It has been known for some time that the Openwave Wap Push
library had some issues when connecting to Push Proxy Gateways
other than the ones that are directly associated with an
Openwave MAG. To resolve this issue, the Openwave Developer
Services team has modified the source of the push library to
accomodate the inclusion of an arbitrary DTD with your Push
submissions.
In this new version of wappushlib.jar, two new constructors have been added to the PushMessage Class: PushMessage(String pushID, String address, String papDTDPath)and PushMessage(String pushID, String address, String papDTDPath, MimeEntity payload)
While the PushIT utility has not been updated to leverage this new ability to arbitrarily specify a DTD, we have also provided two new sample classes to be driven from the command line: ServiceInd and ServiceInd. These classes have been
provided in source format as part of this package.
To install this new version of the WAP Push library, you must already have the full version of the Openwave WAP Push library installed on your system (can be dowloaded from the WAP Push Library Download Page if you have not already installed it). Simply replace the wappushlib.jar
file that can be found in
\Openwave\wappushjava1.0\lib (or in the
lib directory fo where ever you have chosen to
install the library. You can place the convenience classes where
ever is most convenient for you. Also included in this package
are copies of the DTDs used for WAP push,
pap_1.0.dtd, si.did, and
sl.dtd for your use if you so desire.
There is no reason for you to upgrade your existing installation of the Openwave WAP Push library if you are not experiencing problems related to the format or version of the DDT that is currently being used. Download the WAP Push Library update here |