tclxml-users — Discussion on using the TclXML package

[Tclxml-users] 3.0 schema compile failures

[Bill S. <bsc...@ci...>]

Hey folks,

 I read that there are limits to the 3.0 schema compile/validation
capabilities, but I can't seem to get even the simplest schema to
work. For example:

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
	<xs:element name="foo">
		<xs:complexType>
			<xs:sequence>
				<xs:element name="bar"
type="xs:string"/>
				<xs:element name="junk" type="xs:int"
minOccurs="0"/>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>

 Does anyone have an example schema that works, or a list of the known
restrictions/limitations?

Thanks,

-Bill

Re: [Tclxml-users] itcl/tk-like calling syntax for TclDom

[<dg...@mo...>]

Hello,

I recently used Snit to make this working for the tcl-only TclDOM. This can be
now used also as a drop in replacement for tdom if tdom is not
available.

See the wiki page for more infos at:

http://mini.net/tcl/13473

Feel free to comment/improve. 
Please not that not all of tdom-syntax is
supported yet.

regards,
Detlef

-- 
Dr. Detlef Groth
Max-Planck-Institut
fuer Molekulare Genetik
Ihnestr. 63/73
D-14195 Berlin
Tel.: + 49 30 - 8413 1235

[Tclxml-users] WSDL Generation for TclSOAP

[Byron W. <by...@ly...>]

I've wrote a package that allows wsdl generation from Tcl SOAP. I hope someone 
finds this usefull.
http://www.geocities.com/blackboy9692002/tclsoap/

I based this off the 2.6 version of TCLDOM/TCLXML, (though it should work with 
3.x, not tested)

Thanks for  a great package! 

-Byron Whitlock 

Re: [Tclxml-users] API change?

[<da...@de...>]

Steve Ball <Ste...@zv...> writes:

> First I've heard of this... TclXML v3.0 is a major version change,
> but the API has not changed *that* much.

> TclXML v3.X passes all of its regression tests. including the
> parsing API and parsing empty element syntax.  I will investigate
> further, back a small sample XML source document and Tcl script
> would be helpful.

Here's a script that Massimo, the guy who noticed this, sent me.

-- 
David N. Welton
Personal:                   http://www.dedasys.com/davidw/
Apache Tcl:                 http://tcl.apache.org/
Free Software:              http://www.dedasys.com/freesoftware/
Linux Incompatibility List: http://www.leenooks.com/

----
package require xml

proc elemStartCmd {elem_type attr_list args} {
    puts [list >>>>>>>>>> open $elem_type ($attr_list $args)]
}

proc elemEndCmd {elem_type args} {
    puts [list >>>>>>>>>> close $elem_type ($args)]
}

proc descriptiveData {cdata} {
    puts [list cdata: $cdata]
}

set theParser [::xml::parser				    \
		    -elementendcommand	    elemEndCmd	    \
		    -elementstartcommand    elemStartCmd    \
		    -characterdatacommand   descriptiveData ]

set	xmldata ""
append	xmldata "<toplevel> Document root\n"
append  xmldata "   <livello1> Tag for generic element </livello1>\n"
append	xmldata	"   <livello1 attr1_1=\"v1\" attr1_2=\"v2\"> Nuovo Elemento contenente altri Elementi\n"
append	xmldata	"        <livello2 attr2_1=\"v1\" attr2_2=\"v2\"/>\n"
append	xmldata	"        <livello2 attr2_1=\"v3\" attr2_2=\"v4\"/>\n"
append  xmldata	"        <livello2> Tag chiuso in modo \"canonico\" </livello2>\n"
append	xmldata "   </livello1>\n"
append	xmldata "</toplevel>\n"

$theParser parse $xmldata

Re: [Tclxml-users] API change?

[Steve B. <Ste...@zv...>]

First I've heard of this... TclXML v3.0 is a major version change, but 
the API has not changed *that* much.

TclXML v3.X passes all of its regression tests. including the parsing 
API and parsing empty element syntax.  I will investigate further, back 
a small sample XML source document and Tcl script would be helpful.

Cheers,
Steve Ball

On 14/12/2004, at 8:41 PM, David N. Welton wrote:

>
> [ Please CC replies to me. ]
>
> Hi,
>
> I recently packaged up a new version of tclxml for Debian, and have
> received a bug report:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285480
>
> Can you comment on this?
>
> Thanks,
> -- 
> David N. Welton
> Personal:                   http://www.dedasys.com/davidw/
> Apache Tcl:                 http://tcl.apache.org/
> Free Software:              http://www.dedasys.com/freesoftware/
> Linux Incompatibility List: http://www.leenooks.com/
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Tclxml-users mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tclxml-users
>
>

---

Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

[Tclxml-users] API change?

[<da...@de...>]

[ Please CC replies to me. ]

Hi,

I recently packaged up a new version of tclxml for Debian, and have
received a bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285480

Can you comment on this?

Thanks,
-- 
David N. Welton
Personal:                   http://www.dedasys.com/davidw/
Apache Tcl:                 http://tcl.apache.org/
Free Software:              http://www.dedasys.com/freesoftware/
Linux Incompatibility List: http://www.leenooks.com/

Re: [Tclxml-users] wrong display of not nested,emtpy divs

[Steve B. <Ste...@zv...>]

Firstly, in your script you reused the "div" variable, thus creating 
two <div> elements but the variable refers to the second instance when 
the text is added.  That's why the first <div> is an empty element.

Secondly, the use of empty element syntax when the method is set to 
"html" is a bug; please submit a bug report on SourceForge.

Cheers,
Steve Ball

On 24/11/2004, at 11:14 PM, Detlef Groth wrote:

