I tried to use G.Lester's WebServices package with no success.
I have no doubt about the quality of this package but i can't manage to
get the right libraries to put it to work.
tDOM is required. I found what is supposed to be the latest version
(0.8.0) at http://www.tdom.org/
BUT this code does not work
# works great
dom parse $wsdlXML wsdlDoc
$wsdlDoc documentElement wsdlNode
# crash
$wsdlDoc selectNodesNamespaces {
w http://schemas.xmlsoap.org/wsdl/
d http://schemas.xmlsoap.org/wsdl/soap/
s http://www.w3.org/2001/XMLSchema
}
because the selectNodesNamespaces method is not defined for document
objects in tDOM 0.8.0.
I took a look at the current ActiveTcl package. It includes a tDOM
library with the missing
selectNodesNamespaces method (well i can figure this because of the
related documentation).
So where can i find a working (latest ?) tDOM distribution with sources
? (i need to compile it myself in order to install it on older linux
workstations and various UNIX systems) .
Thanks a lot.
Yes, you need 0.8.1 (I'll added the version number required to the
WebServices documentation).
Did you try pulling from the CVS mentioned on http://www.tdom.org/?
Myself, I just used the tDOM 0.8.1 from ActiveState.
Also, it may be appropriate to ask the question on the tDOM mailing list at:
http://groups.yahoo.com/group/tdom/ (as mentioned on http://www.tdom.org/).
As a last resort, send an email to Mr. Hobbs at ActiveState asking where he
got the sources from.
--
+--------------------------------+---------------------------------------+
| Gerald W. Lester |
|"The man who fights for his ideals is the man who is alive." - Cervantes|
+------------------------------------------------------------------------+
The latest actual release. There is newer code in cvs.
>
> So where can i find a working (latest ?) tDOM distribution with sources
> ? (i need to compile it myself in order to install it on older linux
> workstations and various UNIX systems) .
Try a cvs checkout from the cvs mentioned on www.tdom.org. There may be
problems during compile if you have a too new bash 3.x, because some of
the build support files have not been upgraded yet, but those can be
fixed by using more up to date tclconfig files and rerunning autoconf,
which can be checked out from the cvs of the tcl project at sourceforge
(module tclconfig).
If you have further problems with building tdom, either ask here or on
the tdom mailing list.
Michael
Why not also to the 'package require tdom'?
Michael
Turns out that the 0.8.0 build (at least some cases) labeled itself as 080,
which is actually "later" than 0.8.1.
Now I could do an -exact, but I'd like to pick up any fixes that come out
later without having to re-release my code.
Also, it appears that less than 10% of the people grabbing the package are
attempting to use the older 0.8.0 -- most people just seem to use the AS Tcl
bundle.
In fact the other one attempted to use the 0.8.0 *after* getting everything
to work with AS when he discovered the production version of his product
used the 0.8.0 version. I believe he modified my code to do the -exact to
get around the problem with the mislabeled tDOM.
Michael
Thanks to the fast answers i received i made the tDOM upgrade from
0.8.0 to 0.8.1 with CVS.
Now everything's ok ! Thanks a lot for your !GREAT! work.
Thanks to all for your help !
It sure would be nice if the official version of tdom wasn't > 2 years
old...
>From tdom.org:
"The latest tDOM source release is tDOM-0.8.0 (866k gzip tar archive,
2004-08-11)."
Why, that just means it is stable -- or do you know of features it is missing.
One of the reasons a lot of products/packages in languages like Java change
a lot is to fix all of the bugs and add all of the missing features.
>>From tdom.org:
> "The latest tDOM source release is tDOM-0.8.0 (866k gzip tar archive,
> 2004-08-11)."
>
In fact the tdom version included in the ActiveState distribution is
newer than the offically released version.
But talking with Rolf Ade on the chat some days ago he said he will
release an updated version when his current workload allows it.
One main reason is the breakage of the configure script with a new bash
3.x, which exposed a long existing quoting bug in the tclconfig tcl.m4 file.
There are also some small TEA woes that have to be solved:
http://sourceforge.net/tracker/index.php?func=detail&aid=1540729&group_id=10894&atid=110894
Michael