It's a nice idea, but tcllib is harder to install than TWiST and contains a lot of code that probably doesn't need to be in tcllib, it would not be easy to remove just the typing code either.
The model I used was as an AOLserver Tcl module. Installation only requires that you place tWSDL as a child directory of the private Tcl library for the virtual server, and then add a line to the config file telling AOLserver about the module.
The API was written so that it depended very little (one proc) on AOLserver, so you could replace AOLserver. However, I haven't found an easy replacement for AOLserver. If I do find such a replacement, there is a tiny abstraction package I need to write for a few ns_* commands, similar to the ones already there for ns_log. Also, TWiST can run from a tclsh, I use nstclsh which is part of AOLserver. Obviously you can't do an <ws>return, but you can create types, and set a few variables and then generate a WSDL, along with the commands to create and validate the SOAP messages.
Hmm, that suggests that what I really need here is a <ws>server command to go along with an abstracted <ws>return command, then the <ws>server command would be like calling nsd.
But my idea for OpenACS is the TWiST OpenACS package available either at google code:
http://code.google.com/p/twsdl/downloads/list
or on my test server:
http://junom.com/openacs/
The OpenACS TWiST package is only 3.2K and makes TWiST even easier to install on OpenACS than it is to install into AOLserver (without editing any files on disk). But it does depend on either 1) subversion, or 2) also downloading the latest TWiST tagged and tar.gz'd file at googlecode downloads.
And best of all, if you don't need it, it isn't there taking up any space.
