• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Tim Cooke
  • Devaka Cooray
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Mikalai Zaikin
Bartenders:
  • Carey Brown
  • Roland Mueller

Web Service parameter for large xml ?

 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,

I have implementing a web service with only one method, the method have to receive a 'large' xml as input parameter (let say ~60mb ). I have try to use string type, but following error found:

Unable to connect to URL: http://192.168.5.10:8988/ADF-ADFReceiver-context-root/MyWebService1SoapHttpPort due to java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html
09/01/21 14:34:26 ; nested exception is:
HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html


Is there any type (something like inputstream) that can be use as the web service input parameter? Please kinldy advise on this.
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

jerry king wrote:I have implementing a web service with only one method, the method have to receive a 'large' xml as input parameter (let say ~60mb ).


Replacing FTP wasn't part of the overall SOAP web service vision. Accomplishing this with a SOAP web service stack could require you to develop your own "chunking protocol". It is far simpler to
  • use FTP (after all, it was designed to "transfer files")
  • use a (HTTP) servlet-based solution that uses something like Commons FileUpload
  •  
    Paper jam tastes about as you would expect. Try some on this tiny ad:
    We need your help - Coderanch server fundraiser
    https://coderanch.com/wiki/782867/Coderanch-server-fundraiser
    reply
      Bookmark Topic Watch Topic
    • New Topic