>
> Hello,
>
> for a web application I build a dom-tree in memory and depending on
> user input I hide or display certain parts of the dom-tree.
>
> Sample session to create the document:
> (tclkit) 2 % package require xml::tcl
> 3.0
> (tclkit) 3 %   set doc [dom::DOMImplementation create]
> invalid command name "dom::DOMImplementation"
> (tclkit) 4 % package require dom
> 3.0
> (tclkit) 5 %   set doc [dom::DOMImplementation create]
> ::dom::tcl::document1::Document
> (tclkit) 6 %    set top [dom::document createElement $doc html]
> ::dom::tcl::document1::node2
> (tclkit) 7 %     set head [dom::document createElement $top head]
> ::dom::tcl::document1::node6
> (tclkit) 8 %     set title [dom::document createElement $head title]
> ::dom::tcl::document1::node10
> (tclkit) 9 %     set titleText [dom::document createTextNode $title 
> "MPIMG Berlin - Mouse Database"]
> ::dom::tcl::document1::node14
> (tclkit) 10 %    set body [dom::document createElement $top body]
> ::dom::tcl::document1::node18
> (tclkit) 11 %     set div [dom::document createElement $body div]
> ::dom::tcl::document1::node22
> (tclkit) 12 % dom::element setAttribute $div style display:none;
> display:none
> (tclkit) 13 %     set div [dom::document createElement $body div]
> ::dom::tcl::document1::node27
> (tclkit) 14 % [dom::document createTextNode $div Test]
> wrong # args: should be "::dom::tcl::document1::node31 method args"
> (tclkit) 15 % dom::document createTextNode $div Test
> ::dom::tcl::document1::node35
> (tclkit) 16 % $doc serialize -html
> unknown method "serialize"
> (tclkit) 17 % dom::serialize $doc -method "html"
> <?xml version='1.0'?>
> <!DOCTYPE html>
> <html><head><title>MPIMG Berlin - Mouse 
> Database</title></head><body><div 
> style="display:none"/><div>TestTest</div></body></html>
> (tclkit) 18 % dom::serialize $doc -method "html" -indent
> list must have an even number of elements
> (tclkit) 19 % dom::serialize $doc -method "html" -indent 2
> <?xml version='1.0'?>
> <!DOCTYPE html>
>
>     <html>
>       <head>
> 	<title>MPIMG Berlin - Mouse Database</title>
>       </head>
>       <body>
> 	<div style="display:none"/>
> 	<div>TestTest</div>
>       </body>
>     </html>
>
>
>
> both outputs did not render the text although the TestTest-text is not
> a parent of the display:none-div.
>
> if we change the html-code manually to
>
>   <html>
>       <head>
> 	<title>MPIMG Berlin - Mouse Database</title>
>       </head>
>       <body>
> 	<div style="display:none"></div>
> 	<div>TestTest</div>
>       </body>
>     </html>
>
> which should be the same than it renders right. So my adivise is to
> change the following:
> $ diff /d/tcl-lib/tcldom3.0/dom.tcl 
> ~/cvs/tclhttpd/customlib/tcldom3.0/dom.tcl
> ... some other stuff
>
> <
> <       append result />$newline
> ---
>>         # dgroth fixes bad browser behaviour with <div 
>> style='display:none'/> tags
>>       append result "></$nsPrefix$node(node:localName)>$newline"
>
> Or at least allow a option with serialize like:
>
> ::dom::DOMImplementation serialize $doc -emptytags false
>
> I think with tdom this is the default because I did not observe this
> missbehaviour (of modern browsers) until now.
>
> regards,
> Detlef
>
> -- 
> Dr. Detlef Groth
> Max-Planck-Institut
> fuer Molekulare Genetik
> Ihnestr. 63/73
> D-14195 Berlin
> Tel.: + 49 30 - 8413 1235
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Tclxml-users mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tclxml-users
>
>

---

Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

[Tclxml-users] wrong display of not nested,emtpy divs

[<dg...@mo...>]

Hello,

for a web application I build a dom-tree in memory and depending on
user input I hide or display certain parts of the dom-tree.

Sample session to create the document:
(tclkit) 2 % package require xml::tcl
3.0
(tclkit) 3 %   set doc [dom::DOMImplementation create]
invalid command name "dom::DOMImplementation"
(tclkit) 4 % package require dom
3.0
(tclkit) 5 %   set doc [dom::DOMImplementation create]
::dom::tcl::document1::Document
(tclkit) 6 %    set top [dom::document createElement $doc html]
::dom::tcl::document1::node2
(tclkit) 7 %     set head [dom::document createElement $top head]
::dom::tcl::document1::node6
(tclkit) 8 %     set title [dom::document createElement $head title]
::dom::tcl::document1::node10
(tclkit) 9 %     set titleText [dom::document createTextNode $title "MPIMG Berlin - Mouse Database"]
::dom::tcl::document1::node14
(tclkit) 10 %    set body [dom::document createElement $top body]
::dom::tcl::document1::node18
(tclkit) 11 %     set div [dom::document createElement $body div]
::dom::tcl::document1::node22
(tclkit) 12 % dom::element setAttribute $div style display:none;
display:none
(tclkit) 13 %     set div [dom::document createElement $body div]
::dom::tcl::document1::node27
(tclkit) 14 % [dom::document createTextNode $div Test]
wrong # args: should be "::dom::tcl::document1::node31 method args"
(tclkit) 15 % dom::document createTextNode $div Test
::dom::tcl::document1::node35
(tclkit) 16 % $doc serialize -html
unknown method "serialize"
(tclkit) 17 % dom::serialize $doc -method "html"
<?xml version='1.0'?>
<!DOCTYPE html>
<html><head><title>MPIMG Berlin - Mouse Database</title></head><body><div style="display:none"/><div>TestTest</div></body></html>
(tclkit) 18 % dom::serialize $doc -method "html" -indent
list must have an even number of elements
(tclkit) 19 % dom::serialize $doc -method "html" -indent 2
<?xml version='1.0'?>
<!DOCTYPE html>

    <html>
      <head>
	<title>MPIMG Berlin - Mouse Database</title>
      </head>
      <body>
	<div style="display:none"/>
	<div>TestTest</div>
      </body>
    </html>



both outputs did not render the text although the TestTest-text is not
a parent of the display:none-div.

