Thank you Darren! This helped a great deal, and explained some other problems that I've had before. I just got to look now at what I did to generate that wsdl... I don't think we put the spaces in there on purpose?. Anyone else have similar problems?
-mick -----Original Message----- From: Darren Barefoot [mailto:[EMAIL PROTECTED]] Sent: Friday, July 05, 2002 2:57 AM To: [EMAIL PROTECTED] Subject: RE: Beautify your WSDL view... Hi, We had a quick look at your WSDL file and believe we've found the issue. If you open your WSDL file in a text editor, you'll find that the first line appears like this: <?xml That is, there are two spaces before the XML encoding declaration. This, according to the XML spec (specifically, http://www.w3.org/TR/2000/REC-xml-20001006#sec-guessing-no-ext-info), isn't legit. XML processors look for the XML encoding declaration in the first characters of an XML file. When they don't find it, the processor may fall over. This is what's occurred here. To confirm our theory, I've uploaded two versions of your WSDL on CapeScience, the original and one without spaces: http://www.capescience.com/temp/EmailSendBean.wsdl http://www.capescience.com/temp/EmailSendBean_no_spaces.wsdl If you feed them into our WSDL Transformer (http://www.capescience.com/webservices/wsdltransformer/), you'll see that the "no_spaces" WSDL file works where the original didn't. Hope that helps. Thanks. DB. Darren Barefoot Technology Evangelist CapeScience - Cape Clear's Developer Support Network http://www.capescience.com > -----Original Message----- > From: Mick Robinson [mailto:[EMAIL PROTECTED]] > Sent: 04 July 2002 18:01 > To: [EMAIL PROTECTED] > Subject: RE: Beautify your WSDL view... > > > > I was interested in using it, but I must be doing something > wrong, and I'd be really interested If you could point out > what the problem is to me... > > Here's what the results the processing gave me: > > Choked processing http://www.capescience.com/simplifiedwsdl.xslt > transforming http://66.119.161.80/WSDL/EmailSendBean.wsdl > With these parameters: > transform - Submit > xslfile - http://www.capescience.com/simplifiedwsdl.xslt > xmlfile - http://66.119.161.80/WSDL/EmailSendBean.wsdl > > org.xml.sax.SAXParseException: syntax error > at com.jclark.xml.sax.Driver.parse(Driver.java) > at > com.jclark.xsl.sax.XMLProcessorImpl.load(XMLProcessorImpl.java:632) > at > com.jclark.xsl.sax.XSLProcessorImpl.parse(XSLProcessorImpl.java:123) > at org.w3c.app.xsl.XSLtransformer.doGet(XSLtransformer.java:52) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:865) > at > org.w3c.jigsaw.servlet.ServletWrapper$ServletRunner.run(Servle > tWrapper.j > ava:524) > > > -----Original Message----- > From: Darren Barefoot [mailto:[EMAIL PROTECTED]] > Sent: Thursday, July 04, 2002 9:35 AM > To: [EMAIL PROTECTED] > Subject: Beautify your WSDL view... > > > Thought some of you might be interested in a utility we > recently posted called the WSDL Transformer. It basically > uses the XSLT servlet provided by the W3C to apply an XSLT > file and render your WSDL into a more Java-like, > user-friendly format. Just input your WSDL file at > http://www.capescience.com/webservices/wsdltra> nsformer/ and > away you go. > >
