Ask a Question related to Coldfusion - Advanced Techniques, Design and Development.
-
Ken Kolodziej #1
Web Services: SAX Parser Issue
Hello,
I am having an issue instantiating a component as a web service. The
component contains one function (to return a copy of itself) and 27
<cfproperty> tags, of which 20 are simple data types (numeric, string and
boolean), and of which 7 are components. The principle component initializes
perfectly when instantiated normally (i.e. not as a web service), and the wsdl
files for the component, as well as for all sub-components, are generated
without error. Also, all other components I have created that follow the same
general design (i.e. cfproperty tags and one function) work flawlessly; these
components, however, are much smaller, containing not more than 6 or 8
properties, one of which may be a component.
A friend suggested that perhaps ColdFusion is not escaping, or is not
replacing, reserved XML characters when preparing the component for
consumption, fooling SAX into expecting more data when, in fact, there is none.
I created a work-around, which is essentially a stripped-down version of the
component in question without sub-components and with fewer properties which
works fine, but this issue will keep bugging me until I resolve it, a feeling
I'm sure everyone knows all too well!
I should also mention that I'm running the developer edition of MX 7 on a
Windows machine as a standalone, not on a J2EE server. The error also crops up
on our hosting company's shared CF 7 box.
Any help would be greatly appreciated.
- Ken
An excerpt from the detailed error message follows:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXParseException: Premature end of file.
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException:
Premature end of file.
at org.apache.xerces.util.ErrorHandlerWrapper.createS AXParseException(Unknown
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalEr ror(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportErro r(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportErro r(Unknown Source)
at org.apache.xerces.impl.XMLVersionDetector.determin eDocVersion(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse (Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse (Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse( Unknown Source)
at javax.xml.parsers.SAXParser.parse(U...
Ken Kolodziej Guest
-
weird issue with web services
hello one of our clients reported the following error when attempting to use our service component in some asp page. the component connects to... -
Web Services that returns XML - SAX Issue!
From my CFMX7 application, I make a call to a Java Web service that returns me the following SOAP message: <?xml version="1.0" encoding="UTF-8"?>... -
Web Services using custom types - issue as it is redefining them in the proxy class generated.
This one is simple. The WSDL that is generated by your service expresses a wire format contract. This contract assumes that the implementation... -
Terminal Services Issue
Hi, Im running Windows 2003 Server whit Terminal Services in Remote Administration Mode. Since a few days when I'try to connect with Remote... -
ASP.NET Web Services. Web Method CacheDuration Issue.
Hello All. Can someone tell me quickly whether web method level caching is effective for both internal calls AND calls via HTTP/SOAP. I am...



Reply With Quote