if we change the html-code manually to 

  <html>
      <head>
	<title>MPIMG Berlin - Mouse Database</title>
      </head>
      <body>
	<div style="display:none"></div>
	<div>TestTest</div>
      </body>
    </html>

which should be the same than it renders right. So my adivise is to
change the following:
$ diff /d/tcl-lib/tcldom3.0/dom.tcl ~/cvs/tclhttpd/customlib/tcldom3.0/dom.tcl
... some other stuff

< 
<       append result />$newline
---
>         # dgroth fixes bad browser behaviour with <div style='display:none'/> tags
>       append result "></$nsPrefix$node(node:localName)>$newline"

Or at least allow a option with serialize like:

::dom::DOMImplementation serialize $doc -emptytags false

I think with tdom this is the default because I did not observe this
missbehaviour (of modern browsers) until now.

regards,
Detlef

-- 
Dr. Detlef Groth
Max-Planck-Institut
fuer Molekulare Genetik
Ihnestr. 63/73
D-14195 Berlin
Tel.: + 49 30 - 8413 1235

Re: [Tclxml-users] help: beginner

[Steve B. <Ste...@zv...>]

Cedric,

The first thing you must realise is that your XML document has two=20
components:

1. An element, named "Hello", and
2. character data, with the value "145590".

You use different callbacks to get those parts.  You've already=20
discovered "-elementstartcommand" that tells you when an element=20
starts.  This callback gives you the name of the element ("Hello").

The other call back that you need is "-characterdatacommand".  This=20
callback gives you the value of the character data ("145590").

This modification to your script will give you both data items:

proc tutu {data} {
   global f
   $f.valueb configure -text $data
}

set parser [::xml::parser -elementstartcommand toto \
-characterdatacommand tutu]

$parser parse [read $filein]

Another callback you may wish to know about is the=20
"-elementendcommand".  This callback tells you when an element=20
finishes, so you can tell which data belongs to what element.

You may wish to review some of the example scripts included with the=20
TclXML distribution for more detail on how these callbacks work.

In review, remember that with XML:

A) Elements have a name, but they have no value,
B) Character data (text) has a value, but no name,
C) Attributes have a name and a value.

This also applies to the DOM and therefore TclDOM.

HTHs,
Steve Ball

On 20/11/2004, at 4:08 AM, Cedric Marchessoux wrote:

> I am a user of tcl/tk and vtk. I want to use tclxml in to parse xml=20
> files
> and extract values of tags, I have an XML file like this:
>
> test.xml:
>
> <?xml version=3D'1.0'?>
>  <Hello>145590</Hello>
>
> What I have to do if I want to parse this document and the tag Hello=20=

> is in
> th xml, I want to get the value ?
>
> proc toto {Hello tata} {
>  global amax f
>  set amax $tata
>  $f.labela configure -text "a=3D$amax"
>  $f.valuea configure  -textvariable $amax
>
> }
>
> set filein [open "./test.xml" r]
>
> set parser [::xml::parser -elementstartcommand toto]
>
> $parser parse [read $filein]
>
> Thank you in advance,
>
> C=E9dric,
>
> Dr, Phd,
> Marie Curie Fellow, post doctorate
> VICTOR project
> Agfa Gevaert, RDM/Physics & Analytics
> + 32 (0) 3 444 3077,
> ced...@ag...
> http://www.marchessoux.com
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> Tclxml-users mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tclxml-users
>
>

---

Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

[Tclxml-users] help: beginner

[Cedric M. <ced...@ag...>]

Hi,

I am a user of tcl/tk and vtk. I want to use tclxml in to parse xml fil=
es
and extract values of tags, I have an XML file like this:

test.xml:

<?xml version=3D'1.0'?>
 <Hello>145590</Hello>

What I have to do if I want to parse this document and the tag Hello is=
 in
th xml, I want to get the value ?

proc toto {Hello tata} {
 global amax f
 set amax $tata
 $f.labela configure -text "a=3D$amax"
 $f.valuea configure  -textvariable $amax

}

set filein [open "./test.xml" r]

set parser [::xml::parser -elementstartcommand toto]

$parser parse [read $filein]

Thank you in advance,

C=E9dric,

Dr, Phd,
Marie Curie Fellow, post doctorate
VICTOR project
Agfa Gevaert, RDM/Physics & Analytics
+ 32 (0) 3 444 3077,
ced...@ag...
http://www.marchessoux.com=

[Tclxml-users] 11'th Annual Tcl/Tk Conference Audio Casting

[<aku...@sh...>]

11'th Annual Tcl/Tk Conference

October 11 - 15, 2004           -- Running --
New Orleans, Louisiana, USA
Email Contact tc...@tc...

At this year's Tcl conference we are _experimentally_ casting an
ogg/vorbis based audio stream from the talks in the Technical
Sessions. Their detailed schedule can be found at

        http://www.tcl.tk/community/tcl2004/schedule.html

The salient technical details required to receive the stream can be
found on the Tcler's Wiki, on page

        http://wiki.tcl.tk/12643
i.e.    http://wiki.tcl.tk/Audio%20Webcast%20from%20the%20Tcl%20Conference


All listeners are invited to log in to the Tcl'ers Chat [1] as well,
for coordination and for asking questions to the speakers at the
conference. There will be people in the conference room who are logged
in to the chat and can proxy between remote listeners and the speaker.

[1]     Wiki pages to quick start users of the Tcl'ers Chat:

        http://wiki.tcl.tk/1178
        http://wiki.tcl.tk/2949 (just refers to 1178)

[Tclxml-users] Re: Tclxml 3.0 problems

[Larry W. V. <lv...@ca...>]

From: dg...@mo... (Detlef Groth)

> Have you been able to compile TclDomPro on your Solaris ?

I guess I'm still pretty confused about all the various pieces of
xml related extensions for Tcl.  I thought TclDomPro was one of the
pieces no longer used.

Anyways, when I to do the autoconf for TclDomPro I get the error:
/projects/gnu/sparc-sun-solaris2.8/bin/autoconf: /projects/gnu/sparc-sun-solaris2.8/bin/gautom4te: not found

