<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic XERCES C++ (HP v3.0) ACCVIO problem in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/xerces-c-hp-v3-0-accvio-problem/m-p/5207796#M43103</link>
    <description>We're getting access violations as we call  the virtual function getMessage in SaxException class.  The call ACCVIO's; we don't even get into the function, which takes no parameters. The code worked fine with HP v2.2 of XERCES but fails on v3.0.&lt;BR /&gt;&lt;BR /&gt;If anyone has struck this compatibility issue then how did you resolve this?&lt;BR /&gt;&lt;BR /&gt;We have a simple example (a schema and an XML file that doesn't quite match that schema) but the call to XERCES is indirect and we don't know how to access it directly.  We can post this example here (about 20 lines each part) but telling us how to directly access XERCES would be very helpful to us.</description>
    <pubDate>Wed, 04 Nov 2009 23:30:19 GMT</pubDate>
    <dc:creator>John McL</dc:creator>
    <dc:date>2009-11-04T23:30:19Z</dc:date>
    <item>
      <title>XERCES C++ (HP v3.0) ACCVIO problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/xerces-c-hp-v3-0-accvio-problem/m-p/5207796#M43103</link>
      <description>We're getting access violations as we call  the virtual function getMessage in SaxException class.  The call ACCVIO's; we don't even get into the function, which takes no parameters. The code worked fine with HP v2.2 of XERCES but fails on v3.0.&lt;BR /&gt;&lt;BR /&gt;If anyone has struck this compatibility issue then how did you resolve this?&lt;BR /&gt;&lt;BR /&gt;We have a simple example (a schema and an XML file that doesn't quite match that schema) but the call to XERCES is indirect and we don't know how to access it directly.  We can post this example here (about 20 lines each part) but telling us how to directly access XERCES would be very helpful to us.</description>
      <pubDate>Wed, 04 Nov 2009 23:30:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/xerces-c-hp-v3-0-accvio-problem/m-p/5207796#M43103</guid>
      <dc:creator>John McL</dc:creator>
      <dc:date>2009-11-04T23:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: XERCES C++ (HP v3.0) ACCVIO problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/xerces-c-hp-v3-0-accvio-problem/m-p/5207797#M43104</link>
      <description>I had no end of problems with the Xerces port and ended up replacing it with libxml2.  JFP has a PCSI kit containing a recent version of the libxml2 package available.</description>
      <pubDate>Thu, 05 Nov 2009 00:37:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/xerces-c-hp-v3-0-accvio-problem/m-p/5207797#M43104</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-11-05T00:37:24Z</dc:date>
    </item>
    <item>
      <title>Re: XERCES C++ (HP v3.0) ACCVIO problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/xerces-c-hp-v3-0-accvio-problem/m-p/5207798#M43105</link>
      <description>We found errors in our definition of certain C++ structures and correcting those caused the XERCES compiler to successfully complete.&lt;BR /&gt;&lt;BR /&gt;While we were to blame for the failure it seems that Xerces v2 could trap and handle the error but Xerces v3 can not.</description>
      <pubDate>Thu, 12 Nov 2009 02:37:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/xerces-c-hp-v3-0-accvio-problem/m-p/5207798#M43105</guid>
      <dc:creator>John McL</dc:creator>
      <dc:date>2009-11-12T02:37:14Z</dc:date>
    </item>
  </channel>
</rss>

