Menu
▾
▴
tclxml-users — Discussion on using the TclXML package
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(18) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(11) |
Feb
(2) |
Mar
(1) |
Apr
(4) |
May
(23) |
Jun
(17) |
Jul
(1) |
Aug
(17) |
Sep
(4) |
Oct
(14) |
Nov
(1) |
Dec
(2) |
| 2002 |
Jan
|
Feb
(2) |
Mar
(15) |
Apr
|
May
(19) |
Jun
(2) |
Jul
(8) |
Aug
(24) |
Sep
(21) |
Oct
(17) |
Nov
(11) |
Dec
(20) |
| 2003 |
Jan
(17) |
Feb
(19) |
Mar
(21) |
Apr
(13) |
May
(14) |
Jun
(7) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(3) |
| 2004 |
Jan
(5) |
Feb
(2) |
Mar
|
Apr
(3) |
May
(1) |
Jun
(5) |
Jul
(12) |
Aug
(3) |
Sep
(14) |
Oct
(1) |
Nov
(4) |
Dec
(3) |
| 2005 |
Jan
(1) |
Feb
(6) |
Mar
(3) |
Apr
|
May
(2) |
Jun
(3) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
| 2006 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2007 |
Jan
(1) |
Feb
(7) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(8) |
Oct
(1) |
Nov
|
Dec
|
|
From: Steve B. <Ste...@zv...> - 2001-08-15 22:30:46
|
Larry W. Virden wrote: > > I am investigating tclxml, tcldom, and tclsoap and have gotten the first > and last of these packages - but I can't seem to locate a place to download > a tar file of tcldom. Anyone know where I can turn? Thanks! TclDOM v2.0 has not yet been officially released, so there's no tarball. While I'd like to do more work on the package (more Level 2/3 support, XPath support, etc), perhaps there's no point in delaying release. At this stage there's some significant release engineering to be done. Do folks want an official v2.0 release sooner, rather than later? 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 |
|
From: Larry W. V. <lv...@ca...> - 2001-08-15 15:24:13
|
I am investigating tclxml, tcldom, and tclsoap and have gotten the first and last of these packages - but I can't seem to locate a place to download a tar file of tcldom. Anyone know where I can turn? Thanks! -- Never apply a Star Trek solution to a Babylon 5 problem. 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. -><- |
|
From: Peter F. <pet...@zv...> - 2001-08-02 16:30:13
|
Steve Ball wrote:
>
> "Kenneth H. Cox" wrote:
> >
> > Folks, I was trying to use TclSOAP to do RPC when I encountered a
> > tclxml parser bug (it's in the sourceforge tracker): it can't parse
> > this:
> >
> > <?xml version='1.0'?>
> > <Envelope><Body><method>
> > <return>{{SOAP transport error: "HTTP/1.1 401 Authorization Required"}}</return>
> > </method></Body></Envelope>
>
> TclXML v2.1theta fixes that bug. I just released it.
>
> > I thought I should try the C-based parsers, thinking maybe since these
> > are tcl-special characters, the bug won't exist in the C parser. I
> > compiled up the latest tclxml and tcldom. To my surprise, it dumps
> > core when running the tests:
> >
> > $ tclsh8.2 tclxml.tcl
> > ...
> > Tcl_AppendStringsToObj called with shared object
> > Abort (core dumped)
> >
> > Am I wasting my time, or does anyone have the C parsers working? I
> > tried with tcl8.2.3 and tcl8.3.3.
>
> That's why the C distribution of TclXML hasn't been released yet.
> Peter Farmer was working on trying to track down and fix that bug,
> but if anyone can help it would be much appreciated. I believe the
> problem is in the TclXML generic layer, rather than the expat wrapper
> module (Pete: can you add to this?).
>
I was chasing that bug several months ago. It was proving very difficult
to
debug. I know where it goes wrong, but still havent figured why .
I had to lay it aside coz it was taking up too much paid work time. I
hope
to pick up the threads and trace away at that issue again tomorrow.
--
Peter Farmer | Custom XML software | Internet Engineering
Zveno Pty Ltd | Website XML Solutions | Training & Seminars
http://www.zveno.com/ | Open Source Tools | - XML XSL Tcl
Pet...@zv... +------------------------+---------------------
Ph. +61 8 92036380 | Mobile +61 417 906 851 | Fax +61 8 92036380
|
|
From: Steve B. <Ste...@zv...> - 2001-08-02 07:43:03
|
"Kenneth H. Cox" wrote:
>
> Folks, I was trying to use TclSOAP to do RPC when I encountered a
> tclxml parser bug (it's in the sourceforge tracker): it can't parse
> this:
>
> <?xml version='1.0'?>
> <Envelope><Body><method>
> <return>{{SOAP transport error: "HTTP/1.1 401 Authorization Required"}}</return>
> </method></Body></Envelope>
TclXML v2.1theta fixes that bug. I just released it.
> I thought I should try the C-based parsers, thinking maybe since these
> are tcl-special characters, the bug won't exist in the C parser. I
> compiled up the latest tclxml and tcldom. To my surprise, it dumps
> core when running the tests:
>
> $ tclsh8.2 tclxml.tcl
> ...
> Tcl_AppendStringsToObj called with shared object
> Abort (core dumped)
>
> Am I wasting my time, or does anyone have the C parsers working? I
> tried with tcl8.2.3 and tcl8.3.3.
That's why the C distribution of TclXML hasn't been released yet.
Peter Farmer was working on trying to track down and fix that bug,
but if anyone can help it would be much appreciated. I believe the
problem is in the TclXML generic layer, rather than the expat wrapper
module (Pete: can you add to this?).
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
|
|
From: Steve B. <Ste...@zv...> - 2001-08-02 07:32:08
|
TclXML version 2.1 'theta' A new version of the Tcl-only distribution of TclXML has been released. This version contains mainly bug fixes, but the fixes improve well-formedness checking so that XML documents which were previously accepted are now rejected. ----- TclXML is a framework for parsing XML documents in Tcl. The 'theta' distribution only includes Tcl scripts, whereas the full distribution includes wrappers for XML parsers written in C (such as expat). For more information, see http://tclxml.sourceforge.net/ To download go to http://prdownloads.sourceforge.net/tclxml/ -- 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 |
|
From: Kenneth H. C. <ke...@sy...> - 2001-08-02 02:00:31
|
Folks, I was trying to use TclSOAP to do RPC when I encountered a tclxml
parser bug (it's in the sourceforge tracker): it can't parse this:
<?xml version='1.0'?>
<Envelope><Body><method>
<return>{{SOAP transport error: "HTTP/1.1 401 Authorization Required"}}</return>
</method></Body></Envelope>
I thought I should try the C-based parsers, thinking maybe since these
are tcl-special characters, the bug won't exist in the C parser. I
compiled up the latest tclxml and tcldom. To my surprise, it dumps core
when running the tests:
$ tclsh8.2 tclxml.tcl
...
Tcl_AppendStringsToObj called with shared object
Abort (core dumped)
Am I wasting my time, or does anyone have the C parsers working? I
tried with tcl8.2.3 and tcl8.3.3.
Thanks,
--
Ken
|
|
From: Steve B. <Ste...@zv...> - 2001-08-01 01:47:44
|
Rene Humberto Maldonado Fimbres wrote: > > Hi, I'm making some tests whith TclXML and I need to ignore white > spaces... > > -ignorewhitespaces it's not working, here is my code: > > set p [xml::parser -ignorewhitespace true -characterdatacommand > cdata] Please submit a bug report on the SourceForge site, so that I can manage and track it better. 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 |
|
From: Rene H. M. F. <re...@te...> - 2001-07-25 00:22:12
|
Hi, I'm making some tests whith TclXML and I need to ignore white spaces... -ignorewhitespaces it's not working, here is my code: set p [xml::parser -ignorewhitespace true -characterdatacommand cdata] I also try with TREU, 1, but it just don't work.. thanks Rene |
|
From: Asim I. <asi...@ho...> - 2001-06-25 08:17:40
|
Hello All, i have refered to you people by Steve Ball. My name is Asim and im woking in a software house in Pakistan as a software Engineer. i have developed a com component and now i want to integrate this with my other application using xml-rpc for tcl. i got tcl web server for this but i dont know how it is going to be configured for xml-rpc. Can any one help me in this regard. and if any one of you have examples relating this work plz send them to me. i will be very gratefull to you. regards, ASIM ISRAR _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. |
|
From: Steve B. <Ste...@zv...> - 2001-06-22 12:09:07
|
"Lowry, Shaun (ISSReading)" wrote: > > I've checked out TclDOM 2.0 from the CVS repository and want to try and get > the tcldom.cpp Xerces-C wrapper built, but I seem to be missing some files > notably TclDOM_Node.hpp. Anyone know where I can get this? Has anyone else > had any experience with it? All of the Xerces stuff is in a branch off the main trunk. As I recall, the branch was called "xerces" - you may wish to search through the mailing list archive to get an exact reference. If you can't find it, I'll search through my archives... Cheers, Steve Ball -- Steve Ball | waX Me Lyrical XML Editor | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL 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 |
|
From: Lowry, S. (ISSReading) <sl...@is...> - 2001-06-22 09:05:33
|
I've checked out TclDOM 2.0 from the CVS repository and want to try and get the tcldom.cpp Xerces-C wrapper built, but I seem to be missing some files notably TclDOM_Node.hpp. Anyone know where I can get this? Has anyone else had any experience with it? Shaun. |
|
From: Mats B. <ma...@pr...> - 2001-06-19 16:21:16
|
Steve Ball wrote:
>
> Mats Bengtsson wrote:
> > If there is an entity to be expanded in character data, and if
> > this entity is embraced, as in:
> >
> > <body>.can create text 10 10 -text {Hello "new World"}</body>
> >
> > the resulting parsed character data is not a well formed tcl expression anymore.
>
> That sure look like a bug. There's now a bug submission in
> SourceForge for this problem, and I'll look into it ASAP.
>
As a workaround, I can switch off the internal entity replacements,
and do entity replacements by "hand" when getting complete character data.
That works for me, so there is "no cow on the ice".
Swedish saying...
Mats
|
|
From: Cameron L. <cl...@st...> - 2001-06-18 21:53:12
|
From Ste...@zv... Tue Jun 5 18:20:09 2001 . . . CC: tcl...@li... Subject: Re: [Tclxml-users] spaces near attributes References: <200...@st...> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cameron Laird wrote: > > What was the decision about > <?xml version="1.0"?> > vs. > <?xml version = "1.0"?> > ? Version 1.9 of the xml package accepts the former, > and rejects the latter. I'm sure we've discussed this > before, and I've been utterly unable to track down the > conclusion. Please submit this as a bug report on SourceForge. . . . <URL: http://sourceforge.net/tracker/index.php?func=detail&aid=434304&group_id=13178&atid=113178 > |
|
From: Steve B. <Ste...@zv...> - 2001-06-17 01:31:51
|
Mats Bengtsson wrote:
> If there is an entity to be expanded in character data, and if
> this entity is embraced, as in:
>
> <body>.can create text 10 10 -text {Hello "new World"}</body>
>
> the resulting parsed character data is not a well formed tcl expression anymore.
That sure look like a bug. There's now a bug submission in
SourceForge for this problem, and I'll look into it ASAP.
Unfortunately, ASAP is not as soon as I'd like since I'm absolutely
swamped with XML training and consulting commitments for the next
month or so :-(
Cheers,
Steve Ball
--
Steve Ball | waX Me Lyrical XML Editor | Training & Seminars
Zveno Pty Ltd | Web Tcl Complete | XML XSL
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
|
|
From: Steve B. <Ste...@zv...> - 2001-06-17 01:29:23
|
Cameron Laird wrote: > What puzzles me, though, is that I see in the WSDL world, > for example, > <?xml version='1.0'> > <!-- what happened to the DOCTYPE? --> > <wsdl:definitions xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'> > ... > </wsdl:definitions> > What is *that*? Is there some name for version-element-plus- > serialized-document? Is there a clever way to generate it? That's an XML Namespace declaration. DOM Level 2 supports XML Namespaces, and TclDOM v2.0 includes (partial) support for DOM Level 2. Support for XML Namespaces is part of TclDOM v2. BTW, the Document Type Declaration is not required (it's optional in XML anyway). XML Namespaces do not mix at all with DTDs so it's pretty pointless having a Doc Type Declaration when the document is using XML Namespaces. > Quite-unrelated question: has anyone written > WSDL::pretty_print node > to supplement > WSDL::serialize node > ? The former would, I imagine, indent elements proportionally > to their depth, and perhaps prettify attribute punctuation, and > so on. Would such a thing interest anyone else, if I write it? Again, see the '-indent' option of the serialize method. Cheers, Steve Ball -- Steve Ball | waX Me Lyrical XML Editor | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL 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 |
|
From: Steve B. <Ste...@zv...> - 2001-06-17 01:25:58
|
Cameron Laird wrote:
>
> in TclDOM (or tDOM, for that matter)? Will anyone
> else want one I write?
Sorry to steal your thunder, but of course there is!
dom::DOMImplementation serialize accepts the -indent and
-indentspec arguments.
-indent can have the value "yes" ("true" or "on") or
"no" ("false" or "off"). NB. DON'T use 0 or 1.
This option enables (disables) indenting element content
that is element-only content.
The -indentspec option controls how whitespace is used to
do the indenting, and is a RE+replacement string. The default is
to replace sequence of eight spaces with a tab character.
For example:
dom::DOMImplementation serialize $doc -indent yes
There's also the (cruder) -newline option.
Cheers,
Steve Ball
--
Steve Ball | waX Me Lyrical XML Editor | Training & Seminars
Zveno Pty Ltd | Web Tcl Complete | XML XSL
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
|
|
From: Steve B. <Ste...@zv...> - 2001-06-17 01:20:08
|
Cameron Laird wrote: > > to get TclDOM to create a document withOUT a > <!DOCTYPE ...> Try: dom::DOMImplementation serialize $doc -showdoctypedecl 0 Similarly, this method also accepts the -showxmldecl option too. Cheers, Steve Ball -- Steve Ball | waX Me Lyrical XML Editor | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL 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 |
|
From: Cameron L. <cl...@st...> - 2001-06-15 14:24:57
|
From tcl...@li... Thu Jun 14 13:11:12 2001 From: Cameron Laird <cl...@st...> To: tcl...@li... Subject: [Tclxml-users] Is there truly no dom::pretty_print . . . in TclDOM (or tDOM, for that matter)? Will anyone else want one I write? . . . <URL: http://starbase.neosoft.com/~claird/comp.lang.tcl/dom_pretty_print.html > |
|
From: Cameron L. <cl...@st...> - 2001-06-14 17:49:16
|
in TclDOM (or tDOM, for that matter)? Will anyone else want one I write? |
|
From: Cameron L. <cl...@st...> - 2001-06-13 17:15:04
|
From jen...@fl... Tue Jun 12 20:19:32 2001 . . . > [is there a way] > to get TclDOM to create a document withOUT a > <!DOCTYPE ...> Serialize the document element node instead of the root node: package require dom set doc [dom::DOMImplementation create] dom::node appendChild $doc [dom::document createElement $doc FOO] # To include <!DOCTYPE ...> declaration: dom::DOMImplementation serialize $doc # To omit it: dom::DOMImplementation serialize \ [dom::document cget $doc -documentElement] . . . Thank you, Joe. What I really need is more XML documentation. In fact, I've been doing the serialize-the-document trick, and thinking of it as a trick; apparently I wasn't so ori- ginal. What puzzles me, though, is that I see in the WSDL world, for example, <?xml version='1.0'> <!-- what happened to the DOCTYPE? --> <wsdl:definitions xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'> ... </wsdl:definitions> What is *that*? Is there some name for version-element-plus- serialized-document? Is there a clever way to generate it? Quite-unrelated question: has anyone written WSDL::pretty_print node to supplement WSDL::serialize node ? The former would, I imagine, indent elements proportionally to their depth, and perhaps prettify attribute punctuation, and so on. Would such a thing interest anyone else, if I write it? |
|
From: Joe E. <jen...@fl...> - 2001-06-13 01:02:06
|
Cameron Laird wrote:
> [is there a way]
> to get TclDOM to create a document withOUT a
> <!DOCTYPE ...>
Serialize the document element node
instead of the root node:
package require dom
set doc [dom::DOMImplementation create]
dom::node appendChild $doc [dom::document createElement $doc FOO]
# To include <!DOCTYPE ...> declaration:
dom::DOMImplementation serialize $doc
# To omit it:
dom::DOMImplementation serialize \
[dom::document cget $doc -documentElement]
I think that dom::c has a bug where [dom::DOMImplementation serialize]
can end up writing out _two_ <!DOCTYPE ...> declarations
under certain circumstances; I haven't looked into this yet.
--Joe English
jen...@fl...
|
|
From: Cameron L. <cl...@st...> - 2001-06-12 20:26:37
|
to get TclDOM to create a document withOUT a <!DOCTYPE ...> ? |
|
From: Mats B. <ma...@pr...> - 2001-06-12 16:15:24
|
Hi,
If there is an entity to be expanded in character data, and if
this entity is embraced, as in:
<body>.can create text 10 10 -text {Hello "new World"}</body>
the resulting parsed character data is not a well formed tcl expression anymore.
The result is:
% $myParser parse $data6
Element start ==> stream
Character data ==>
Element start ==> body
Character data ==> .can create text 10 10 -text \{Hello }
Character data ==> "
Character data ==> new World
Character data ==> "
Character data ==> \
Element end ==> body
Character data ==>
Element end ==> stream
%
If assembling the ch data we get:
.can create text 10 10 -text \{Hello }"new World"\
which is not a well formed tcl expression. I think the reason is that the character
data callbacks are split up so that entities are reported alone. When tcl handles
an open braced structure, it starts to insert backslashes in a number of places.
Somehow this is not robust, and results in the result above.
Yes, entity parsing can be switched
off by -defaultexpandinternalentities 0 which works (though no entity parsing).
Having tcl code like this is not an example of good structure, and is only
to get things up running fast.
The code was:
package require xml
proc HandleStart {name attlist} {
if {[llength $attlist] > 0} {
puts stderr "Element start ==> $name has attributes $attlist"
} else {
puts stderr "Element start ==> $name"
}
}
proc HandleEnd {name} {
puts stderr "Element end ==> $name"
}
proc HandleText {data} {
puts stderr "Character data ==> $data"
}
set data6 {<stream><body>.can create text 10 10 -text {Hello "new World"}</body></stream>}
set myParser [xml::parser]
$myParser configure -elementstartcommand HandleStart \
-ignorewhitespace 1 \
-elementendcommand HandleEnd -characterdatacommand HandleText
$myParser parse $data6
/Mats
|
|
From: Steve B. <Ste...@zv...> - 2001-06-05 23:04:46
|
Cameron Laird wrote: > > What was the decision about > <?xml version="1.0"?> > vs. > <?xml version = "1.0"?> > ? Version 1.9 of the xml package accepts the former, > and rejects the latter. I'm sure we've discussed this > before, and I've been utterly unable to track down the > conclusion. Please submit this as a bug report on SourceForge. According to the XML Specification, 2nd Edition, the version attribute may be surrounded by spaces ([25]), but TclXML v2.0theta is rejecting it. Cheers, Steve Ball -- Steve Ball | waX Me Lyrical XML Editor | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL 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 |
|
From: Cameron L. <cl...@st...> - 2001-06-05 15:38:43
|
What was the decision about <?xml version="1.0"?> vs. <?xml version = "1.0"?> ? Version 1.9 of the xml package accepts the former, and rejects the latter. I'm sure we've discussed this before, and I've been utterly unable to track down the conclusion. |
3 messages has been excluded from this view by a project administrator.
