See: 
http://en.wikibooks.org/wiki/WebObjects/Web_Services/Common_Pitfalls_and_Troubleshooting

SAXParseException when using HTTPS

If, in WebObjects 5.4.x, you get an exception connecting to your web service 
via HTTPS (through the WebObjects Apache adaptor) and get an error like the 
following:

 org.xml.sax.SAXParseException: Premature end of file.
   at 
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown 
Source
   at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
   at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown 
Source))
     ... more
You will need to add additional information to the file server.wsdd to tell 
Apache AXIS what to do when it believes the transport mechanism is 'https.' 
AXIS will make this determination based on the HTTP header information 
forwarded by the Apache WebObjects adaptor. If no entry is made to tell AXIS 
how to handle 'https', it will assume the incoming data from the adaptor is 
encrypted via SSL, even though the communication between the adaptor and the 
instance is in the clear. To change the behavior of AXIS, change the file 
server.wsdd from:

<transport name="http">
 <requestFlow>
  <handler type="HTTPActionHandler"/>
  <handler type="URLMapper"/>
 </requestFlow>
</transport>
To:

<transport name="http">
 <requestFlow>
  <handler type="HTTPActionHandler"/>
  <handler type="URLMapper"/>
 </requestFlow>
</transport>
<transport name="https">
 <requestFlow>
  <handler type="HTTPActionHandler"/>
  <handler type="URLMapper"/>
 </requestFlow>
</transport>
Thanks for all the HELP!
PS: and the Wiki page!
JR
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to