Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 25939 invoked from network); 20 Nov 1999 05:57:40 -0000 Received: from adsl-209-76-108-112.dsl.snfc21.pacbell.net (HELO helium.brownell.org) (209.76.108.112) by apache.org with SMTP; 20 Nov 1999 05:57:40 -0000 Received: from pacbell.net (xenon [10.0.0.101]) by helium.brownell.org (Postfix) with ESMTP id 258546F93 for ; Fri, 19 Nov 1999 21:52:17 -0800 (PST) Message-ID: <38363853.FC29A671@pacbell.net> Date: Fri, 19 Nov 1999 21:57:39 -0800 From: David Brownell Organization: Yoyodyne Systems Labs X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en,fr MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: Tomcat on IBM OS/390? References: <00b001bf32e8$41305030$3e880118@msnv1.occa.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Preston L. Bannister" wrote: > > Result with encoding="EBCDIC-CP-US" in all *.xml and *.dtd files: The diagnostics suggest breakage still ... as if the XML declaration didn't take. Specifically, as if the files started something like xml ... rather than (again, all in EBCDIC) Configuring web service using "default" > config parse: can't read config: SAXParseException: null : 1 > msg : Character conversion error: "Unconvertible UTF-8 character beginning with 0xa7" (line number may be too low). Strange -- but then, parser diagnostics got mangled on the way out, last time I needed to look at that stuff. Costin, you never applied that patch I sent you to ensure that the right diagnostic information got presented ... do you still have that? I think that some of the changes over the past few weeks broke it. For example, "default" isn't a filename ... > Configuring web service using "file:/nsa/users/bannisp/nsa/Jakarta/build/tomcat/webpages/WEB-INF/web.xml" > config parse: can't read config: SAXParseException: null : 1 > msg : Character conversion error: "Unconvertible UTF-8 character beginning with 0xa7" (line number may be too low). > Configuring web service using "default" > config parse: can't read config: SAXParseException: null : 1 > msg : Character conversion error: "Unconvertible UTF-8 character beginning with 0xa7" (line number may be too low). > Configuring web service using "file:/nsa/users/bannisp/nsa/Jakarta/build/tomcat/examples/WEB-INF/web.xml" > config parse: can't read config: SAXParseException: null : 1 > msg : Character conversion error: "Unconvertible UTF-8 character beginning with 0xa7" (line number may be too low). > Starting tcp endpoint on 8080 with org.apache.tomcat.service.http.HttpConnectionHandler > Starting tcp endpoint on 8007 with org.apache.tomcat.service.Ajp11ConnectionHandler > Starting tcp endpoint on 8009 with org.apache.tomcat.service.connector.Ajp12ConnectionHandler > Starting tcp endpoint on 8008 with org.apache.tomcat.service.connector.Ajp23ConnectionHandler > --- > > It's running!! ... but I wonder if it's using some compiled-in default instead of anything you gave it.