Hi,

There are a couple of tools from kannel to help you test the wbxml compiler:

wmlsc & wmlsdasm

Check them out, they might help you. At present few people in kannel are 
interested in wap, most of them are in SMS.
I am one of the few interested, but haven't been able to test it with a real 
phone yet. I am using winwap for tests, 
though, with no problems.

After I return from my trip, I may have more time to look into it.

BR,
Nikos
  ----- Original Message ----- 
  From: Pai Peng 
  To: [email protected] 
  Sent: Thursday, February 05, 2009 5:48 PM
  Subject: Re: xml to wbxml compiler incorrect by 1.4.2!?


  hello Kannel Users&Developers,


  althrough in the change log for 1.4.1:

Bugfixes:  * ............  *   * Fixed OTA compiler, within WBXML compilation.
  But with libwbxml, binary data converted by libwbxml is different than by 
kannel.

  The binary data converted by kannel can not be decoded back to XML by 
libwbxml: Error: wbxml2xml failed 'Invalid String Table Index'.

  The provisioning doesn't work on my Nokia Symbian 3rd, after SMS received.


  Please confirm me, if I am wrong or not.


  Regards

  Pai



  On Tue, Feb 3, 2009 at 8:15 PM, Pai Peng <[email protected]> wrote:

    hello,


    i have dumped the wbxml data for a OTA-Prov XML into a binary file, which 
data is converted by ota_compiler.c.

    With libxbxml tool (convert wbxml back to xml) to check validity, I got 
error by wbxml2xml:

    ***************************
     Converting file: output.wbxml
    (0) Parsed version: '0x1'
    (1) Parsed publicid: '0x6'
    (2) Parsed charset: '0x2F'
    (3) Parsing strtbl
          Checking PublicID
          PublicID token: 0x6
          PublicID : '-//WAPFORUM//DTD SL 1.0//EN'
    (35) Parsing body
    (35) Parsing element
    (35) Parsing stag
    (36) Parsing content: '0x33'
    (36) Parsing element
    (36) Parsing stag
    (37) Parsing content: '0x34'
    (37) Parsing element
    (37) Parsing stag
    (38) Parsing content: '0x34'
    (38) Parsing element
    (38) Parsing stag
    (39) Parsing content: '0x39'
    (39) Parsing element
    (39) Parsing stag
    (40) Parsing content: '0x44'
    (40) Parsing element
    (40) Parsing stag
    (40) Parsing literalTag
    WBXML Parser failed at 41 - token: 34 (Invalid String Table Index)
    wbxml2xml convertion failed - WBXML Parser Error: Invalid String Table Index
    Current allocations: 0 areas, 0 bytes
    Highest number of allocations: 33 areas
    Highest memory usage: 6001 bytes

    I can be sure, that the wbxml2xml works corretly.
    So my question is, if the kannel's implementation of wbxml is correct or 
the compatibility protocol with libwbxml? has somebody got the same problem by 
XML to WBXML converting?


    Regards

    Pai


Reply via email to