Re: Anyone getting XML to work??

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

In case you are not using a real newsreader, I just posted a message with an
attached sample ZIPped up...

Paul T.

"Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT com>
wrote in message news:OTeADDBUFHA.1152@xxxxxxxxxxxxxxxxxxxxxxx
> Here you go. A relatively simple example of parsing a small XML file from
> the local filesystem.
>
> Paul T.
>
> "Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT com>
> wrote in message news:usDJi$$TFHA.4092@xxxxxxxxxxxxxxxxxxxxxxx
>>I don't have any OSes with just the minimal parser in them, but I'll see
>> what I can whip up showing SAX.
>>
>> Paul T.
>>
>> "Carl Dreher" <CarlDreher@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:7A7A7BCB-9657-48EB-A630-66081632914A@xxxxxxxxxxxxxxxx
>>> I'm simply trying to read (parse) and write some XML files on a headless
>>> WinCE device. The first attempt was to build the OS using the minimal
>>> SAX
>>> support option. The 3-part example provided in the CE4.2 doc shows the
>>> following:
>>>
>>> #include "stdafx.h"
>>> #include "MyContent.h"
>>> #include "SAXErrorHandlerImpl.h"
>>> int main(int argc, char* argv[])
>>> {
>>> ...
>>>
>>> The file "SAXErrorHandlerImpl.h" does NOT exist anywhere in the OS
>>> support.
>>> The only way I was able to create an error handler was to implement the
>>> entire ISAXErrorHandler interface, and guess what? There is NO
>>> documentation
>>> on that interface, so I'm working blind as to what most of the functions
>>> do.
>>> The class I created that meets the interface spec does compile but upon
>>> running it, it crashes upon loading, so I have no forensics to find out
>>> why.
>>>
>>> Even worse, there are NO..ZERO, NONE, NADA... examples of how to use the
>>> more complicated DOM interface.
>>>
>>> Did MicroSoft just bail out of XML support for CE4.2 and but leave it in
>>> the
>>> documentat? How come a company with more money than God can't write
>>> documentation?
>>>
>>> This is yet ANOTHER example of why I will NEVER do another project in
>>> WinCE.
>>> (Assuming I survive this mess.)
>>>
>>>
>>
>>
>
>
>


.

Relevant Pages

  • Re: CreateFile api call failing
    ... Paul T. ... NDISUIO and use that to send OIDs to the driver. ... hence i m trying to open the interface to get a valid handle. ...
    (microsoft.public.windowsce.app.development)
  • Re: 2.6.24-rc6-mm1 - git-lblnet.patch and networking horkage
    ... tcl tests won't run without an external interface). ... SELinux: Convert the netif code to use ifindex values ... permissive and enforcing mode without generating any log messages. ... I suggest dropping the patchset from -mm until Paul gets back from ...
    (Linux-Kernel)
  • Re: I backed out of the deal
    ... stranger in West St. Paul where I normally did not do business. ... I did explain that we didn't find out about the TV not being the one in the documentation until after we put the deposit down, but you were so intent on being your usual hateful self that you must have missed it. ... We had already put the deposit down when we learned of the TV switch. ...
    (rec.outdoors.rv-travel)
  • Re: VB6 App to ASP
    ... it was in the documentation. ... Regards ... Paul ... > component should expose its own collection of the other form elements. ...
    (microsoft.public.inetserver.asp.db)
  • Re: I backed out of the deal
    ... stranger in West St. Paul where I normally did not do business. ... I did explain that we didn't find out about the TV not being the one in the documentation until after we put the deposit down, but you were so intent on being your usual hateful self that you must have missed it. ... Those who have the ability to read English were able to see that it wasn't until we contacted the TV manufacturer as per the booklet with the documentation in the camper that we found out from the dealer that the TV in the camper was not the TV in the documentation. ...
    (rec.outdoors.rv-travel)