I will have to track that down and fix it.




> I had no problems compiling it on an old OSF1-machine. However I am
> using the tcl-only version because I just need to build small docs for 

> What happen with the TCL-only solution. Is it to slow for your efforts
> or do you need TclXSLT? Then you could use tDom which can also
> handle this.

I was able to get the various parts of tclxml/tcldom/etc. 
version 2.6 to build and so that is what I've been using.
My problem comes when I try the 3.0 code.


-- 
Tcl - The glue of a new generation.  <URL: http://wiki.tcl.tk/ >
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

[Tclxml-users] RE: Tclxml 3.0 problems

[<dg...@mo...>]

Hello Larry,

Have you been able to compile TclDomPro on your Solaris ?
I had no problems compiling it on an old OSF1-machine. However I am
using the tcl-only version because I just need to build small docs for 

What happen with the TCL-only solution. Is it to slow for your efforts
or do you need TclXSLT? Then you could use tDom which can also
handle this.

regards,
Detlef


>
>
>I've seen several problem reports recently where the
>reply was "are you using tclxml 3.0".  However, as
>I explained in my messages earlier, this is difficult to
>do on Solaris - I've not yet found a way to build tclxml
>so that it statically links in the libxml, and the libxml
>that 3.0 requires is newer, and conflicts, with the libxml
>that comes with the operating system.
>
>Has anyone successfully gotten tclxml 3.0 to work on
>sparc solaris 8?
>-- 
>Tcl - The glue of a new generation.  <URL: http://wiki.tcl.tk/ >
>Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
>Even if explicitly stated to the contrary, nothing in this posting should 
>be construed as representing my employer's opinions.
>-><-
>
>

-- 
Dr. Detlef Groth
Max-Planck-Institut
fuer Molekulare Genetik
Ihnestr. 63/73
D-14195 Berlin
Tel.: + 49 30 - 8413 1235

[Tclxml-users] Tclxml 3.0 problems

[Larry W. V. <lv...@ca...>]

I've seen several problem reports recently where the
reply was "are you using tclxml 3.0".  However, as
I explained in my messages earlier, this is difficult to
do on Solaris - I've not yet found a way to build tclxml
so that it statically links in the libxml, and the libxml
that 3.0 requires is newer, and conflicts, with the libxml
that comes with the operating system.

Has anyone successfully gotten tclxml 3.0 to work on
sparc solaris 8?
-- 
Tcl - The glue of a new generation.  <URL: http://wiki.tcl.tk/ >
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

Re: [Tclxml-users] itcl/tk-like calling syntax for TclDom

[<dg...@mo...>]

Hello, Ok I modified the the file dom.tcl inside TclDom3.0 in order to (get|set|remove)Attributes:

Here is the diff:
$ diff /d/home/dgroth/cvs/tclhttpd/customlib/tcldom3.0/dom.tcl /d/tcl-lib/tcldo
m3.0/dom.tcl
1211,1222d1210
<         *Attribute {
<             switch $node(node:nodeType) {
<                 textNode {}
<                 default {
<                     if {[llength $args] == 1} {
<                         set result [dom::element $method $token [lindex $args
0]]
<                     } else {
<                         set result [dom::element $method $token [lindex $args
0] [lindex $args 1]]
<                     }
<                 }
<             }
<         }

Might add something for (get|set|remove)AttributeNS too.

Now the following works for TclDom/tcl:

% lappend auto_path d:/home/dgroth/cvs/tclhttpd/customlib
D:/tcl-programme/tclkit/tclkit8.4.7-mingw.exe/lib/tcl8.4 D:/tcl-programme/tclkit/tclkit8.4.7-mingw.exe/lib D:/tcl-programme/tclkit/tclkit8.4.7-mingw.exe/lib/tk8.4 d:/home/dgroth/cvs/tclhttpd/customlib
(tclkit) 2 % package require dom	
3.0
(tclkit) 3 % set doc [dom::DOMImplementation create]
::dom::tcl::document1::Document
(tclkit) 4 % set top [$doc createElement html]
::dom::tcl::document1::node2
(tclkit) 5 % set head [$doc createElement head]
::dom::tcl::document1::node6
(tclkit) 6 % $top appendChild $head
::dom::tcl::document1::node6
(tclkit) 7 % set title [$doc createElement title]
::dom::tcl::document1::node13
(tclkit) 8 % $head appendChild $title
::dom::tcl::document1::node13
(tclkit) 9 % $title appendChild [$doc createTextNode "MPIMG Berlin - Mouse Database"]
::dom::tcl::document1::node20
(tclkit) 10 % set body [$doc createElement body]
::dom::tcl::document1::node30
(tclkit) 11 % $top appendChild $body
::dom::tcl::document1::node30
(tclkit) 12 % $body setAttribute bgcolor black
black
(tclkit) 13 % $body getAttribute bgcolor
black
(tclkit) 14 % dom::serialize $doc
<?xml version='1.0'?>
<!DOCTYPE html>
<html><head><title>MPIMG Berlin - Mouse Database</title></head><body bgcolor="black"/></html>

Looks good.

Should I add this to the feature requests?

regards,
Detlef



