- cxml-devel - mailman3.common-lisp.net

[cxml-devel] SAX handler
by Andy Chambers 10 Sep '08

10 Sep '08

Hi, What is the current recommended method of implementing a custom SAX handler? The documentation says that you just need to implement the generic functions for any old class but when you do that, you get lots of warnings like the following. "deprecated SAX default method used by a handler that is not a subclass of SAX:ABSTRACT-HANDLER or HAX:ABSTRACT-HANDLER" Should new code inherit from sax:default-handler? Cheers, Andy

2 1

[cxml-devel] CXML performance
by Chaitanya Gupta 10 Sep '08

10 Sep '08

Hi, I tried using CXML to parse a slightly big (~1.2 MB) XML in ACL 8.0. I am using the following form to parse it into a DOM: (cxml:parse xml (cxml-dom:make-dom-builder)) ; xml is a string Generally, it takes about 0.73-0.75 sec to parse on my machine. What also happens is that, while the parser is running, it blocks all the other threads i.e. they become unresponsive. Any clues on why it can be happening? And how it can be fixed? Also, ACL on OS X (and Linux) does not run any Lisp code while a foreign call is being made (thus blocking all the other threads). Is there any chance that CXML calls any foreign code? Chaitanya

3 5

[cxml-devel] Fwd: Problem with cxml-xmls:map-node?
by Daniel Katz 19 Aug '08

19 Aug '08

