Where to find SOAP::dom
Christian Heide Damm
In SOAP.tcl, the following statement is executed:
package require SOAP::dom
Where can I find this package?
Christian
Cameron Laird
.
.
Do you mean that in the sense addressed in the second
paragraph of <URL: http://mini.net/tcl/TclSOAP>:
A fairly large number of people have
trouble finding a suitable TclDOM
package to use with the SOAP package.
I have therefore placed the versions
of TclDOM 2.0 that I use for
development at http://
tclsoap.sourceforge.net/dom-packages.html
You can still get the canonical TclDOM
code from http://sourceforge.net/projects/tclxml
?
--
Cameron Laird <Cam...@Lairds.com>
Business: http://www.Phaseit.net
Personal: http://starbase.neosoft.com/~claird/home.html
Pat Thoyts
You don't. :)
The actual code involved here is:
if {[catch {
package require tdom
package require SOAP::dom
log::log debug "using tDOM and SOAP::dom"
}]} {
if { [catch {package require dom 2.0} domVer]} {
if { [catch {package require dom 1.6} domVer]} {
error "require dom package greater than 1.6"
}
package require SOAP::xpath
}
}
There ought to be a comment on it but the intent is to create a
wrapper to permit the use of tDOM with TclSOAP. To do this I began
constructing a 'shim' that converted TclDOM interface calls to tDOM
calls. However, it isn't complete and won't work yet.
What happens is that tDOM is loaded, but the package require SOAP::dom
fails so you then load in tcldom. Once the SOAP::dom shim is complete
then you'll be able to use tDOM or TclDOM. But not yet!
Sorry,
Pat Thoyts.
Christian Heide Damm
> ...
> What happens is that tDOM is loaded, but the package require SOAP::dom
> fails so you then load in tcldom. Once the SOAP::dom shim is complete
> then you'll be able to use tDOM or TclDOM. But not yet!
I'm not sure I understand.
Does this mean that I can't use either of tDOM or TclDOM? Then how do I construct my XML documents to be
used in SOAP messages?
When do you think the wrapper for tDOM will be ready?
Christian
Pat Thoyts
>Pat Thoyts wrote:
>
>> ...
>> What happens is that tDOM is loaded, but the package require SOAP::dom
>> fails so you then load in tcldom. Once the SOAP::dom shim is complete
>> then you'll be able to use tDOM or TclDOM. But not yet!
>
>I'm not sure I understand.
>
>Does this mean that I can't use either of tDOM or TclDOM? Then how do I construct my XML documents to be
>used in SOAP messages?
You misunderstand me. TclSOAP works with TclDOM. One day it might be
able to work with tDOM as well via the use of this SOAP::dom module
but this module is incomplete.
>
>When do you think the wrapper for tDOM will be ready?
>
I have two small children so no guaruntees but there is some interest
in this so I shall likely revist it soon. By Christmas if you're
lucky. :)
--
Pat Thoyts http://www.zsplat.freeserve.co.uk/resume.html
To reply, rot13 the return address or read the X-Address header.
PGP fingerprint 2C 6E 98 07 2C 59 C8 97 10 CE 11 E6 04 E0 B9 DD
Steve Ball
> There ought to be a comment on it but the intent is to create a
> wrapper to permit the use of tDOM with TclSOAP. To do this I began
> constructing a 'shim' that converted TclDOM interface calls to tDOM
> calls. However, it isn't complete and won't work yet.
Ideally, TclDOM and tDOM would be API compatible. A while ago
I tried several times to contact Joachim to get agreement on
a compatible API, but to no avail :-(
If your desire to use tDOM is speed, then perhaps a Tcl wrapper
to libxml2 might help? I have checked-in the start of such
a beast to the TclXML CVS repository - look for the subdir
src-libxml2 in the TclDOM module.
Cheers,
Steve
--
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
Steve...@zveno.com +---------------------------+---------------------
Ph. +61 2 6242 4099 | Mobile (0413) 594 462 | Fax +61 2 6242 4099
Christian Heide Damm
I have downloaded TclDOM from the SOAP project homepage, but it crashes,
when I try to load it. Probably it was built for another tcl-version. I use
8.4a2.
I have checked out the latest TclDOM from CVS (btw.: is there a stable
release that I could use instead?), but I don't know how to build it :-(
Any help appreciated (e.g., in the form of a .dsw file).
Thanks,
Christian
---
Joe English
>I have checked out the latest TclDOM from CVS (btw.: is there a stable
>release that I could use instead?), but I don't know how to build it :-(
For the Tcl-only version, there's nothing to build.
For the C version, there is a quasi-TEA [*] build setup in
the 'src' subdirectory, so you *should* be able to run
cd src
sh configure
make
make install
>Any help appreciated (e.g., in the form of a .dsw file).
Is '.dsw' an MSVC thing or a Mac thing? If it's the latter
I can't help you, but for MSVC you could try copying 'Makefile.in'
to 'Makefile', edit it by hand to replace the @CONFIGVARS@
with their appropriate values on that platform, and run 'nmake'.
The file tcldom/src/Makefile.in is fairly simple [**], so this
shouldn't be an insurmountable task.
I'll take a closer look at this when I get in to the office
and have access to a Windows box; more later.
--Joe English
[*] I don't know if it's really TEA-compliant; Jeff Hobbs hasn't
said whether or not it compiles on his machine.
[**] which makes me suspect that it can't possibly be TEA-compliant
after all.
Christian Heide Damm
The .dsw is a MSVC thing, and I just got it working with help from a friend.
(this involved checking out tcldom+tclxml from CVS, because tcldom required a
tclexpat.lib - tclxml only had expat.lib, but that worked anyway).
Is it supposed to be this complicated?
Christian
--
Steve Ball
> Thanks for the answer.
>
> The .dsw is a MSVC thing, and I just got it working with help from a friend.
> (this involved checking out tcldom+tclxml from CVS, because tcldom required a
> tclexpat.lib - tclxml only had expat.lib, but that worked anyway).
>
> Is it supposed to be this complicated?
No, of course not. However, I haven't had the time to do the
release engineering necessary to make things easier.
Volunteers would be most appreciated.
Cheers,
Steve Ball
Pat Thoyts
>Hi,
>
>I have downloaded TclDOM from the SOAP project homepage, but it crashes,
>when I try to load it. Probably it was built for another tcl-version. I use
>8.4a2.
>
>I have checked out the latest TclDOM from CVS (btw.: is there a stable
>release that I could use instead?), but I don't know how to build it :-(
>
>Any help appreciated (e.g., in the form of a .dsw file).
Apologies - I probably built it against tcl8.3 and didn't use stubs.
It's pretty easy to build with Visual Studio really. I'll see if I
can't get around to rebuilding it with stubs.
lvi...@yahoo.com
According to Christian Heide Damm <da...@daimi.au.dk>:
:Is it supposed to be this complicated?
What? Life? Tcl? TclSOAP?
Life - it's pretty messy
Tcl - Nope, doing simple things should be simple, and complicated things
a bit more complicated.
TclSOAP - as people start using the package, and sending back to the
maintainers specific platform issues, as well as fixes, etc. it
would be expected to get easier as time goes by.
--
"I know of vanishingly few people ... who choose to use ksh." "I'm a minority!"
<URL: mailto:lvi...@cas.org> <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.
Cameron Laird
>
>According to Christian Heide Damm <da...@daimi.au.dk>:
>:Is it supposed to be this complicated?
>
>What? Life? Tcl? TclSOAP?
>
>Life - it's pretty messy
>Tcl - Nope, doing simple things should be simple, and complicated things
> a bit more complicated.
>TclSOAP - as people start using the package, and sending back to the
> maintainers specific platform issues, as well as fixes, etc. it
> would be expected to get easier as time goes by.
.
.
TclSOAP will indeed get easier.
However, it's important to say this very clearly: the
one language that makes beginning SOAP programming easiest
is ... Tcl! What happens with Java, Perl, VB, ... is even
more confusing for beginners. Python (and possibly Frontier
and PHP) actually have advantages for beginners over Tcl,
but not many, and they're not portable in the same way.
Here's how you, too, can be a SOAP programmer: install
ActiveTcl, write
package require SOAP
and you're in business. That's it. Compare that to Java,
for example, and it's really quite remarkable.
I'm not belittling Christian's problems in any way. His
questions are quite natural and legitimate, and illustrate
how much is left to do.
Pat's achievement with TclSOAP, and tclguy's in pushing for
BI, deserve great praise.