>
>On 15/09/2004, at 12:37 AM, Detlef Groth wrote:
>
>> I like the itcl/tk- and Tdom-like calling conventions for tdom:
>
>TclDOM version 3.0 has introduced that style of API, but not uniformly 
>throughout the package (yet).
>
>At the time that I was implementing this feature I had an issue with 
>overloading the document/node commands with methods for multiple node 
>classes.  For example, an element node is both a Node and an Element 
>class object, so should have the methods for both the ::dom::node and 
>::dom::element commands.  However, a TextNode or a Document node will 
>have a different set a methods.
>
>> (tclkit) 82 % set doc [dom::DOMImplementation create]
>> ::dom::tcl::document7::Document
>> (tclkit) 83 % set top [dom::document createElement $doc html]
>> ::dom::tcl::document7::node2
>> (tclkit) 84 % set title [$doc createElement title]
>> ::dom::tcl::document7::node6
>> (tclkit) 85 % $top appendChild $title
>> ::dom::tcl::document7::node6
>> (tclkit) 86 % set body [$doc createElement body]
>> ::dom::tcl::document7::node13
>> (tclkit) 87 % $top appendChild $body
>> ::dom::tcl::document7::node13
>> (tclkit) 88 % $body setAttribute bgcolor black
>> unknown method "setAttribute"
>>
>> This does not work, however this:
>>
>> (tclkit) 90 % dom::element setAttribute $body bgcolor black
>> black
>
>Yes, that exactly the issue raised above.  "setAttribute" is a method 
>of the ::dom::element command.  You'd like to be able to do:
>
>$body setAttribute bgcolor black
>
>What happens if you do:
>
>$doc setAttribute bgcolor black
>
>The latter should probably throw an exception.
>
>Making the former work would mean either defining the node command as a 
>separate function and implementing every method from every node class 
>command (for both Tcl and libxml2), or modifying the node command to 
>call the class-specific function if the method is not defined 
>(actually, the latter would be the best approach).
>
>> which is for me a little bit awkward, and I always forget to add the
>> nodename after the (get|set)Attribute-command. I am used to javascript
>> where we say something like:
>>
>> var input = window.document.createElement("input");
>> input.setAttribute("name", "inputvalue");
>
>Having to remember to add the node token does make the API a bit 
>awkward, I agree.
>
>> It should be not to difficult to write some simple wrapper classes
>> with Snit or something similar. But using snit may slow down the code. 
>> Did
>> anyone have a better suggestion?
>
>Do it in the TclDOM package itself; please submit a feature request to 
>SF.
>
>At the moment I'm flat-out with other (paid-for) projects so I won't be 
>able to do anything about it in the short-term.  However, maybe someone 
>else will step up to the plate and give it a go.
>
>>  As a side effect the same code might run with tdom also.
>
>Ah... that's a sore point.  You go talk to the tDOM people about 
>compatibility :-(
>
>Cheers,
>Steve Ball
>
>---
>
>Steve Ball            |   XSLT Standard Library   | Training & Seminars
>Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
>http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
>Ste...@zv...  +---------------------------+---------------------
>Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099
>

-- 
Dr. Detlef Groth
Max-Planck-Institut
fuer Molekulare Genetik
Ihnestr. 63/73
D-14195 Berlin
Tel.: + 49 30 - 8413 1235

Re: [Tclxml-users] itcl/tk-like calling syntax for TclDom

[Steve B. <Ste...@zv...>]

On 15/09/2004, at 12:37 AM, Detlef Groth wrote:

> I like the itcl/tk- and Tdom-like calling conventions for tdom:

TclDOM version 3.0 has introduced that style of API, but not uniformly 
throughout the package (yet).

At the time that I was implementing this feature I had an issue with 
overloading the document/node commands with methods for multiple node 
classes.  For example, an element node is both a Node and an Element 
class object, so should have the methods for both the ::dom::node and 
::dom::element commands.  However, a TextNode or a Document node will 
have a different set a methods.

> (tclkit) 82 % set doc [dom::DOMImplementation create]
> ::dom::tcl::document7::Document
> (tclkit) 83 % set top [dom::document createElement $doc html]
> ::dom::tcl::document7::node2
> (tclkit) 84 % set title [$doc createElement title]
> ::dom::tcl::document7::node6
> (tclkit) 85 % $top appendChild $title
> ::dom::tcl::document7::node6
> (tclkit) 86 % set body [$doc createElement body]
> ::dom::tcl::document7::node13
> (tclkit) 87 % $top appendChild $body
> ::dom::tcl::document7::node13
> (tclkit) 88 % $body setAttribute bgcolor black
> unknown method "setAttribute"
>
> This does not work, however this:
>
> (tclkit) 90 % dom::element setAttribute $body bgcolor black
> black

Yes, that exactly the issue raised above.  "setAttribute" is a method 
of the ::dom::element command.  You'd like to be able to do:

$body setAttribute bgcolor black

What happens if you do:

$doc setAttribute bgcolor black

The latter should probably throw an exception.

Making the former work would mean either defining the node command as a 
separate function and implementing every method from every node class 
command (for both Tcl and libxml2), or modifying the node command to 
call the class-specific function if the method is not defined 
(actually, the latter would be the best approach).

> which is for me a little bit awkward, and I always forget to add the
> nodename after the (get|set)Attribute-command. I am used to javascript
> where we say something like:
>
> var input = window.document.createElement("input");
> input.setAttribute("name", "inputvalue");

Having to remember to add the node token does make the API a bit 
awkward, I agree.

> It should be not to difficult to write some simple wrapper classes
> with Snit or something similar. But using snit may slow down the code. 
> Did
> anyone have a better suggestion?

Do it in the TclDOM package itself; please submit a feature request to 
SF.

At the moment I'm flat-out with other (paid-for) projects so I won't be 
able to do anything about it in the short-term.  However, maybe someone 
else will step up to the plate and give it a go.

>  As a side effect the same code might run with tdom also.

Ah... that's a sore point.  You go talk to the tDOM people about 
compatibility :-(

Cheers,
Steve Ball

---

Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

Re: re[4]: [Tclxml-users] Dom node problems with tclsoap 1.6.7, tcldom 2.6 (libxml2)

[Steve B. <Ste...@zv...>]

On 15/09/2004, at 2:22 AM, Byron Whitlock wrote:

> Okay I think I have it running.
> Is there a way to tell which parser I am running?

You can get a list of available parser classes using:

xml::parserclass info names

You can get the default parser class using:

xml::parserclass info default

(I just noticed that option was missing from the man page, so I've 
fixed that)

> I did this:
> package require xml
> package require xml::libxml2
> package require dom
> And I get no errors.

Yes, this appears to be necessary on Windows.  I do that in the 
tkxmllint/tkxsltproc example applications.

I'll add that to the documentation.

> I am worried that I'm running the interpereted version though.

You shouldn't be, but the above commands will tell you.  You should see 
"libxml2" appear as an available parser class.

Cheers,
Steve Ball

---

Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

Re: [Tclxml-users] XHTML conform documenttype declaration

[Steve B. <Ste...@zv...>]

On 15/09/2004, at 12:22 AM, Detlef Groth wrote:

> Steve thanks for the fast response,

That's OK... I do my best ;-)

>>   Firstly, which version of TclDOM are you using?
>
> Version 3.0, the tcl-one.

OK - in that case submit a bug report.

>>> btw. a tDom like asHTML, asXML serialization would be great.
>>
>>   dom::serialize $doc -method "xml"
>>   dom::serialize $doc -method "html"
> (tclkit) 60 % package require dom
> 3.0
> (tclkit) 61 %  set doc [dom::DOMImplementation create]
> ::dom::tcl::document5::Document
> (tclkit) 62 %     set top [dom::document createElement $doc html]
> ::dom::tcl::document5::node2
> (tclkit) 63 %     set head [dom::document createElement $top head]
> ::dom::tcl::document5::node6
> (tclkit) 64 %     set title [dom::document createElement $head title]
> ::dom::tcl::document5::node10
> (tclkit) 65 %     set titleText [dom::document createTextNode $title 
> "MPIMG Berlin - Mouse Database"]
> ::dom::tcl::document5::node14
> (tclkit) 66 %    set body [dom::document createElement $top body]
> ::dom::tcl::document5::node18
> (tclkit) 67 %     set div [dom::document createElement $body div]
> ::dom::tcl::document5::node22
> (tclkit) 68 % dom::serialize $doc -method "html"
> <?xml version='1.0'?>
> <!DOCTYPE html>
> <html><head><title>MPIMG Berlin - Mouse 
> Database</title></head><body><div/></body></html>
> (tclkit) 69 %  dom::serialize $doc -method "xml"
> <?xml version='1.0'?>
> <!DOCTYPE html>
> <html><head><title>MPIMG Berlin - Mouse 
> Database</title></head><body><div/></body></html>
> (tclkit) 70 %  dom::serialize $doc
> <?xml version='1.0'?>
> <!DOCTYPE html>
> <html><head><title>MPIMG Berlin - Mouse 
> Database</title></head><body><div/></body></html>
>
> I can't see a difference between those three versions.

OK, I see what you mean.  Again, you'll have to submit a bug report 
against the TclDOM/Tcl package to improve the support for the -method 
option.

> May be if somebody could provide a minimal example writing an
> XHTML-conform document with TclDom this would be enough.

Sounds fair; that's something that should be on the website, or on the 
Tcl Wiki.

Once again, if you submit this as a feature request on SF so I don't 
forget, or someone else can be assigned the task, that would be very 
helpful.

Cheers,
Steve Ball

---

Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

[Tclxml-users] itcl/tk-like calling syntax for TclDom

[<dg...@mo...>]

Hello,

I like the itcl/tk- and Tdom-like calling conventions for tdom:

(tclkit) 82 % set doc [dom::DOMImplementation create]
::dom::tcl::document7::Document
(tclkit) 83 % set top [dom::document createElement $doc html]
::dom::tcl::document7::node2
(tclkit) 84 % set title [$doc createElement title]
::dom::tcl::document7::node6
(tclkit) 85 % $top appendChild $title
::dom::tcl::document7::node6
(tclkit) 86 % set body [$doc createElement body]
::dom::tcl::document7::node13
(tclkit) 87 % $top appendChild $body
::dom::tcl::document7::node13
(tclkit) 88 % $body setAttribute bgcolor black
unknown method "setAttribute"

This does not work, however this:

(tclkit) 90 % dom::element setAttribute $body bgcolor black
black

which is for me a little bit awkward, and I always forget to add the
nodename after the (get|set)Attribute-command. I am used to javascript
where we say something like:

var input = window.document.createElement("input");
input.setAttribute("name", "inputvalue");

(tclkit) 91 % ::dom::serialize $doc
<?xml version='1.0'?>
<!DOCTYPE html>
<html><title/><body bgcolor="black"/></html>

It should be not to difficult to write some simple wrapper classes
with Snit or something similar. As a side effect the same code might
run with tdom also. But using snit may slow down the code. Did
anyone have a better suggestion?

regards,
Detlef

-- 
Dr. Detlef Groth
Max-Planck-Institut
fuer Molekulare Genetik
Ihnestr. 63/73
D-14195 Berlin
Tel.: + 49 30 - 8413 1235

Re: [Tclxml-users] XHTML conform documenttype declaration

[<dg...@mo...>]

Steve thanks for the fast response,

>
>   Firstly, which version of TclDOM are you using?

Version 3.0, the tcl-one. 

>   On 14/09/2004, at 5:54 PM, Detlef Groth wrote:
>
>   > Hello, I am using TclDom inside the tclh-webserver to build an
>   > webapplication. I was trying to figure out how to build a
>   > XHTML-Declaration like this:
>   >
>   > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
>   >        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
>   >
>   > or a even a HTML-DTD
>   > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
>   >        "http://www.w3.org/TR/html4/strict.dtd">
>   >
>   > via this `dom::DOMImplementation createDocumentType' Command but did
>   > not get success.
>
>   If you are using v2.6 then it will definitely not work.
>   If you are using v3.0 then please submit a bug report.  documentType 
>   nodes should now be working correctly.
>
>   > btw. a tDom like asHTML, asXML serialization would be great.
>
>   dom::serialize $doc -method "xml"
>   dom::serialize $doc -method "html"
(tclkit) 60 % package require dom
3.0
(tclkit) 61 %  set doc [dom::DOMImplementation create]
::dom::tcl::document5::Document
(tclkit) 62 %     set top [dom::document createElement $doc html]
::dom::tcl::document5::node2
(tclkit) 63 %     set head [dom::document createElement $top head]
::dom::tcl::document5::node6
(tclkit) 64 %     set title [dom::document createElement $head title]
::dom::tcl::document5::node10
(tclkit) 65 %     set titleText [dom::document createTextNode $title "MPIMG Berlin - Mouse Database"]
::dom::tcl::document5::node14
(tclkit) 66 %    set body [dom::document createElement $top body]
::dom::tcl::document5::node18
(tclkit) 67 %     set div [dom::document createElement $body div]
::dom::tcl::document5::node22
(tclkit) 68 % dom::serialize $doc -method "html"
<?xml version='1.0'?>
<!DOCTYPE html>
<html><head><title>MPIMG Berlin - Mouse Database</title></head><body><div/></body></html>
(tclkit) 69 %  dom::serialize $doc -method "xml"
<?xml version='1.0'?>
<!DOCTYPE html>
<html><head><title>MPIMG Berlin - Mouse Database</title></head><body><div/></body></html>
(tclkit) 70 %  dom::serialize $doc
<?xml version='1.0'?>
<!DOCTYPE html>
<html><head><title>MPIMG Berlin - Mouse Database</title></head><body><div/></body></html>

I can't see a difference between those three versions.

>
>   aren't good enough for you?
>
>   > Here a trial with the `dom::DOMImplementation createDocumentType'
>   > set doc [dom::DOMImplementation createDocumentType HTML PUBLIC
>   > "-//W3C//DTD XHTML 1.0 Transitional//EN"
>   > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"]
>   > dom::serialize $doc
>   > but
>   > invalid command name "Serialize:documentType"
>
>   My first reaction is to make sure you are using v3.0.

May be if somebody could provide a minimal example writing an
XHTML-conform document with TclDom this would be enough.

Anyway it renders okay even if is not an valid XHTML-document, so
Steve did a great job. Thanks.

>
>   Cheers,
>   Steve Ball
>
>   ---
>
>   Steve Ball            |   XSLT Standard Library   | Training & Seminars
>   Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
>   http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
>   Ste...@zv...  +---------------------------+---------------------
>   Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099
>
>
regards,
Detlef

-- 
Dr. Detlef Groth
Max-Planck-Institut
fuer Molekulare Genetik
Ihnestr. 63/73
D-14195 Berlin
Tel.: + 49 30 - 8413 1235

Re: [Tclxml-users] XHTML conform documenttype declaration

[Steve B. <Ste...@zv...>]

Firstly, which version of TclDOM are you using?

On 14/09/2004, at 5:54 PM, Detlef Groth wrote:

> Hello, I am using TclDom inside the tclh-webserver to build an
> webapplication. I was trying to figure out how to build a
> XHTML-Declaration like this:
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
>        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
>
> or a even a HTML-DTD
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
>        "http://www.w3.org/TR/html4/strict.dtd">
>
> via this `dom::DOMImplementation createDocumentType' Command but did
> not get success.

If you are using v2.6 then it will definitely not work.
If you are using v3.0 then please submit a bug report.  documentType 
nodes should now be working correctly.

> btw. a tDom like asHTML, asXML serialization would be great.

dom::serialize $doc -method "xml"
dom::serialize $doc -method "html"

aren't good enough for you?

> Here a trial with the `dom::DOMImplementation createDocumentType'
> set doc [dom::DOMImplementation createDocumentType HTML PUBLIC
> "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"]
> dom::serialize $doc
> but
> invalid command name "Serialize:documentType"

My first reaction is to make sure you are using v3.0.

Cheers,
Steve Ball

---

Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

[Tclxml-users] XHTML conform documenttype declaration

[<dg...@mo...>]

Hello, I am using TclDom inside the tclh-webserver to build an
webapplication. I was trying to figure out how to build a
XHTML-Declaration like this:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

or a even a HTML-DTD
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
       "http://www.w3.org/TR/html4/strict.dtd">

via this `dom::DOMImplementation createDocumentType' Command but did
not get success. Here my trials:

set doc [dom::DOMImplementation create]
set top [dom::document createElement $doc html]
set head [dom::document createElement $top head]
set title [dom::document createElement $head title]
set titleText [dom::document createTextNode $title "MPIMG Berlin - Mouse Database"]
set body [dom::document createElement $top body]
set div [dom::document createElement $body div]
puts [dom::serialize $doc]
<?xml version='1.0'?>
<!DOCTYPE html>
<html><head><title>MPIMG Berlin - Mouse
Database</title></head><body><div/></body></html>

whichs renders ok in the browser but the correct declaration is
missing.

btw. a tDom like asHTML, asXML serialization would be great.

Here a trial with the `dom::DOMImplementation createDocumentType'
set doc [dom::DOMImplementation createDocumentType HTML PUBLIC
"-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"]
dom::serialize $doc
but
invalid command name "Serialize:documentType"

any help,suggestions on creating XHTML-conform documents?

regards,
Detlef

-- 
Dr. Detlef Groth
Max-Planck-Institut
fuer Molekulare Genetik
Ihnestr. 63/73
D-14195 Berlin
Tel.: + 49 30 - 8413 1235

Re: [Tclxml-users] Dom node problems with tclsoap 1.6.7, tcldom 2.6 (libxml2)

[Steve B. <Ste...@zv...>]

You could (should) try using TclXML/TclDOM v3.0.  The latest version is  
much more reliable in terms of managing document/node tokens.

HTHs,
Steve Ball

On 14/09/2004, at 8:25 AM, Byron Whitlock wrote:

> Using Tclsoap 1.6.7 tcldom/tclxml 2.6
>
> I've written a server using tclsoap.
>
> TclSoap is blowing up when trying to deserialize .NET style arrays.
>
> When using dom::tcl the problem does not happen, the array is  
> deserialized into a tcl list correctly.
>
> When using the libxml2 version of tcldom,  tcldom craps out:
> [dom::node parent $node]
> 'token "malformed node token "doc12"" is not a DOM Document'
>
> Has anyone seen this before?
>
>
> ================Request============================================
> <?xml version="1.0" encoding="utf-8"?><soap:Envelope  
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"  
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"  
> xmlns:tns="http://www.lyris.com/lmapi"  
> xmlns:types="http://www.lyris.com/lmapi/encodedTypes"  
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  
> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>
> <soap:Body  
> soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
>
>         <q1:SelectMembers xmlns:q1="lmapi">
>                 <ArrayOfFilterCriteria href="#id1" />
>         </q1:SelectMembers>
>
>         <soapenc:Array id="id1" soapenc:arrayType="xsd:string[2]">
>                 <Item>EmailAddress like %1balh% </Item>
>                 <Item>ListName = list1 </Item>
>         </soapenc:Array>
> </soap:Body>
>
> </soap:Envelope>
>
>
>
> ====================RESPONCE===============================
> <?xml version="1.0"?>
> <SOAP-ENV:Envelope  
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"  
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"  
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"  
> xmlns:s0="http://www.lyris.com/lmapi"><SOAP-ENV:Body><SOAP-ENV: 
> Fault><faultcode>NONE</faultcode><faultstring>token "malformed node  
> token "doc12"" is not a DOM Document</faultstring><detail><e:errorInfo  
> xmlns:e="urn:TclSOAP-ErrorInfo"><errorCode>NONE</ 
> errorCode><stackTrace>token "malformed node token "doc12"" is not a  
> DOM Document
>     while executing
> "dom::node parent $node"
>     (procedure "getDocumentElement" line 2)
>     invoked from within
> "getDocumentElement $parent"
>     (procedure "getDocumentElement" line 6)
>     invoked from within
> "getDocumentElement $parent"
>     (procedure "getDocumentElement" line 6)
>     invoked from within
> "getDocumentElement $parent"
>     (procedure "getDocumentElement" line 6)
>     invoked from within
> "getDocumentElement $parent"
>     (procedure "getDocumentElement" line 6)
>     invoked from within
> "getDocumentElement $parent"
>     (procedure "getDocumentElement" line 6)
>     invoked from within
> "getDocumentElement $domElement"
>     (procedure "getElementValue" line 10)
>     invoked from within
> "getElementValue $domElement"
>     (procedure "decomposeSoap" line 9)
>     invoked from within
> "decomposeSoap  
> $node"</stackTrace></e:errorInfo></detail></SOAP-ENV:Fault></SOAP-ENV: 
> Body></SOAP-ENV:Envelope>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> Tclxml-users mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tclxml-users
>
>

---

Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

[Tclxml-users] Dom node problems with tclsoap 1.6.7, tcldom 2.6 (libxml2)

[Byron W. <by...@ly...>]

Using Tclsoap 1.6.7 tcldom/tclxml 2.6=20

I've written a server using tclsoap.

TclSoap is blowing up when trying to deserialize .NET style arrays.

When using dom::tcl the problem does not happen, the array is deserialized into =
a tcl list correctly.

When using the libxml2 version of tcldom,  tcldom craps out:
[dom::node parent $node]
'token "malformed node token "doc12"" is not a DOM Document'

Has anyone seen this before?


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DRequest=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
<?xml version=3D"1.0" encoding=3D"utf-8"?><soap:Envelope =
xmlns:soap=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:soapenc=3D"http://schemas.xmlsoap.org/soap/encoding/" =
xmlns:tns=3D"http://www.lyris.com/lmapi" =
xmlns:types=3D"http://www.lyris.com/lmapi/encodedTypes" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema">

<soap:Body soap:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/">

        <q1:SelectMembers xmlns:q1=3D"lmapi">
                <ArrayOfFilterCriteria href=3D"#id1" />
        </q1:SelectMembers>

        <soapenc:Array id=3D"id1" soapenc:arrayType=3D"xsd:string[2]">
                <Item>EmailAddress like %1balh% </Item>
                <Item>ListName =3D list1 </Item>
        </soapenc:Array>
</soap:Body>

</soap:Envelope>



=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DRESPONCE=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
<?xml version=3D"1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:SOAP-ENC=3D"http://schemas.xmlsoap.org/soap/encoding/" =
xmlns:s0=3D"http://www.lyris.com/lmapi"><SOAP-ENV:Body><SOAP-ENV:Fault><faultco=
de>NONE</faultcode><faultstring>token "malformed node token "doc12"" is not a =
DOM Document</faultstring><detail><e:errorInfo =
xmlns:e=3D"urn:TclSOAP-ErrorInfo"><errorCode>NONE</errorCode><stackTrace>token =
"malformed node token "doc12"" is not a DOM Document
    while executing
"dom::node parent $node"
    (procedure "getDocumentElement" line 2)
    invoked from within
"getDocumentElement $parent"
    (procedure "getDocumentElement" line 6)
    invoked from within
"getDocumentElement $parent"
    (procedure "getDocumentElement" line 6)
    invoked from within
"getDocumentElement $parent"
    (procedure "getDocumentElement" line 6)
    invoked from within
"getDocumentElement $parent"
    (procedure "getDocumentElement" line 6)
    invoked from within
"getDocumentElement $parent"
    (procedure "getDocumentElement" line 6)
    invoked from within
"getDocumentElement $domElement"
    (procedure "getElementValue" line 10)
    invoked from within
"getElementValue $domElement"
    (procedure "decomposeSoap" line 9)
    invoked from within
"decomposeSoap =
$node"</stackTrace></e:errorInfo></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SO=
AP-ENV:Envelope>

[Tclxml-users] tkxmllint, tkxsltproc

[Steve B. <Ste...@zv...>]

Version 1.6 of the tkxmllint and tkxsltproc applications has been 
released,
but so far only for Mac OS X.  An MS Windows version will be released 
shortly.
When all platform binaries are available I will be making a wider 
announcement.

This version addresses a number of bugs and adds new functionality:

* Handling of character encoding has been improved in both input and 
output
* Relative URIs in system identifiers are now supported
* Indenting of output is now supported
* An interface has been added to save profiling information
* The URI of the result document is made known to the stylesheet
(allowing chunking to work correctly)

Get the new version from the SourceForge website:

http://tclxml.sourceforge.net/tkxmllint.html
http://tclxml.sourceforge.net/tkxsltproc.html

Enjoy!

---

Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099