Hi - I'm exploring cxml, and I'm running into trouble using the cxml- xmls:map-node. I don't know whether I'm doing something stupid or whether it's a bug, so I thought I'd ask here. I began by following the example in the Quick-Start Guide (http:// common-lisp.net/project/cxml/quickstart.html#id54132) and found myself in the debugger with an error related to namespaces: > > CL-USER> (with-open-file (out > "example.out" :direction :output :element-type '(unsigned-byte 8)) > (cxml-xmls:map-node (cxml:make-character-stream- > sink out) > '("test" (("a" "b")) > ("child" nil)))) > > serializing with :INCLUDE-NAMESPACE-URI, but node was created > without namespace URI > [Condition of type SIMPLE-ERROR] > > Restarts: > 0: [ABORT] Return to SLIME's top level. > 1: [ABORT-BREAK] Reset this process > 2: [ABORT] Kill this process > > Backtrace: > 0: ((:INTERNAL CXML-XMLS::WALK CXML-XMLS::MAP-NODE/LNAMES) > '("test" (("a" "b")) ("child" NIL))) > 1: (CXML-XMLS::MAP-NODE/LNAMES #<CXML::NAMESPACE-NORMALIZER > #x8D0290E> '("test" (("a" "b")) ("child" NIL)) 'T) > 2: (#<Anonymous Function #x8D04486>) I have to admit that I didn't find this error to be very useful in terms of understanding what the problem is. My second attempt was to avoid constructing the xmls-style data by hand but to instead take the output of a cxml parse. Suffice it to say that I ran into the same issue: > CL-USER> (with-open-file (out "foo.out" :direction :output :element- > type '(unsigned-byte 8)) > (cxml-xmls:map-node (cxml:make-character-stream- > sink out) > (cxml:parse-file > "foo.xml" (cxml-xmls:make-xmls-builder)))) > > > serializing with :INCLUDE-NAMESPACE-URI, but node was created > without namespace URI > [Condition of type SIMPLE-ERROR] > > Restarts: > 0: [ABORT] Return to SLIME's top level. > 1: [ABORT-BREAK] Reset this process > 2: [ABORT] Kill this process > > Backtrace: > 0: ((:INTERNAL CXML-XMLS::WALK CXML-XMLS::MAP-NODE/LNAMES) > '("foo" NIL " > " > ("bar" (("quux" "quux")) " > baz > ") > " > ")) > 1: (CXML-XMLS::MAP-NODE/LNAMES #<CXML::NAMESPACE-NORMALIZER > #x8CFCF86> '("foo" NIL " > " > ("bar" (("quux" "quux")) " > baz > ") > " > ") 'T) > 2: (#<Anonymous Function #x8C7D31E>) > 3: (SWANK::EVAL-REGION "(with-open-file (out \"foo.out\" > :direction :output > :element-type '(unsigned-byte 8)) > (cxml-xmls:map-node (cxml:make-character-stream-sink out) > (cxml:parse-file \"foo.xml\" (cxml-xmls:make-xmls- > builder)))) > ") So now I'm sort of at a loss for what to do next. And my basic question once again is: am I doing something stupid? Or is the xmls- style serialization facility broken? Thanks. Dan

1 1

[cxml-devel] Bug in validating XSD:DATE
by Chaitanya Gupta 18 Aug '08

18 Aug '08

If I have an RNC file which looks like this: start = element foo { element bar { text }, element baz { xsd:date } } and try to validate against this schema an XML which looks like this: <foo> <bar>haha!</bar> <baz>2008-09-09T22:00:00</baz> </foo> (Note that the value of 'baz' should have been a date, not a date-time) I get the following error/backtrace: `NIL' is not of the expected type `NUMBER' [Condition of type TYPE-ERROR] Restarts: 0: [ABORT-REQUEST] Abort handling SLIME request. 1: [ABORT] Abort entirely from this (lisp) process. Backtrace: 0: (SWANK::DEBUG-IN-EMACS #<TYPE-ERROR @ #x117dba9a>) 1: (SWANK:SWANK-DEBUGGER-HOOK #<TYPE-ERROR @ #x117dba9a> #<Function SWANK-DEBUGGER-HOOK>) 2: (ERROR TYPE-ERROR :DATUM NIL :EXPECTED-TYPE NUMBER :FORMAT-CONTROL "~@<`~s' is not of the expected type `~s'~:@>" :FORMAT-ARGUMENTS (NIL NUMBER)) 3: (CXML-TYPES::PARSE-TIME NIL NIL NIL NIL #1="0" #1# #1# NIL NIL ...) 4: ((METHOD CXML-TYPES::PARSE/XSD (CXML-TYPES:DATE-TYPE T T)) #<CXML-TYPES:DATE-TYPE > "2008-09-09T22:00:00" #<CXML-RNG::VALIDATOR @ #x117cb302>) 5: ((METHOD CXML-TYPES::PARSE/XSD :AROUND (CXML-TYPES:XSD-TYPE T T)) #<CXML-TYPES:DATE-TYPE > "2008-09-09T22:00:00" #<CXML-RNG::VALIDATOR @ #x117cb302>) 6: ((:INTERNAL (:EFFECTIVE-METHOD 3 NIL NIL T T) 0) #<CXML-TYPES:DATE-TYPE > "2008-09-09T22:00:00" #<CXML-RNG::VALIDATOR @ #x117cb302>) 7: ((METHOD CXML-TYPES:VALIDP (CXML-TYPES:XSD-TYPE T)) #<CXML-TYPES:DATE-TYPE > "2008-09-09T22:00:00" #<CXML-RNG::VALIDATOR @ #x117cb302>) 8: ((METHOD CXML-RNG::|DATA'| (T CXML-RNG:DATA T)) #<CXML-RNG::VALIDATOR @ #x117cb302> #<CXML-RNG:DATA @ #x117c65a2> "2008-09-09T22:00:00") Attached is a patch which fixes this. Now I get the expected error: text node not valid, was expecting a text node of type #<DATE-TYPE > [ Error at line 3, column 33 in #<PURI:URI file://+/Users/chaitanya/tmp/test.xml> ] [Condition of type CXML-RNG:RNG-ERROR] On a side note, I think that the error reporting can be improved a bit. e.g. the element inside which the validation error was encountered, can that also be reported? Chaitanya diff --git a/types.lisp b/types.lisp index 26f89fa..1d481c6 100644 --- a/types.lisp +++ b/types.lisp @@ -1049,11 +1049,11 @@ (num (str) (and str (parse-number:parse-number str)))) (setf (values y m d h min s tz-h tz-m) - (values (* (int y) (if minusp -1 1)) + (values (and y (* (int y) (if minusp -1 1))) (int m) (int d) (int h) (int min) (num s) (int tz-h) (int tz-m)))) - (let ((day-limit (day-limit m y))) + (let ((day-limit (and m y (day-limit m y)))) ;; check ranges (cond ((and y m d h min s

1 0

[cxml-devel] Problem compiling PARSE-SCHEMA on ACL
by Chaitanya Gupta 18 Aug '08

18 Aug '08

Hi, When I try to call PARSE-SCHEMA in ACL, I get this error -- attempt to call the undefined function (SETF CXML-RNG::GRAMMAR-START) with args: #S(CXML-RNG::DEFINITION :NAME :START :COMBINE-METHOD NIL :HEAD-P NIL :REDEFINITION NIL :CHILD ...) #S(CXML-RNG::GRAMMAR :START NIL :PARENT NIL :DEFINITIONS #<EQUAL hash-table with 0 entries @ #x13904c62>). [Condition of type UNDEFINED-FUNCTION] This happens because GRAMMAR is defined after PARSE-SCHEMA in parse.lisp. Same issue with the DEFN-CHILD accessor for DEFINITION. If I move the definition of PARSE-SCHEMA to the end of the file, for example, the issue is fixed. Chaitanya

2 4

[cxml-devel] out of synch with cl-ppcre
by Ben Hyde 16 Aug '08

16 Aug '08

The code around *convert-char-class-to-hash* in nppcre.lisp fails now since cl-ppcre::convert-char-class-to-hash is no more. I was able to get things to compile by commenting it out. I haven't a clue what that's going to break ...

1 0

[cxml-devel] Problems with Xuriella on LispWorks
by Jochen Schmidt 15 Jun '08

15 Jun '08

Hi, I had problems compiling Xuriella (a current clone from the git repository) with LispWorks. There were a few problems regarding the order of the definitions. Common Lisp is quite sensitive to the order of definitions if macros or structures are used. You have to define a structure before you use it (this also entails accesses using structure-slot-accessors). You also have to define a macro before compiling a function using that macro. I've fixed those issues locally here and Xuriella runs now withing my LispWorks setup. If you're interested in what I've done; how should I make my changes available? ciao, Jochen -- Jochen Schmidt CRISPYLOGICS Julienstr. 1, 90419 Nuremberg Fon +49 (0)911 517 999 82 Fax +49 (0)911 517 999 83 mailto:info@crispylogics.com http://www.crispylogics.com

2 1

[cxml-devel] [PATCH] Make pathname-to-uri handle :back/:up components in directory.
by Pierre R. Mai 07 Jun '08

07 Jun '08

Previously cxml:parse-file would cause an error in pathname-to-uri when handed a pathname with :back or :up entries in the directory component. This change ensures that a suitable base-uri is generated in those cases. --- xml/xml-parse.lisp | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/xml/xml-parse.lisp b/xml/xml-parse.lisp index eb8e338..546b60b 100644 --- a/xml/xml-parse.lisp +++ b/xml/xml-parse.lisp @@ -3030,7 +3030,9 @@ #-cxml-system::uri-is-namestring (defun pathname-to-uri (pathname) (let ((path - (append (pathname-directory pathname) + (append (mapcar #'(lambda (x) (cond ((member x '(:up :back)) "..") + (t x))) + (pathname-directory pathname)) (list (if (specific-or (pathname-type pathname)) (concatenate 'string -- 1.5.6.rc1.15.g03aab

2 1

[cxml-devel] charset-windows.patch
by Pierre R. Mai 07 Jun '08

07 Jun '08

Hello everyone, having had the unfortunate opportunity to need to parse XML files with Windows encodings, I've added created the following patch against current CVS, which adds encodings for Windows-1250,1251,1252,1253,1254,1255 and 1257 (1256 and 1258 not being in wide usage hereabouts). The patch also adds ISO-8859-13 (very similar to 1257) and the remaining official aliases from IANA for the ISO-8859-14 and ISO-8859-15 encodings for completeness. Regs, Pierre. -- Pierre R. Mai <pmai(a)pmsf.de> PMSF IT Consulting Pierre R. Mai http://www.pmsf.de/ Ludwig-Thoma-Str. 11 Schleißheimer Str. 263 87724 Ottobeuren 80809 München Tel. +49(0)8332/93669-13 +49(0)89/35061750 Fax +49(0)8332/93669-03 Germany

2 1

[cxml-devel] charset-windows.patch
by Pierre R. Mai 03 Jun '08

03 Jun '08

[ Sorry for the duplication, but it seems I accidentally signed the previous mail, which can cause problems with patch and mailman ] Hello everyone, having had the unfortunate opportunity to need to parse XML files with Windows encodings, I've added created the following patch against current CVS, which adds encodings for Windows-1250,1251,1252,1253,1254,1255 and 1257 (1256 and 1258 not being in wide usage hereabouts). The patch also adds ISO-8859-13 (very similar to 1257) and the remaining official aliases from IANA for the ISO-8859-14 and ISO-8859-15 encodings for completeness. Regs, Pierre. -- Pierre R. Mai <pmai(a)pmsf.de> PMSF IT Consulting Pierre R. Mai http://www.pmsf.de/ Ludwig-Thoma-Str. 11 Schleißheimer Str. 263 87724 Ottobeuren 80809 München Tel. +49(0)8332/93669-13 +49(0)89/35061750 Fax +49(0)8332/93669-03 Germany

1 0