Hi,
It appeared very easy to integrate tclws and oacs...
I use (logical) tcl interp because tclws uses global variables.
Note that WS definition is done only during the first http request
to that webservice (probably when wsdl is read by client toolkit).
Of course tclws tcl package must be loadable for oacs...
If we want to install WS "wsexample" in oacs package "qqq1",
then we should put file below in qqq1/www:
----------------------------------------
## using tclws from oacs (wsexample.vuh file)
#
#catch {interp delete tclws_qqq1_wsexample}; # dbg
proc tclws_eval args {uplevel $args}
if {![interp exists tclws_qqq1_wsexample]} {
interp create tclws_qqq1_wsexample
# name of an interp: tclws_oacsPackageName_WSName
# "qqq1" is a name of oacs package with WS "wsexample"
tclws_qqq1_wsexample alias x tclws_eval
tclws_qqq1_wsexample alias ns_return ns_return
tclws_qqq1_wsexample eval {
# only at the beginning
set prefix "/przyklad1/qqq1/wsexample"
set service "wsexample"
set host "myserver:myportnumber"
proc log {x y} {x ns_log $x $y}
namespace eval log {}
proc log::log {x y} {x ns_log $x $y}
package re WS::Server
package re WS::AOLserver
::WS::Server::Service -mode aolserver \
-prefix $prefix -service $service -host $host \
-description {oacs + tclws example}
::WS::Server::ServiceProc $service {razyDwa {type int()}} {
par1 {type int() comment {a sequence of ints}}
} {multiply by 2 an input sequence of ints} {
set w {}
foreach e $par1 {lappend w [expr {$e*2}]}
return [list razyDwaResult $w]
}
log notice "WebService $service definition..."
}
}
tclws_qqq1_wsexample eval {
# for every http request
set reqType [x ad_conn path_info]
if {$reqType=="/"||$reqType==""} {set reqType "/doc"}
switch -exact -- $reqType {
/doc {
WS::Server::generateInfo $service nosock
}
/wsdl {
WS::Server::generateWsdl $service nosock
log notice "WS::Server::generateWsdl $service nosock"
}
/op {
upvar #0 Httpdnosock data
set data(ipaddr) [x ad_conn peeraddr]
set data(headerlist) [x ns_set array [x ad_conn headers]]
set data(query) [x ad_conn content]
WS::Server::callOperation $service nosock
log notice "WS::Server::callOperation $service nosock"
}
}
}
----------------------------------------
And here is an example how to use that webserwise
from client-side of tclws toolkit:
-------------------------------------
set headers "Cookie ad_session_id=???"
# + ad_session_id must be somehow reveived (?)
package re WS::Client
#% 2.3.7
set w1 [::WS::Client::GetAndParseWsdl http://myserver:myportnumber/przyklad1/qqq1/wsexample/wsdl $headers]
dict get $w1 name
#% wsexample
# + this is a name of our WS
::WS::Client::CreateStubs wsexample
#%
::wsexample::razyDwa par1
wsexample::razyDwa {1 2 3 4 5 6}
#% razyDwaResult {2 4 6 8 10 12}
--------------------------------------------
...............
best regards,
Michal Hanckowiak
