cxml-devel January 2006

cxml-devel@common-lisp.net

4 participants
6 discussions

[cxml-devel] flush-ystream on character-stream-yestream
by Nathan Bird 24 Jan '06

24 Jan '06

I was having a problem with serializing to a character stream (rather than string or octets) on SBCL 0.9.7. CL-USER> (let* ((dom (cxml-dom:create-document)) (string (with-output-to-string (stream) (dom:map-document (cxml:make-character-stream-sink stream :indentation 4 :canonical nil) dom )))) (values string (length string))) "<?xml version=\"1.0\" encoding=\"UTF-8\"?>^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@ .... (I've actually typed these in since I can't paste them) ..... ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@............." 1024 It was looking an awfully lot like it was trying to write out buffer that wasn't filled. Tracked it down to (defmethod flush-ystream ((ystream character-stream-ystream)) (write-string (ystream-in-buffer ystream) (ystream-target-stream ystream) ;;this end argument had been missing. :end (ystream-in-ptr ystream)) (setf (ystream-in-ptr ystream) 0)) Patch attached. Nathan Bird BTW, I've been playing around with using CXML to generate XUL, since it mixes with HTML and namespaces matter and all that jazz. As an interesting comparison I tried generating and serializing out through UnCommon Web a big html table with a lot of dynamic generated strings in it. It looks like doing it with CXML is about 2.5 times faster than doing the equivalent with UCW's own tool-- yaclml. Sweet!

2 3

[cxml-devel] Indentation patch.
by Nathan Bird 23 Jan '06

23 Jan '06

I've been working off of CVS head and had a problem with serializing nicely formatted indented xml. I am using sbcl 0.9.7 that has Unicode support rune-is-character is in the *features*. I was running into an error along the lines of "The value 10 is not of type CHARACTER." and "The value 32 is not of type CHARACTER.". I tracked it down a bit and found in unparse.lisp a couple of lines (%write-rune 10 sink) whereas most of the occurrences in the file were more like (%write-rune #/U+000A sink) Changing these seems to fix it. I take it you've changed the interface to this function at some point and just didn't get all the references? Patch attached. Nathan

2 1

[cxml-devel] Escaped characters
by Adam Thorsen 23 Jan '06

23 Jan '06

I am running into an issue in which any time cxml encounters an escaped character such as ", &, etc. while parsing a socket stream, it throws an error (pasted below). I have tried parsing xml with such characters using cxml:parse-file and have not encountered any issues. I've taken a look at the data going across the socket using tcpdump and it appears to be transmitted correctly. Here is an example of the type of element that causes the problem: <message type="groupchat" id="ac0ca" to="20(a)conference.shiva.guruza.com" > <body>Hello"</body> </message> I'm using the cxml distributed in the cxml-2006-01-05 tar file with sbcl 0.9.8 with unicode support. The value NIL is not of type CXML::STREAM-NAME. [Condition of type TYPE-ERROR] Restarts: 0: [ABORT] Abort handling SLIME request. 1: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" {A197959}>) Backtrace: 0: ((LAMBDA (CXML::X)) #<RUNES:XSTREAM NIL>) 1: (SB-KERNEL:%FIND-POSITION-IF #<CLOSURE (LAMBDA (CXML::X)) {950CD3D}> (:STOP #<RUNES:XSTREAM NIL>) NIL 0 NIL #<FUNCTION IDENTITY>) 2: (CXML::ZSTREAM-PUSH #<RUNES:XSTREAM [apos :GENERAL NIL]> #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP #<RUNES:XSTREAM NIL>))) 3: ((LAMBDA (CXML::NEW-XSTREAM)) #<RUNES:XSTREAM [apos :GENERAL NIL]>) 4: (CXML::CALL-WITH-ENTITY-EXPANSION-AS-STREAM #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP #<RUNES:XSTREAM NIL>)) #<CLOSURE (LAMBDA (CXML::NEW-XSTREAM)) {950CCB5}> "apos" :GENERAL NIL) 5: (CXML::P/CONTENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP #<RUNES:XSTREAM NIL>))) 6: (CXML::P/ELEMENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP #<RUNES:XSTREAM NIL>))) 7: (CXML::P/CONTENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP #<RUNES:XSTREAM NIL>))) 8: (CXML::P/ELEMENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP #<RUNES:XSTREAM NIL>))) 9: (CXML::P/DOCUMENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP #<RUNES:XSTREAM NIL>)) #<CL-XMPP::STANZA-HANDLER {94D3E51}> :VALIDATE NIL :DTD NIL :ROOT NIL :ENTITY-RESOLVER NIL :DISALLOW-INTERNAL-SUBSET NIL :RECODE T) 10: (CXML::PARSE-XSTREAM #<RUNES:XSTREAM NIL> #<CL-XMPP::STANZA-HANDLER {94D3E51}>) 11: (CL-XMPP::READ-STANZA #<CL-XMPP:CONNECTION to shiva.guruza.com:5222 (open) {A9AE611}>) 12: ((SB-PCL::FAST-METHOD CL-XMPP:RECEIVE-STANZA (CL-XMPP:CONNECTION)) #<unavailable argument> #<unavailable argument> #<CL-XMPP:CONNECTION to shiva.guruza.com:5222 (open) {A9AE611}> NIL) 13: (SB-INT:EVAL-IN-LEXENV (CL-XMPP:RECEIVE-STANZA (GET-CONNECTION 20)) #<NULL-LEXENV>)

