Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices)
I have been using various tools (SOAPclient and HTTPtester) and here's what I am getting Request is OK, as follows User-Agent: Mac OS X; WebServicesCore.framework (1.0.0) Content-Type: text/xml Soapaction: http://localhost/nees.wws Host: localhost But **response** is in error, sending back Content-Type: text/html instead of text/xml HTTP/1.1 200 OK Connection: close Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 OpenSSL/0.9.7l DAV/2 Content-Type: text/html Date: Wed, 05 Mar 2008 11:15:54 GMT Set-Cookie: Witango_UserReference=F4E923AA5841685247CE80EA; path=/ Transfer-Encoding: Identity What I can't figure out is how to set up Witango (and/or Apache 2.2.6) to send back the RESPONSE to a .wws call as XML The WSDL file starts out with ?xml version=1.0 encoding=UTF-8 ? so I presumed that would be enough I tried to add content-type headers for the tcfs providing the data, but that corrupted the process I experimented with the mime.types but only succeeded in killing all webservices Any ideas or solutions? TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
RE: Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices)
I am by no means an expert here, and I am not sure what you are trying to do... but I have set up variuos rss feeds in xml and I have had to rewrite all the headers to the following before I could get it to work... @purgeresults@ASSIGN local$httpHeader VALUE=Content-Type:text/xml@CRLF@USERREFERENCECOOKIE@CRLF (no returns in the above) This may not even apply to you... just thought I would throw it out there. _ From: Dale Graham [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2008 5:20 AM To: Witango-Talk list Subject: Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices) I have been using various tools (SOAPclient and HTTPtester) and here's what I am getting Request is OK, as follows User-Agent: Mac OS X; WebServicesCore.framework (1.0.0) Content-Type: text/xml Soapaction: http://localhost/nees.wws Host: localhost But **response** is in error, sending back Content-Type: text/html instead of text/xml HTTP/1.1 200 OK Connection: close Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 OpenSSL/0.9.7l DAV/2 Content-Type: text/html Date: Wed, 05 Mar 2008 11:15:54 GMT Set-Cookie: Witango_UserReference=F4E923AA5841685247CE80EA; path=/ Transfer-Encoding: Identity What I can't figure out is how to set up Witango (and/or Apache 2.2.6) to send back the RESPONSE to a .wws call as XML The WSDL file starts out with ?xml version=1.0 encoding=UTF-8 ? so I presumed that would be enough I tried to add content-type headers for the tcfs providing the data, but that corrupted the process I experimented with the mime.types but only succeeded in killing all webservices Any ideas or solutions? TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
Re: Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices)
Dale, Did you use the apache AddType and AddCharset directives in your virtual host stanza and/or .htaccess file? I presume you already have an AddHandler directive for your .wws files. I would try these out in an .htaccess file first so you can easily play around without interrupting other services. --bill On Mar 5, 2008, at 6:20 AM, Dale Graham wrote: I have been using various tools (SOAPclient and HTTPtester) and here's what I am getting Request is OK, as follows User-Agent: Mac OS X; WebServicesCore.framework (1.0.0) Content-Type: text/xml Soapaction: http://localhost/nees.wws Host: localhost But **response** is in error, sending back Content-Type: text/html instead of text/xml HTTP/1.1 200 OK Connection: close Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 OpenSSL/0.9.7l DAV/2 Content-Type: text/html Date: Wed, 05 Mar 2008 11:15:54 GMT Set-Cookie: Witango_UserReference=F4E923AA5841685247CE80EA; path=/ Transfer-Encoding: Identity What I can't figure out is how to set up Witango (and/or Apache 2.2.6) to send back the RESPONSE to a .wws call as XML The WSDL file starts out with ?xml version=1.0 encoding=UTF-8 ? so I presumed that would be enough I tried to add content-type headers for the tcfs providing the data, but that corrupted the process I experimented with the mime.types but only succeeded in killing all webservices Any ideas or solutions? TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
Re: Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices)
When 5.5 came out, we were excited about its built in ws feature. That lasted about a week. I spent a month or so, working out the best and most efficient method for webservices in witango. I made a simple template, that we used to make hundreds of webservices, all of them in production in heavy load environments. This method is careful not to use looping to generate xml. You can download the template, and a document explaining my methodologies at: http://www.bighead.net/tools/download.taf Here is the meat of it: @assign local$outstyle 'xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform xsl:output method=xml encoding=ISO-8859-1 indent=yes/ xsl:strip-space elements=*/ xsl:template match=* xsl:copy xsl:copy-of select=@* / xsl:apply-templates / /xsl:copy /xsl:template /xsl:stylesheet' @assign local$tempstyle 'xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform xsl:output method=xml omit-xml-declaration =yes indent=no/ xsl:strip-space elements=*/ xsl:template match=* xsl:copy xsl:copy-of select=@* / xsl:apply-templates / /xsl:copy /xsl:template xsl:template match=event xsl:for-each select=//event/Row event xsl:attribute name=rowid xsl:value-of select=@id / /xsl:attribute xsl:copy-of select=./* / /event /xsl:for-each /xsl:template /xsl:stylesheet' @comment The tempstyle above, and the local array to convert to dom needs to be changed to match the name you want for Node name for your data. /@comment @assign local$labServiceInclusions @var local$resultSet @arraytodom array=local$labServiceInclusions @assign local$thexml @dom 'EPXSWServiceResponse /' @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendsuccess1/success/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendreason@literal Authorization Successful. encoding=cdata/reason/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendstatus1/status/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendrowCount@numrows array=local$resultSet/rowCount/ @dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse@replace str='@xslt local$labServiceInclusions stylesheet=@var local $tempstyle' findstr='\?.+\?' replacestr='' type=regex/@dominsert @! output of xslt is string, so it applies xslt and outputs as text @assign local$result '@xslt local$thexml stylesheet=@var local $outstyle' @assign local$cLen @length @var local$result @assign local$httpResponse false Then the next acction is the header, but notice the response variable above, this must be set to false. @purgeresults@assign local$httpHeader HTTP/1.1 200 OK@crlfServer: WiTango 5.5.009@crlfMIME-Version: 1.0@crlfContent- Type: text/xml;charset=utf-8@crlfContent-length: @var local $cLen@crlfX-Timer: @timer@CRLF@CRLF Then finally, return the data: @var local$result encoding=none We have a few old clients still running like this, but all the heavy hitting ws's are now in php. But I can tell you the above worked, and worked well, AS LONG AS you had no high byte characters in your xml data. NOTE: the template you download from my site, uses UTF-8 declaration, but should be the above, ISO-8859-1. No matter what, you can't get witango 5.5 to properly output UTF-8. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Mar 5, 2008, at 3:20 AM, Dale Graham wrote: I have been using various tools (SOAPclient and HTTPtester) and here's what I am getting Request is OK, as follows User-Agent: Mac OS X; WebServicesCore.framework (1.0.0) Content-Type: text/xml Soapaction: http://localhost/nees.wws Host: localhost But **response** is in error, sending back Content-Type: text/html instead of text/xml HTTP/1.1 200 OK Connection: close Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 OpenSSL/0.9.7l DAV/2 Content-Type: text/html Date: Wed, 05 Mar 2008 11:15:54 GMT Set-Cookie: Witango_UserReference=F4E923AA5841685247CE80EA; path=/ Transfer-Encoding: Identity What I can't figure out is how to set up Witango (and/or Apache 2.2.6) to send back the RESPONSE to a .wws call as XML The WSDL file starts out with ?xml version=1.0 encoding=UTF-8 ? so I presumed that would be enough I tried to add content-type headers for the tcfs providing the data, but that corrupted the process I experimented with the mime.types but only succeeded in killing all webservices Any ideas or solutions? TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
Re: Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices)
Change the content type declaration to iso-8859-1 also. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Mar 5, 2008, at 7:36 AM, Robert Garcia wrote: When 5.5 came out, we were excited about its built in ws feature. That lasted about a week. I spent a month or so, working out the best and most efficient method for webservices in witango. I made a simple template, that we used to make hundreds of webservices, all of them in production in heavy load environments. This method is careful not to use looping to generate xml. You can download the template, and a document explaining my methodologies at: http://www.bighead.net/tools/download.taf Here is the meat of it: @assign local$outstyle 'xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform xsl:output method=xml encoding=ISO-8859-1 indent=yes/ xsl:strip-space elements=*/ xsl:template match=* xsl:copy xsl:copy-of select=@* / xsl:apply-templates / /xsl:copy /xsl:template /xsl:stylesheet' @assign local$tempstyle 'xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform xsl:output method=xml omit-xml-declaration =yes indent=no/ xsl:strip-space elements=*/ xsl:template match=* xsl:copy xsl:copy-of select=@* / xsl:apply-templates / /xsl:copy /xsl:template xsl:template match=event xsl:for-each select=//event/Row event xsl:attribute name=rowid xsl:value-of select=@id / /xsl:attribute xsl:copy-of select=./* / /event /xsl:for-each /xsl:template /xsl:stylesheet' @comment The tempstyle above, and the local array to convert to dom needs to be changed to match the name you want for Node name for your data. /@comment @assign local$labServiceInclusions @var local$resultSet @arraytodom array=local$labServiceInclusions @assign local$thexml @dom 'EPXSWServiceResponse /' @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendsuccess1/success/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendreason@literal Authorization Successful. encoding=cdata/reason/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendstatus1/status/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendrowCount@numrows array=local$resultSet/ rowCount/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse@replace str='@xslt local$labServiceInclusions stylesheet=@var local $tempstyle' findstr='\?.+\?' replacestr='' type=regex/ @dominsert @! output of xslt is string, so it applies xslt and outputs as text @assign local$result '@xslt local$thexml stylesheet=@var local $outstyle' @assign local$cLen @length @var local$result @assign local$httpResponse false Then the next acction is the header, but notice the response variable above, this must be set to false. @purgeresults@assign local$httpHeader HTTP/1.1 200 OK@crlfServer: WiTango 5.5.009@crlfMIME-Version: 1.0@crlfContent-Type: text/xml;charset=utf-8@crlfContent-length: @var local$cLen@crlfX-Timer: @timer@CRLF@CRLF Then finally, return the data: @var local$result encoding=none We have a few old clients still running like this, but all the heavy hitting ws's are now in php. But I can tell you the above worked, and worked well, AS LONG AS you had no high byte characters in your xml data. NOTE: the template you download from my site, uses UTF-8 declaration, but should be the above, ISO-8859-1. No matter what, you can't get witango 5.5 to properly output UTF-8. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Mar 5, 2008, at 3:20 AM, Dale Graham wrote: I have been using various tools (SOAPclient and HTTPtester) and here's what I am getting Request is OK, as follows User-Agent: Mac OS X; WebServicesCore.framework (1.0.0) Content-Type: text/xml Soapaction: http://localhost/nees.wws Host: localhost But **response** is in error, sending back Content-Type: text/html instead of text/xml HTTP/1.1 200 OK Connection: close Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 OpenSSL/0.9.7l DAV/2 Content-Type: text/html Date: Wed, 05 Mar 2008 11:15:54 GMT Set-Cookie: Witango_UserReference=F4E923AA5841685247CE80EA; path=/ Transfer-Encoding: Identity What I can't figure out is how to set up Witango (and/or Apache 2.2.6) to send back the RESPONSE to a .wws call as XML The WSDL file starts out with ?xml version=1.0 encoding=UTF-8 ? so I presumed that would be enough I tried to add content-type headers for the tcfs providing the data, but that corrupted the process I experimented with the mime.types but only succeeded in killing all webservices Any ideas
Re: Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices)
Thanks! I will try this out. On Mar 5, 2008, at 10:42 AM, Robert Garcia wrote: Change the content type declaration to iso-8859-1 also. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Mar 5, 2008, at 7:36 AM, Robert Garcia wrote: When 5.5 came out, we were excited about its built in ws feature. That lasted about a week. I spent a month or so, working out the best and most efficient method for webservices in witango. I made a simple template, that we used to make hundreds of webservices, all of them in production in heavy load environments. This method is careful not to use looping to generate xml. You can download the template, and a document explaining my methodologies at: http://www.bighead.net/tools/download.taf Here is the meat of it: @assign local$outstyle 'xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform xsl:output method=xml encoding=ISO-8859-1 indent=yes/ xsl:strip-space elements=*/ xsl:template match=* xsl:copy xsl:copy-of select=@* / xsl:apply-templates / /xsl:copy /xsl:template /xsl:stylesheet' @assign local$tempstyle 'xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform xsl:output method=xml omit-xml-declaration =yes indent=no/ xsl:strip-space elements=*/ xsl:template match=* xsl:copy xsl:copy-of select=@* / xsl:apply-templates / /xsl:copy /xsl:template xsl:template match=event xsl:for-each select=//event/Row event xsl:attribute name=rowid xsl:value-of select=@id / /xsl:attribute xsl:copy-of select=./* / /event /xsl:for-each /xsl:template /xsl:stylesheet' @comment The tempstyle above, and the local array to convert to dom needs to be changed to match the name you want for Node name for your data. /@comment @assign local$labServiceInclusions @var local$resultSet @arraytodom array=local$labServiceInclusions @assign local$thexml @dom 'EPXSWServiceResponse /' @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendsuccess1/success/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendreason@literal Authorization Successful. encoding=cdata/reason/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendstatus1/status/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendrowCount@numrows array=local$resultSet/ rowCount/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse@replace str='@xslt local$labServiceInclusions stylesheet=@var local $tempstyle' findstr='\?.+\?' replacestr='' type=regex/ @dominsert @! output of xslt is string, so it applies xslt and outputs as text @assign local$result '@xslt local$thexml stylesheet=@var local $outstyle' @assign local$cLen @length @var local$result @assign local$httpResponse false Then the next acction is the header, but notice the response variable above, this must be set to false. @purgeresults@assign local$httpHeader HTTP/1.1 200 OK@crlfServer: WiTango 5.5.009@crlfMIME-Version: 1.0@crlfContent-Type: text/xml;charset=utf-8@crlfContent- length: @var local$cLen@crlfX-Timer: @timer@CRLF@CRLF Then finally, return the data: @var local$result encoding=none We have a few old clients still running like this, but all the heavy hitting ws's are now in php. But I can tell you the above worked, and worked well, AS LONG AS you had no high byte characters in your xml data. NOTE: the template you download from my site, uses UTF-8 declaration, but should be the above, ISO-8859-1. No matter what, you can't get witango 5.5 to properly output UTF-8. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Mar 5, 2008, at 3:20 AM, Dale Graham wrote: I have been using various tools (SOAPclient and HTTPtester) and here's what I am getting Request is OK, as follows User-Agent: Mac OS X; WebServicesCore.framework (1.0.0) Content-Type: text/xml Soapaction: http://localhost/nees.wws Host: localhost But **response** is in error, sending back Content-Type: text/html instead of text/xml HTTP/1.1 200 OK Connection: close Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 OpenSSL/0.9.7l DAV/2 Content-Type: text/html Date: Wed, 05 Mar 2008 11:15:54 GMT Set-Cookie: Witango_UserReference=F4E923AA5841685247CE80EA; path=/ Transfer-Encoding: Identity What I can't figure out is how to set up Witango (and/or Apache 2.2.6) to send back the RESPONSE to a .wws call as XML The WSDL file starts out with ?xml version=1.0 encoding=UTF-8 ? so I presumed that would be enough I tried to add content-type headers for the tcfs providing the data, but that corrupted the process I
Re: Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices)
I am testing on my local server so I can cheerfully bungle as much stuff as I like.8) But I want to be sure I am doing this correctly... AddType yes In Apache 2.2.6 has to go in mime.types and I have Witango set like this application/witango-application-file taf tml thtml tcf wws AddCharset appears in the httpd-languages.conf file for 2.2.6 UTF directives are already there (all kinds of them). Do I need anything else? AddHandler... wouldn't that already be covered by the AddType directions? and if so, what would I put? On Mar 5, 2008, at 10:13 AM, William Conlon wrote: Dale, Did you use the apache AddType and AddCharset directives in your virtual host stanza and/or .htaccess file? I presume you already have an AddHandler directive for your .wws files. I would try these out in an .htaccess file first so you can easily play around without interrupting other services. --bill On Mar 5, 2008, at 6:20 AM, Dale Graham wrote: I have been using various tools (SOAPclient and HTTPtester) and here's what I am getting Request is OK, as follows User-Agent: Mac OS X; WebServicesCore.framework (1.0.0) Content-Type: text/xml Soapaction: http://localhost/nees.wws Host: localhost But **response** is in error, sending back Content-Type: text/html instead of text/xml HTTP/1.1 200 OK Connection: close Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 OpenSSL/0.9.7l DAV/2 Content-Type: text/html Date: Wed, 05 Mar 2008 11:15:54 GMT Set-Cookie: Witango_UserReference=F4E923AA5841685247CE80EA; path=/ Transfer-Encoding: Identity What I can't figure out is how to set up Witango (and/or Apache 2.2.6) to send back the RESPONSE to a .wws call as XML The WSDL file starts out with ?xml version=1.0 encoding=UTF-8 ? so I presumed that would be enough I tried to add content-type headers for the tcfs providing the data, but that corrupted the process I experimented with the mime.types but only succeeded in killing all webservices Any ideas or solutions? TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf -- Dale Graham, PhD Technical Manager, NIDB NIH Intramural DataBase Annual Reports, NIH Bibliography, Scientific Directory [EMAIL PROTECTED] TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
RE: Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices)
NOTE: the template you download from my site, uses UTF-8 declaration, but should be the above, ISO-8859-1. No matter what, you can't get witango 5.5 to properly output UTF-8. Robert, An update done in 5.5.020 was to add a UTF-8 conversion to @CIPHER. This: @CIPHER action=encode str=@VAR xml_text_block type=utf-8 seems to work as advertised. I have a customer who is returning data to Google using this encoding and it is being accepted normally. I saw that you listed the version in your header as 5.5.009, so I'm not sure that you've ever seen that command. Robert TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
Re: Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices)
Yes, when 020 came out, I did test it, still didn't work reliably. If you included high byte chars, and did it, they still got messed up. There is a possibility, that with more time, I could have gotten it to work, but we had already started porting to php, and now that is done. Also, even though witango added this quick feature, witango still is poorly suited for working with UTF-8, this just helped somewhat. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Mar 5, 2008, at 9:41 AM, Robert Shubert wrote: NOTE: the template you download from my site, uses UTF-8 declaration, but should be the above, ISO-8859-1. No matter what, you can't get witango 5.5 to properly output UTF-8. Robert, An update done in 5.5.020 was to add a UTF-8 conversion to @CIPHER. This: @CIPHER action=encode str=@VAR xml_text_block type=utf-8 seems to work as advertised. I have a customer who is returning data to Google using this encoding and it is being accepted normally. I saw that you listed the version in your header as 5.5.009, so I’m not sure that you’ve ever seen that command. Robert TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
Re: Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices)
I used your templates, got xml output of my data, etc. (Template/ explanations were GREAT) However, when called, it is STILL outputting in text/html. Source looks great, I am thrilled, but I cannot get it to my client... it HAS to come over as text/xml for his application. That's the bit I really need to fix. It's the OUTPUT that's thwarting me. Here's what httptester says about it.. HTTP/1.1 200 OK Date: Wed, 05 Mar 2008 18:18:58 GMT Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 OpenSSL/0.9.7l DAV/2 Set-Cookie: Witango_UserReference=B1B1522D002A6BAA47CEE412; path=/ Connection: close Content-Type: text/html That is, I am calling it as the taf, e.g., http://localhost/webservices/wstemplate.taf?nedid=1113311619 As I presumed from your explanation that you weren't using a wsdl file. On Mar 5, 2008, at 10:36 AM, Robert Garcia wrote: When 5.5 came out, we were excited about its built in ws feature. That lasted about a week. I spent a month or so, working out the best and most efficient method for webservices in witango. I made a simple template, that we used to make hundreds of webservices, all of them in production in heavy load environments. This method is careful not to use looping to generate xml. You can download the template, and a document explaining my methodologies at: http://www.bighead.net/tools/download.taf Here is the meat of it: @assign local$outstyle 'xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform xsl:output method=xml encoding=ISO-8859-1 indent=yes/ xsl:strip-space elements=*/ xsl:template match=* xsl:copy xsl:copy-of select=@* / xsl:apply-templates / /xsl:copy /xsl:template /xsl:stylesheet' @assign local$tempstyle 'xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform xsl:output method=xml omit-xml-declaration =yes indent=no/ xsl:strip-space elements=*/ xsl:template match=* xsl:copy xsl:copy-of select=@* / xsl:apply-templates / /xsl:copy /xsl:template xsl:template match=event xsl:for-each select=//event/Row event xsl:attribute name=rowid xsl:value-of select=@id / /xsl:attribute xsl:copy-of select=./* / /event /xsl:for-each /xsl:template /xsl:stylesheet' @comment The tempstyle above, and the local array to convert to dom needs to be changed to match the name you want for Node name for your data. /@comment @assign local$labServiceInclusions @var local$resultSet @arraytodom array=local$labServiceInclusions @assign local$thexml @dom 'EPXSWServiceResponse /' @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendsuccess1/success/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendreason@literal Authorization Successful. encoding=cdata/reason/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendstatus1/status/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendrowCount@numrows array=local$resultSet/ rowCount/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse@replace str='@xslt local$labServiceInclusions stylesheet=@var local $tempstyle' findstr='\?.+\?' replacestr='' type=regex/ @dominsert @! output of xslt is string, so it applies xslt and outputs as text @assign local$result '@xslt local$thexml stylesheet=@var local $outstyle' @assign local$cLen @length @var local$result @assign local$httpResponse false Then the next acction is the header, but notice the response variable above, this must be set to false. @purgeresults@assign local$httpHeader HTTP/1.1 200 OK@crlfServer: WiTango 5.5.009@crlfMIME-Version: 1.0@crlfContent-Type: text/xml;charset=utf-8@crlfContent-length: @var local$cLen@crlfX-Timer: @timer@CRLF@CRLF Then finally, return the data: @var local$result encoding=none We have a few old clients still running like this, but all the heavy hitting ws's are now in php. But I can tell you the above worked, and worked well, AS LONG AS you had no high byte characters in your xml data. NOTE: the template you download from my site, uses UTF-8 declaration, but should be the above, ISO-8859-1. No matter what, you can't get witango 5.5 to properly output UTF-8. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Mar 5, 2008, at 3:20 AM, Dale Graham wrote: I have been using various tools (SOAPclient and HTTPtester) and here's what I am getting Request is OK, as follows User-Agent: Mac OS X; WebServicesCore.framework (1.0.0) Content-Type: text/xml Soapaction: http://localhost/nees.wws Host: localhost But **response** is in error, sending back Content-Type: text/html instead of text/xml HTTP/1.1 200 OK Connection: close Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 OpenSSL/0.9.7l DAV/2 Content-Type: text/html Date: Wed, 05 Mar 2008 11:15:54 GMT Set-Cookie:
Re: Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices)
Bummer. Those are my settings, too. I do think it's Apache, but when I tinker with the mime types to deliver xml, it breaks either webservices or (worse) witango. I'll keep Googling around and if I come up with anything useful, share it with the list. Thanks, anyway, I really appreciated the input. On Mar 5, 2008, at 1:46 PM, Robert Garcia wrote: 2 things, here are my settings from my witango.ini ENCODEHTTPRESPONSE=false ENCODERESULTHTML=false ENCODERESULTSHTML=false If that doesn't help, then apache is definitely overwriting the content-type header. We used IIS and didn't have that issue. Whether this is an issue of the apache plugin, or apache itself, not sure. I can tell you how to make sure the header is right with php and apache, but php and apache work together much more closely. It seems to me that with witango, its more of just a hand-off. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Mar 5, 2008, at 10:25 AM, Dale Graham wrote: I used your templates, got xml output of my data, etc. (Template/ explanations were GREAT) However, when called, it is STILL outputting in text/html. Source looks great, I am thrilled, but I cannot get it to my client... it HAS to come over as text/xml for his application. That's the bit I really need to fix. It's the OUTPUT that's thwarting me. Here's what httptester says about it.. HTTP/1.1 200 OK Date: Wed, 05 Mar 2008 18:18:58 GMT Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 OpenSSL/0.9.7l DAV/2 Set-Cookie: Witango_UserReference=B1B1522D002A6BAA47CEE412; path=/ Connection: close Content-Type: text/html That is, I am calling it as the taf, e.g., http://localhost/webservices/wstemplate.taf?nedid=1113311619 As I presumed from your explanation that you weren't using a wsdl file. On Mar 5, 2008, at 10:36 AM, Robert Garcia wrote: When 5.5 came out, we were excited about its built in ws feature. That lasted about a week. I spent a month or so, working out the best and most efficient method for webservices in witango. I made a simple template, that we used to make hundreds of webservices, all of them in production in heavy load environments. This method is careful not to use looping to generate xml. You can download the template, and a document explaining my methodologies at: http://www.bighead.net/tools/download.taf Here is the meat of it: @assign local$outstyle 'xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform xsl:output method=xml encoding=ISO-8859-1 indent=yes/ xsl:strip-space elements=*/ xsl:template match=* xsl:copy xsl:copy-of select=@* / xsl:apply-templates / /xsl:copy /xsl:template /xsl:stylesheet' @assign local$tempstyle 'xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform xsl:output method=xml omit-xml-declaration =yes indent=no/ xsl:strip-space elements=*/ xsl:template match=* xsl:copy xsl:copy-of select=@* / xsl:apply-templates / /xsl:copy /xsl:template xsl:template match=event xsl:for-each select=//event/Row event xsl:attribute name=rowid xsl:value-of select=@id / /xsl:attribute xsl:copy-of select=./* / /event /xsl:for-each /xsl:template /xsl:stylesheet' @comment The tempstyle above, and the local array to convert to dom needs to be changed to match the name you want for Node name for your data. /@comment @assign local$labServiceInclusions @var local$resultSet @arraytodom array=local$labServiceInclusions @assign local$thexml @dom 'EPXSWServiceResponse /' @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendsuccess1/success/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendreason@literal Authorization Successful. encoding=cdata/reason/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendstatus1/status/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendrowCount@numrows array=local$resultSet/ rowCount/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse@replace str='@xslt local$labServiceInclusions stylesheet=@var local $tempstyle' findstr='\?.+\?' replacestr='' type=regex/ @dominsert @! output of xslt is string, so it applies xslt and outputs as text @assign local$result '@xslt local$thexml stylesheet=@var local $outstyle' @assign local$cLen @length @var local$result @assign local$httpResponse false Then the next acction is the header, but notice the response variable above, this must be set to false. @purgeresults@assign local$httpHeader HTTP/1.1 200 OK@crlfServer: WiTango 5.5.009@crlfMIME-Version: 1.0@crlfContent-Type: text/xml;charset=utf-8@crlfContent- length: @var local$cLen@crlfX-Timer: @timer@CRLF@CRLF Then finally, return the data: @var local$result encoding=none We have a few old clients
Re: Witango-Talk: Sigh. STILL having issues with XML not being returned (webservices)
I'm confused. Are you still trying to get your .wws file to output with a text/xml content type header? Can you create an .htaccess file that applies to the directory containing a problematic file, and apply to AddType, AddHandler, AddCharset directives and see what happens as you change them. If you're using a taf, which is normally output as text/html, then you need to override the header in witango, as Robert G showed in his example. bill On Mar 5, 2008, at 2:16 PM, Dale Graham wrote: Bummer. Those are my settings, too. I do think it's Apache, but when I tinker with the mime types to deliver xml, it breaks either webservices or (worse) witango. I'll keep Googling around and if I come up with anything useful, share it with the list. Thanks, anyway, I really appreciated the input. On Mar 5, 2008, at 1:46 PM, Robert Garcia wrote: 2 things, here are my settings from my witango.ini ENCODEHTTPRESPONSE=false ENCODERESULTHTML=false ENCODERESULTSHTML=false If that doesn't help, then apache is definitely overwriting the content-type header. We used IIS and didn't have that issue. Whether this is an issue of the apache plugin, or apache itself, not sure. I can tell you how to make sure the header is right with php and apache, but php and apache work together much more closely. It seems to me that with witango, its more of just a hand-off. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Mar 5, 2008, at 10:25 AM, Dale Graham wrote: I used your templates, got xml output of my data, etc. (Template/ explanations were GREAT) However, when called, it is STILL outputting in text/html. Source looks great, I am thrilled, but I cannot get it to my client... it HAS to come over as text/xml for his application. That's the bit I really need to fix. It's the OUTPUT that's thwarting me. Here's what httptester says about it.. HTTP/1.1 200 OK Date: Wed, 05 Mar 2008 18:18:58 GMT Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 OpenSSL/0.9.7l DAV/2 Set-Cookie: Witango_UserReference=B1B1522D002A6BAA47CEE412; path=/ Connection: close Content-Type: text/html That is, I am calling it as the taf, e.g., http://localhost/webservices/wstemplate.taf?nedid=1113311619 As I presumed from your explanation that you weren't using a wsdl file. On Mar 5, 2008, at 10:36 AM, Robert Garcia wrote: When 5.5 came out, we were excited about its built in ws feature. That lasted about a week. I spent a month or so, working out the best and most efficient method for webservices in witango. I made a simple template, that we used to make hundreds of webservices, all of them in production in heavy load environments. This method is careful not to use looping to generate xml. You can download the template, and a document explaining my methodologies at: http://www.bighead.net/tools/download.taf Here is the meat of it: @assign local$outstyle 'xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform xsl:output method=xml encoding=ISO-8859-1 indent=yes/ xsl:strip-space elements=*/ xsl:template match=* xsl:copy xsl:copy-of select=@* / xsl:apply-templates / /xsl:copy /xsl:template /xsl:stylesheet' @assign local$tempstyle 'xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xsl:output method=xml omit-xml-declaration =yes indent=no/ xsl:strip-space elements=*/ xsl:template match=* xsl:copy xsl:copy-of select=@* / xsl:apply-templates / /xsl:copy /xsl:template xsl:template match=event xsl:for-each select=//event/Row event xsl:attribute name=rowid xsl:value-of select=@id / /xsl:attribute xsl:copy-of select=./* / /event /xsl:for-each /xsl:template /xsl:stylesheet' @comment The tempstyle above, and the local array to convert to dom needs to be changed to match the name you want for Node name for your data. /@comment @assign local$labServiceInclusions @var local$resultSet @arraytodom array=local$labServiceInclusions @assign local$thexml @dom 'EPXSWServiceResponse /' @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendsuccess1/success/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendreason@literal Authorization Successful. encoding=cdata/reason/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendstatus1/status/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse position=appendrowCount@numrows array=local$resultSet/ rowCount/@dominsert @dominsert local$thexml xpath=/EPXSWServiceResponse@replace str='@xslt local$labServiceInclusions stylesheet=@var local $tempstyle' findstr='\?.+\?' replacestr='' type=regex/ @dominsert @! output of xslt is string, so it applies xslt and outputs as text @assign local$result '@xslt local$thexml stylesheet=@var local
Witango-Talk: In need of a Witango architecture consultant
OK, I put out a similar request a few months ago that was nixed by my management. However, I have finally convinced them that we need to have someone come in and look at our setup of Witango (currently 2 windows servers and a SQL server box) We are experiencing slow execution of Witango programs. This may be related to any one or all of the following: 1. Poor programming 2. Setup of servers 3. Communication issues between Witango Servers and SQL Server 4. Gremlins I need someone who will be available for 3 days on site. No remote entry possible. You have to be a US citizen and you have to be on site. Airfare, hotel, car rental, meals and your daily rate are all covered. Florida is a great place to visit in March, especially if you're from one of the northern climates. We are looking for someone who has set up multiple Witango servers, has gotten them running efficiently, has experience with Witango in a Windows and SQL Server environment, etc. We're talking Windows Server 2003, SQL Server 2000 and Witango Professional 5.5. I'd like to have someone in here yesterday. Please contact me off list. Gene Wolf Supervisor, Business Systems DRS Sensors Targeting Systems-Optronics 2330 Commerce Park Drive NE Palm Bay, Florida 32905 Phone: 321-309-0685 321-309-0202 (fax) Dictionary.com Word of the Day http://dictionary.reference.com/wordoftheday/ This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior written approval from the U.S. Department of State. TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
