[Octave-bug-tracker] [bug #45951] Add "xmlread" to core Octave or replace the one in io package

[Philip Nienhuis]

Update of bug #45951 (project octave):

                  Status:                    None => In Progress            

    _______________________________________________________

Follow-up Comment #14:

@Panxto,
sorry I didn't actively follow this bug report - I'll add myself to the
cc-list.
In the mean time the io pkg is already 2 minor versions further 8-Z

What I forgot to mention is that (1) we might have to test for xerces &
xml-apis being in the javaclasspath, (2) in addition we might need to include
them in Windows binary installers.
(1) is implemented in the io package as private function chk_jar_entries.m,
I'll see if I can morph it into some useful form for these new function
scripts. Or if you prefer to have xmlread.m and xmlwrite.m live in the io
package for a while it is even easier.

Normally I have a persistent variable remembering the outcome of all checks,
for performance reasons; I'll try to add this to xmlread/-write.m as well.

As to Java exceptions, I know just enough Java to invoke some methods so I
can't be of any help.

Ah, and I just found that with xml-apis.jar in the javaclasspath as well (next
to xercesImpl.jar), ODF Toolkit works fine (to some extent) with newer xerces
releases than 2.9.1 - one less obstacle for the io package.

So far your xmlwrite/-read.m work fine here.

Status => in progress



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45951>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/