2 1

[cxml-devel] Catalog problems
by Adam C. Emerson 09 Jan '06

09 Jan '06

I've been trying to use the CXML catalog feature, but so far I haven't had any success. Is there something that I am doing that is obviously wrong? Things such as: (setf cxml:*catalog* (cxml:make-catalog)) (cxml:resolve-extid "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" cxml:*catalog*) Return NIL, when using the Debian /etc/xml/catalog I've checked and it's in there under a few lines of delegates, so I tried making my own: <?xml version='1.0'?> <!DOCTYPE catalog PUBLIC "-//GlobalTransCorp//DTD XML Catalogs V1.0-Based Extension V1.0//EN" "http://globaltranscorp.org/oasis/catalog/xml/tr9401.dtd"> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog" xmlns:soc="urn:oasis:names:tc:entity:xmlns:tr9401:catalog" xmlns:unk="urn:oasis:names:tc:entity:xmlns:unknown" > <group prefer="public"> <public publicId="-//W3C//DTD XHTML 1.1//EN" uri="/usr/share/xml/xhtml/schema/dtd/1.1/xhtml11-flat.dtd"/> <soc:dtddecl publicId="-//W3C//DTD XHTML 1.1//EN" uri="/usr/share/xml/xhtml/schema/dtd/1.1/xml1.dcl"/> </group> </catalog> Passing that file to cxml:make-catalog and doing the same thing, but resolve-extid still comes back with NIL. Thank you very much

2 3

[cxml-devel] building cxml-2006-01-05.tgz
by Adam Thorsen 08 Jan '06

08 Jan '06

I am attempting to use cxml with sbcl 0.9.6 with unicode support on linux. When I attempt to load cxml using the latest release, mentioned in the subject, I get the following error: debugger invoked on a SB-PCL::FIND-METHOD-LENGTH-MISMATCH in thread #<THREAD "initial thread" {90033E9}>: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-READ-SEQUENCE (2)> takes 2 required arguments; was asked to find a method with specializers (#<STANDARD-CLASS OCTET-INPUT-STREAM> #<BUILT-IN-CLASS T> #<BUILT-IN-CLASS T> #<BUILT-IN-CLASS T>) Can someone tell me why this won't load?

2 1

[cxml-devel] upcoming release
by David Lichteblau 05 Jan '06

05 Jan '06

Hi, it is time for a new cxml release. I am planning to create the release tarball in a week or so. It would be great if anyone using cxml could do some testing until then. Changes: * Implemented DOM 2 Core. (I.e., namespace support.) * Error handling overhaul. All wellformedness violations should now be signalled as instances of CXML:WELL-FORMEDNESS-VIOLATION. We also try to print line numbers. * On Lisps without unicode support, there is now an (alternative) DOM implementation that uses UTF-8-encoded lisp strings instead of runes and rods. * Some minor new features (whitespace normalization; parse-string has been exported under the new name cxml:parse-rod, ...) Incompatible API changes: * On Lisps without unicode support, the parser recodes to UTF-8 by default now. (Anyone using recoders manually can suppress the default recoding using :recode nil.) * dom:make-dom-builder has been replaced with two separate functions, rune-dom:make-dom-builder and utf8-dom:make-dom-builder. There is a nickname cxml-dom on the former package if the Lisp supports Unicode or on the latter otherwise. (The utf8-dom package is not defined if the Lisp supports Unicode.) * The unparse-document-* functions have been removed in favour of map-document. * Sink functions have changed. Beware that make-character-stream-sink happens to have the same name as an older functions but works differently. Thanks, David

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cxml-devel January 2006