I tried the same experiment on Windows 10 and got the same failure result as on Windows 7. Java is:
C:\WINDOWS\system32>java -version java version "1.8.0_66" Java(TM) SE Runtime Environment (build 1.8.0_66-b18) Java HotSpot(TM) 64-Bit Server VM (build 25.66-b18, mixed mode) Cheers, Eliot ---- Eliot Kimber, Owner Contrext, LLC http://contrext.com On 3/13/16, 9:05 AM, "Eliot Kimber" <ekim...@contrext.com> wrote: >I tried some more experiments. > >I used the BaseX GUI as follows: > >1. Created a new database and used the GUI to select the catalog file >directly. >2. Used the add function from the New Database dialog to load a directory, >selecting all the .xml, .dita, and .ditamap files. > >All the DITA files were skipped. > >I did the same test using 8.4.1 under OS X but against the same source >files and catalog and it worked fine. > >So this seems to be a general issue with catalog resolution under Windows. > >Cheers, > >E. >---- >Eliot Kimber, Owner >Contrext, LLC >http://contrext.com > > > > >On 3/12/16, 6:11 PM, "Eliot Kimber" ><basex-talk-boun...@mailman.uni-konstanz.de on behalf of >ekim...@contrext.com> wrote: > >>I'm trying to make BaseX work under Windows 7 and I don't seem to be able >>to get catalog resolution to work. (I'm doing a workshop in Japan and the >>classroom only has 32-bit Windows machines available--since Docker >>requires 64-bit Windows I'm having to scramble to make the same code work >>directly under Windows 7 32-bit--ugh.) >> >>I'm using BaseX 8.4.1 with Java 8 (the Java supplied with the 32-bit >>version of oXygenXML). >> >>In my .basex file I have these entries: >> >>CATFILE = C:/workspace/DITA-OT2.x/catalog-dita.xml" >>DTD = true >>SKIPCORRUPT = true >>CHOP = false >> >> >>Using the DBA Web app I can see that the CATFILE property is set to that >>value, DTD is checked, CHOP is unchecked, and SKIPCORRUPT is checked, so >>my settings are clearly being used. >> >>However, if I create a database and use the DBA app to load a document >>that uses a DTD mapped by the catalog (e.g., a DITA document), load fails >>with a "Can't resolve DTD" message. >> >>The document is valid according to oXygen (and it's the same >>catalog--this >>is the OT oXygen is using) and of course my OS X and Docker-based >>versions >>of the same setup work fine, so it looks like a Windows-specific issue. >> >>Is there any known issue with catalog resolution under Windows? Is there >>anything I can do to try to debug the problem? >> >>Thanks, >> >>Eliot >> >>---- >>Eliot Kimber, Owner >>Contrext, LLC >>http://contrext.com >> >> >> >> > > >
