cxml-devel

cxml-devel@common-lisp.net

167 discussions

[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

[cxml-devel] cxml on cmucl19c
by Kristian Elof Sørensen 12 Dec '05

12 Dec '05

Hi I downloaded cxml from cvs a few hours ago and gave it a try, but it fails to run the "Quick-Start Example" correctly: Using CMU 19c: (cmucl19a gave the same results) CL-USER> (with-open-file (s "example.xml" :direction :output) (write-string "<test a='b'><child/></test>" s)) "<test a='b'><child/></test>" CL-USER> (cxml:parse-file "example.xml" (dom:make-dom-builder)) #<DOM-IMPL::DOCUMENT {58B6E205}> CL-USER> (defparameter *example* *) *EXAMPLE* CL-USER> (dom:document-element *example*) #<DOM-IMPL::ELEMENT test {5808FCD5}> CL-USER> (dom:tag-name (dom:document-element *example*)) #(116 101 115 116) ^^^^^^^^^^^^^^^^^^ CL-USER> (dom:child-nodes (dom:document-element *example*)) #(#<DOM-IMPL::ELEMENT child {582711A5}>) CL-USER> (dom:get-attribute (dom:document-element *example*) "a") #(98) ^^^^^ CL-USER> (cxml:parse-file "example.xml" (cxml-xmls:make-xmls-builder)) (#(116 101 115 116) ((#(97) #(98))) (#(99 104 105 108 100) NIL)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Using Lispworks 4.4 strings are returned as on the webpage. Kristian

2 1

[cxml-devel] License (?)
by Edi Weitz 28 Nov '05

28 Nov '05

What exactly is the status of CXML's license? The website says it's "(L)LGPL", some files say "LLGPL", some files says "LGPL". If this isn't on purpose (but why?) maybe it would be easier to just release everything under the same license. Cheers, Edi.

2 4

[cxml-devel] cxml character handling issue?
by Adam Thorsen 14 Nov '05

14 Nov '05

I'm trying to use cl-xmpp wich uses cxml. I believe there may be an issue within cxml. The problem arises results from this call: (defvar connection (xmpp:connect :hostname "jabber.org")) This appears to be an issue only on cmucl. I'm using version 19b. Here is the backtrace: Argument Y is not a NUMBER: #\s. [Condition of type SIMPLE-TYPE-ERROR] Restarts: 0: [ABORT] Abort handling SLIME request. 1: [ABORT] Return to Top-Level. Backtrace: 0: (KERNEL:TWO-ARG-= 115 #\s) 1: (RUNES:ROD= #(115 116 114 101 97 ...) "stream") 2: (ASSOC #(115 116 114 101 97 ...) (("stream" . "http://etherx.jabber.org/streams") (#) (# . #) (# . #))$ 3: (CXML::FIND-NAMESPACE-BINDING #(115 116 114 101 97 ...)) 4: (CXML::DECODE-QNAME #(115 116 114 101 97 ...)) 5: (CXML::P/ELEMENT-NS #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (#<RUNES::XS$ 6: (CXML::P/DOCUMENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (#<RUNES::XSTR$ 7: (CXML::PARSE-XSTREAM #<RUNES::XSTREAM NIL> #<CL-XMPP::STANZA-HANDLER {58A17AA5}>) 8: (CL-XMPP::READ-STANZA #<CL-XMPP:CONNECTION to jabber.org:5222 (open) {5854FD0D}>) 9: ((METHOD CL-XMPP:RECEIVE-STANZA NIL (CL-XMPP:CONNECTION)) #<#1=unused-arg> #<#1#> #<CL-XMP

1 0

[cxml-devel] READ-TOKEN-3 bad data from CL+SSL stream?
by Erik Enge 14 Nov '05

14 Nov '05

Using CVS cl-xmpp, cl+ssl and the latest cxml release I get the following error when trying to parse xml from the ssl stream: * (defparameter *c* (xmpp:connect-tls :hostname "talk.google.com" :jid-domain-part "gmail.com")) <?xml version='1.0' ?><stream:stream to='gmail.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'><?xml version="1.0" encoding="UTF-8"?version="1.0" encoding="UTF-8"><stream:stream from="gmail.com" id="8D040D109BF0BC76" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" UNHANDLED: #<XML-ELEMENT STREAM:STREAM (3:0:0) {B6DA4D1}> ><stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>X-GOOGLE-TOKEN</mechanism></mechanisms></stream:features UNHANDLED: #<XML-ELEMENT STREAM:FEATURES (0:2:0) {B6E5979}> <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>><proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/ UNHANDLED: #<XML-ELEMENT PROCEED (0:0:0) {B6ECC41}> <?xml version='1.0' ?><stream:stream to='gmail.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'> *C* * (xmpp:auth *c* "username" "password" "clxmpp" :sasl-plain) <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='PLAIN'/>> debugger invoked on a SIMPLE-ERROR: Unexpected character #\Etb. Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level. (CXML::READ-TOKEN-3 #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (#<RUNES::XSTREAM NIL>))) 0] :backtrace 0: (CXML::READ-TOKEN-3 #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (#<RUNES::XSTREAM NIL>))) 1: (CXML::PEEK-TOKEN #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (#<RUNES::XSTREAM NIL>))) 2: (CXML::P/DOCUMENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (#<RUNES::XSTREAM NIL>)) #<CL-XMPP::STANZA-HANDLER {B799909}> :VALIDATE NIL :DTD NIL :ROOT NIL :ENTITY-RESOLVER NIL :DISALLOW-INTERNAL-SUBSET NIL) 3: (CXML::PARSE-XSTREAM #<RUNES::XSTREAM NIL> #<CL-XMPP::STANZA-HANDLER {B799909}>) 4: (CL-XMPP::READ-STANZA #<CL-XMPP:CONNECTION to talk.google.com:5222 (open) {B75D929}>) 5: ((SB-PCL::FAST-METHOD CL-XMPP:RECEIVE-STANZA (CL-XMPP:CONNECTION)) #<unavailable argument> #<unavailable argument> #<CL-XMPP:CONNECTION to talk.google.com:5222 (open) {B75D929}> NIL) 6: ((SB-PCL::FAST-METHOD CL-XMPP::HANDLE-CHALLENGE-RESPONSE (CL-XMPP:CONNECTION T T T)) #<unavailable argument> #<unavailable argument> #<CL-XMPP:CONNECTION to talk.google.com:5222 (open) {B75D929}> "username" "password" "PLAIN") 7: (SB-INT:EVAL-IN-LEXENV (CL-XMPP:AUTH *C* "username" "password" "clxmpp" :SASL-PLAIN) #<NULL-LEXENV>) 8: (INTERACTIVE-EVAL (CL-XMPP:AUTH *C* "username" "password" "clxmpp" :SASL-PLAIN)) 9: (SB-IMPL::REPL-FUN NIL) 10: ((LAMBDA ())) 11: ((LAMBDA ())) 12: (SB-IMPL::%WITH-REBOUND-IO-SYNTAX #<CLOSURE (LAMBDA #) {ACDA1FD}>) 13: (SB-IMPL::TOPLEVEL-REPL NIL) 14: (SB-IMPL::TOPLEVEL-INIT) 15: ((LABELS SB-IMPL::RESTART-LISP)) 0] Perhaps I'm missing something and have missed a step in how to convert my stream to an SSL stream. Here's the code: (setf (server-stream connection) (cl+ssl:make-ssl-client-stream (server-stream connection)) Then I proceed to write and read to the stream as if it were an (unsigned-byte 8) stream just like the original one. Is this correct? What's that Unknown character #\Etb about? I would've expected at this point to get <?xml version='1.0' ?> from the server. Any pointers would be helpful. Thanks, Erik.

1 0

[cxml-devel] Re: Bug and patch for CXML's cxml.asd
by David Lichteblau 13 May '05

13 May '05

Quoting Dave Lambert (d.j.lambert(a)gmail.com): > I just found a small bug in the cxml.asd file. The definition for > :xml includes two declarations of the "characters" file. The diff is: [...] Thanks, applied. David

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cxml-devel