|
Re: Proposed fixes to support "multiple code pages" for WBXML documents: msg#00003java.enhydra.kxml
Christian Kurzke wrote: > Please let us know your opinion. Great! :) Thanks a lot! I have committed all of the proposed changes except from the following: 2. To make it working properly we should add "org.kxml2.wap.WbxmlParser, org.kxml2.wap.WbxmlSerializer" I am not sure whether this is a good idea: How can the factory decide to deliver the WBXML parser and not a regular XML parser? The problem is that a regular parser won't work for WBXML and vice versa...? a) In the function nextImpl() replace call peekId() with readByte(). Is there any difference in functionality? With your change, the line "nextId = -2" could be removed, is that correct? Best regards, Stefan Haustein
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Performance comparision of kxml with other wbxml parsers, Garimella Sandilya-W20683 |
|---|---|
| Next by Date: | The kXML mailing list at enhydra.org will be shut down, Stefan Haustein |
| Previous by Thread: | Proposed fixes to support "multiple code pages" for WBXML documents, Christian Kurzke |
| Next by Thread: | The kXML mailing list at enhydra.org will be shut down, Stefan Haustein |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |