TclXML is Explain's XML extension, based at http://sf.net/projects/tclxml/ .
What: TclXML
Where: http://tclxml.sf.net/
http://sf.net/project/showfiles.php?group_id=13178
http://webperso.easyconnect.fr/bdesgraupes/tcl.html
Description: This project covers a range of specifications and
tools for processing and manipulating XML documents using Tcl.
Collectively these tools are known as TclXML.
Includes a parser written in
Tcl which has equivalent functionality to TclExpat, known as the
"native" TclXML parser (now also available for download).
Check the code for some introductory work on an XML DTD parser.
A mailing list is available.
Binary versions for MacOS X and Windows are available =
see the combo html page above.
The current version is 3.2 .
Updated: 12/2008
Contact: mailto:[email protected]TclXML v3.2 now includes TclDOM and TclXSLT.
As of September 2001, TclXML has a pure-Tcl XPath parser.
This package is part of the ActiveTcl Batteries Included distribution.
Examples, Tutorials, etc.
Please let SRB know what XML-related tasks you are having trouble understanding. I'd like to start a series of pages that provide a tutorial on using TclXML.
There have been some people having problems loading the TclDOM and TclXML packages into Safe interpreters. The problem is that the safe package restricts filenames to 14 characters. TclXML has tclparser-8.1.tcl as one of its files, which exceeds this limit. Here is the TclSOAP solution which removes this restriction:
proc SOAP::CGI::createInterp {interp path} {
set slave [safe::interpCreate $interp]
safe::interpAddToAccessPath $slave $path
# override the safe restrictions so we can load our
# packages (actually the xml package files)
proc ::safe::CheckFileName {slave file} {
if {![file exists $file]} {error "file non-existent"}
if {![file readable $file]} {error "file not readable"}
}
return $slave
}This returns a safe interpreter for which interp eval "package require xml" should work. PT
[As people keep turning up asking for tutorials on getting started with TclXML--the most basic things, like retrieval of one value from one tag of a single document--I want to make a point at least of putting a few links here which point to Steve's explanations in the mailing list.]
Dave Griffin offers a sample retrieval of values from a DOM tree: (19-Aug-2004 Note: This example seems to have stopped working! Did the getElementsByTagName method become "unimplemented" at some point? -dmg) (SRB 20-Aug-2004 Answer: The API changed some time ago. getElementsByTagName is a "live-list"; i.e., its return value is the name of a variable that contains the list of matching nodes. This variable must be dereferenced to get the actual node tokens. In addition, the result is a set (list) of nodes so you must handle that, but in this simple case just getting the first node is sufficient. E.g.
set sr [dom::document getElementsByTagName $d SampleRequest]
should be
set sr [lindex [set [dom::document getElementsByTagName $d SampleRequest]] 0]
Sounds complicated? That's because it is. A simpler and better way is to use XPath:
set sr [dom::document selectNode $d /SampleRequest] set purl [$sr selectNode PostingURL]
SRB)
package require xml
package require dom
set xmlSrc {
<?xml version="1.0" encoding="UTF-8"?>
<SampleRequest>
<PostingURL url="http://foo.com/some/service/url"/>
<Password>FooBar</Password>
</SampleRequest>
}
# First you parse the XML, the result is held in token d.
set xmlSrc [string trim $xmlSrc] ;# v2.6 barfed w/o this
set d [dom::DOMImplementation parse $xmlSrc]
# One way in is to parse it by the assumed structure and
# use the Document interface -style of query. This code isn't
# flexible at all and only highlights how the dom methods
# can be used.
# First find the SampleRequest element in the DOCUMENT
set sr [set [dom::document getElementsByTagName $d SampleRequest]]
# Next retrieve the two sub-elements in SampleRequest
set purl [set [dom::element getElementsByTagName $sr PostingURL]]
set pword [set [dom::element getElementsByTagName $sr Password]]
# Now we will retrieve the url attribute of PostingURL
set url [dom::element getAttribute $purl url]
# url == "http://foo.com/some/service/url"
puts "url = $url"
# Finally, we want to retrieve the password. This is non-obvious.
# The value "FooBar" is actually in a "textNode" child of pword,
# so you have to do ferret it out with generic node commands.
set pwordv [dom::node children $pword]
# You could have also used: dom::node cget $pword -firstchild
# dom::node cget $pwordv -nodeType -> textNode
set password [dom::node cget $pwordv -nodeValue]
# password == "FooBar"
puts "password = $password"
Note: The above example did not work (at least not with my TclXML 3.0). It was missing the second "set" command in order to access the data returned by the dom::document and dom::element instructions.
Steve's starting to make courseware available through http://www.zveno.com/courses/samples/XML-App-Dev-Tcl/ (this link is broken :-( )
escargo 05/05/05 - As of this date, there is nothing there, perhaps because Steve isn't at zveno any more.
SRB 2005-11-07 - that's right, I'm now at Explain. We'll try and get some of these tutorials available ASAP.
The 2001 article, "Programming XML and Web services in TCL" [L1 ], features TclXML.
The TclXML SourceForge Site mentions this document:
TclXML: The Next Generation. Presented at the 9th Tcl Workshop, 16-19 September 2002, Vancouver Canada.
RA 2006-11-24: A link is available here:
SRB 2005-11-07 - See above. My move from Zveno has resulted in a few pages being dropped. I'm working on getting these restored.
LV 2008-01-15 A few notes while building tclxml for Tcl 8.5. I obtained the cvs head tclxml tar file from the tcl xchange's netcvs mirror. I extracted the tar so that it was a sibling to tcl 8.5's directory. I then had to run autoconf so that a configure file was available. I typically run configure and make in a subdirectory named after the type of OS I am using (for instance, unix). The configure was successful, but included a warning about tclxml's Makefile.in seeming to ignore the --datarootdir setting. At this point, there were warnings about PACKAGE_NAME and a few other macros being redefined, but the .o files were generated. Next, the makefile built the libTclxmlstub3.1g.a and .so files. Then, I tried to run the test suite. However, the Makefile attempts to use tclsh8.4 for the test suite, but the install directory supplied only has tclsh8.5, so that failed.
I'll submit a bug report on this error.
SRB 2008-12-17 - The v3.2 release has been tested against Tcl 8.5. Things should be much better now.
| Category Package | Category XML | Category Parsing |
|---|