Hi David, Thanks for the answer, Am Mittwoch, 10. August 2005 21:31 schrieb David N. Welton: > Arnulf Wiedemann wrote: > > Sorry I should have been more specific: I found that message in the > > apache error_log file. > > As respone within my Tcl SOAP request I get: > > > > debug ok - HTTP/1.1 500 Internal Server Error > > ERROR:MSG:Server response is not well-formed XML. > > response was <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > > <HTML><HEAD> > > <TITLE>500 Internal Server Error</TITLE> > > </HEAD><BODY> > > <H1>Internal Server Error</H1> > > The server encountered an internal error or > > misconfiguration and was unable to complete > > your request.<P> > > This is indicative that perhaps things aren't even set up right, or that > something is really having troubles internally. > > > I am using the following Tcl Script: > > > > #!/bin/sh > > # \ > > exec ~/ActiveTcl/bin/tclsh "$0" "$@" > > > > set vn [package require SOAP] > > puts stderr "vn:$vn:" > > > > SOAP::setLogLevel debug > > > > > > SOAP::create AntragNeu \ > > -proxy "http://localhost:8083/soaptest.ttml"; \ > > -params {"Mandant" "" "Prozess" "" "Aussteller" ""} \ > > -action "AntragNeu" \ > > > > > > if {[catch {set ret [::AntragNeu 5 P "5as"]} msg]} { > > puts stderr "ERROR:MSG:$msg:$::errorInfo:" > > } else { > > puts stderr "ret:$ret:" > > } > > > > The suffix .ttml is configured the same as .rvt. > > Ok... so far so good... > > > What I want to do is process a POST request which has some xml stuff in > > it. The processing can be done using tclxml, but the problem is, that I > > do not get the contents of that request to process it within the > > .ttml/.rvt file. The contents is normally placed in the request, that > > after having called hgetvars, I have it in the VARS array. > > I'd use 'var get' these days, but that shouldn't be a problem. I will use that in the future > > >>headers type "text/xml" > > > > That is what the tclSOAP package is producing. > > Yes, but your Rivet page may need to return a text/xml page, no? Or is > plain HTML ok? > Yes, I have to return a text/xml page (if I get the contents of the request first). > > Here is the output, if I am removing the -type text/xml parameter from > > the SOAP Request (that is what I want to get in the other case too): > > Aha! Ok, I think I am starting to get it after seeing this, too: > ::http::geturl http://localhost:8083/soaptest.ttml -headers {SOAPAction > > {"AntragNeu"}} -type text/xml > <==== here is the difference > -timeout 0 -query {<?xml version="1.0"?> > <SOAP-ENV:Envelope > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:xsd="http://www.w3.org/1999/XMLSchema"; > xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";><SOAP-ENV:Body><Antra >gNeu><Mandant>5</Mandant><Prozess>P</Prozess> > <Aussteller>5as</Aussteller></AntragNeu></SOAP-ENV:Body></SOAP-ENV:Envelope >> } > > You basically want to send that over as query data and have the Rivet > script grab it 'as is' yes.
And having the contents of the request 'as is', I have to build a text/xml answer, but that's the second step and I have an idea on how to do that. > > > debug ok - HTTP/1.1 200 OK > > ERROR:MSG:Server response is not well-formed XML. > > response was VARS: > > <?xml version:"1.0"?> > > <SOAP-ENV:Envelope > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; xm > > lns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; > > SOAP-ENV:encodingStyle= > > "http://schemas.xmlsoap.org/soap/encoding/"; > > xmlns:xsd="http://www.w3.org/1999/XM > > LSchema" > > xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";><SOAP-ENV:Body><A > > ntragNeu><Mandant>5</Mandant><Prozess>P</Prozess><Aussteller>5as</Ausstel > >ler></A ntragNeu></SOAP-ENV:Body></SOAP-ENV:Envelope> > > <br> > > > > That is the contents of the .ttml file: > > <? > > hgetvars > > puts "VARS:" > > foreach name [array names VARS] { > > puts "$name:$VARS($name)<br>" > > } > > ?> > > So what we need for you is a way to get the raw, unparsed data, it looks > like. It's not there yet, but I'll see what I can do... I don't think > it should be terribly difficult. I am awaiting your answer, if you have found out a solution. Thanks in advance, Arnulf --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
