| WAP Push to Midlet |  Search
|
|
NowSMS Support Forums ⬆ WAP Technical Discussions (unsupported) ⬆ |
◄ ► |
| Author | Message | |||
| amit nahar New member Username: Amitn Post Number: 1 Registered: 04-2009 |
Hi all, Is it possible to send a WAP Push message to a J2ME Midlet? This way, instead of native WAP mobile application, my J2ME application will process contents of this WAP Message and act accordingly. Currently, it is possible to invoke a J2ME midlet by sending an SMS to Additionally, can a WAP Message consist of an application binary (a JAR file)? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 698 Registered: 08-2008 |
Hi, Generally speaking, your application will not be able to replace the default WAP Push handler (JSR-205 lists the WAP push port as being restricted, so a Java app is not allowed to register to replace the WAP push handler). However, in some environments, you are allowed to register with the WAP push router on the client device to receive WAP push messages of specific content types and/or application ids. I've seen this documented for Windows Mobile, and I suspect that it is available in some other environments as well, but I don't know any more specifics. -- Des NowSMS Support | |||
| amit nahar New member Username: Amitn Post Number: 2 Registered: 04-2009 |
Hey thanks a lot for the update! I understand the restriction of not allowing a J2ME app to register to a standard port. But I can configure my application (using Push Registry ) to wait on incoming SMS on a custom port. Is there any way to send a WAP Push message from a PPG to a *custom* port rather than the standard WAP Push port? This way the received WAP Push SMS will be handed to my J2ME application. I have tried doing this for normal SMS messages (sending them to a custom port rather than the default port 0). This works wonderfully and the J2ME app can read contents and parse the SMS message and act accordingly. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 729 Registered: 08-2008 |
Hi, There is no way to configure NowSMS to send normal format WAP Push messages to an alternate port. It can easily send other messages to any port that you want ... but it won't encode a message into WAP push format and send it to any port other than the WAP push port. Since you're probably just testing/experimenting, I do have one suggestion. You could disconnect your SMSC connection from NowSMS (turn off the modem or disconnect the network cable) ... submit your message ... then manually edit the message file(s) in the Q subdirectory of NowSMS. Look for 0B84 in the UDH ... this is the WAP push destination port (2948 decimal), and you could change it to the port you want to use, then reconnect your SMSC connection to send the message out. -- Des NowSMS Support | |||
