HTTP 415 Unsupported Media Type with SOAP adapter ?

Hello All,
Iam getting  HTTP 415 Unsupported Media Type with SOAP adapter  error while executing the scenario.
i got one thread which have the solution. iam not getting exactly how to write message transform Bean.
HTTP 415 Unsupported Media Type with SOAP adapter trying to put SOAP header
Please tell me where i need to write the MessageTransformBean at sender adapter or receiver file adapter.
Thanks and regards,
chinna

Hi Chinna,
Have you checked this
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
Regards
Ramesh

Similar Messages

  • HTTP 415 Unsupported Media Type with SOAP adapter trying to put SOAP header

    Hello,
    I am trying to put data into soap header using soap receiver adapter. Seems like building the complete soap message is the right way to go. Thus I wrote a java program to build the complete soap message (soap envelop, soap header and soap body which contains the message PI received from the sender). Mapping program works well. However when I ran the scenario, I got Error "SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type" when calling the receiver's web service (the SOAP receiver adapter CC have the "Do Not use SOAP Envelop" checked). Anyone knows why I got this error? From google, seems like this error is because the http's content-type is set to other type, rather than "text/xml". However in soap CC there is no option to control this.
    The message sent to the receiver is (after mapping);
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
    <SOAP-SEC:Signature xmlns:SOAP-SEC="http://schemas.xmlsoap.org/soap/security/2000-12" MyAttr="value">My Test Value</SOAP-SEC:Signature>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
    <ns1:UpdateEquipment xmlns:ns1="http://mycomp.com/mywebservice">
    <ns1:EquipmentNumber>000000012345</ns1:EquipmentNumber>
    <ns1:LicensePlate>654321</ns1:LicensePlate>
    </ns1:UpdateEquipment>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Anyone can help?
    Thanks

    When you check "Do Not use SOAP Envelop", the SOAP adapter chooses application/xml instead of text/xml.
    You can change the content type with help of the MessageTransformBean. You put the bean in the module chain of the receiver channel and add the parameter Transform.ContentType = text/xml
    See
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/57/0b2c4142aef623e10000000a155106/frameset.htm

  • ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type

    Hi All,
    We have a Proxy to SOAP scenario which is throwing the below response.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type</SAP:AdditionalText>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    We have used XSLT mapping and also used the Message transform bean (ocalejbs/AF_Modules/MessageTransformBean) with the module parameters.
    Please help.

    this is the Audit log... Just in case this helps..
    20.10.2011 09:57:34 Information Transform: successfully transformed
    20.10.2011 09:57:34 Information MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    20.10.2011 09:57:34 Information SOAP: request message entering the adapter with user J2EE_GUEST
    20.10.2011 09:57:34 Information SOAP: completed the processing
    20.10.2011 09:57:34 Information SOAP: continuing to response message 765df5dd-fb23-11e0-a52b-0000124b6826
    20.10.2011 09:57:34 Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    20.10.2011 09:57:34 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    20.10.2011 09:57:34 Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    20.10.2011 09:57:34 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error. Setting message to status failed.
    20.10.2011 09:57:34 Error The message status was set to FAIL.

  • [RPC Fault faultString="HTTP/1.1 415 Unsupported Media Type" faultCode="Server.Proxy.Request.Failed"

    Hi,
    Posting in the 'General' forums as well. Did not yet get any response for the topic posted in the 'Configuration and Getting Started Discussion' forum.
    I am having nightmares to call the POST method of a REST service thru Flex. Initially tried with the HTTPService without any proxy server. Wasn't able to call POST, though the GET method was successfully called. Please see the post here (http://www.flexdeveloper.eu/forums/actionscript-3-0/how-to-acces-post-method-of-rest-web -service-thru-flex/)
    b THEN I tried with BlazeDS
    , but with the same results!
    I have set up BlazeDS with the integrated Tomcat option. I have also set up the Flex project as mentioned in the instructions. It is working fine when I run the sample projects.
    But the problem is that
    i when I try to access a
    b POST for a REST service,
    i I get the "HTTP/1.1 415 Unsupported Media Type" fault.
    b The complete fault I'm getting is: [RPC Fault faultString="HTTP/1.1 415 Unsupported Media Type" faultCode="Server.Proxy.Request.Failed" faultDetail="HTTP/1.1 415 Unsupported Media Type"]
    at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()[E:\dev \3.1.0\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:218]
    at mx.rpc::Responder/fault()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\rpc\Responder.as:53 ]
    at mx.rpc::AsyncRequest/fault()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\rpc\AsyncRequest .as:103]
    at HTTPMessageResponder/resultHandler()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\messagin g\channels\HTTPChannel.as:871]
    at HTTPMessageResponder/completeHandler()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\messag ing\channels\HTTPChannel.as:940]
    at ChannelRequestLoader/callEventCallback()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\mess aging\channels\HTTPChannel.as:1155]
    at ChannelRequestLoader/completeHandler()[E:\dev\3.1.0\frameworks\projects\rpc\src\mx\messag ing\channels\HTTPChannel.as:1191]
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at flash.net::URLLoader/onComplete()
    I have added correct entry to the policy-config.xml (I know this because the GET for the same REST service is working).
    b Only the POST thing is giving me the fault!
    Appreciate any inputs. (am in need of 'em badly)
    thanks
    BJG

    My guess is that the Server/Rest service doesn't like the content type of the request. HTTPService uses a content type of application/x-www-form-urlencoded by default. Maybe the Rest service is expecting the request to be XML? If that's the case, you need to set the contentType property of the HTTPService to application/xml.
    Sometimes an HTTP sniffer/proxy such as Charles can be useful for debugging these kinds of issues. If my suggestion doesn't help, capture the HTTP request and response using a HTTP sniffer like Charles and post back to this thread with it and someone will take a look at it for you. Thanks.
    -Alex

  • Unable to invoke endpoint uri : 415 unsupported media type

    Hi all,
    I'm trying to invoke a HTTP Binding with POST where the endpoint is a RESTFUL webservice that takes in an XML message and sends an email.
    I'm using JDeveloper 11g to create the composite where it'll have an exposed HTTP Binding POST and an external reference which is also a HTTP Binding POST that calls a RESTFUL Webservice endpoint . In the BPEL process, i'm just doing a simple receive from the exposed HTTP Binding and then using the input to invoke the External References HTTP Binding.  However, I'm always getting an error at the invoke phase :
    <part  name="summary">
    <summary>oracle.fabric.common.FabricInvocationException: Unable to invoke endpoint URI "http://xxxxxxxxx/xxxx/xxxx/sendEmail" successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Bad response: 415 Unsupported Media Type from url http://xxxxxxxxx/xxxx/xxxx/sendEmail</summary> 
    </part>
    <part  name="detail">
    <detail>Unable to invoke endpoint URI "http://xxxxxxxxx/xxxx/xxxx/sendEmail" successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Bad response: 415 Unsupported Media Type from url http://xxxxxxxxx/xxxx/xxxx/sendEmail</detail> 
    </part>
    <part  name="code">
    <code>415</code> 
    </part>
    I'm guessing that it's because my payload is lacking the HTTP header content-type : application/xml. The webservice endpoint itself is working fine as I'm able to test it through other means such as POSTMan and soapUI.
    Is there a way to set the HTTP header content-type of the payload? Is there anyway to check or verify? Any help would be greatly appreciated.
    Regards,
    Mark

    Hi all,
    I'm trying to invoke a HTTP Binding with POST where the endpoint is a RESTFUL webservice that takes in an XML message and sends an email.
    I'm using JDeveloper 11g to create the composite where it'll have an exposed HTTP Binding POST and an external reference which is also a HTTP Binding POST that calls a RESTFUL Webservice endpoint . In the BPEL process, i'm just doing a simple receive from the exposed HTTP Binding and then using the input to invoke the External References HTTP Binding.  However, I'm always getting an error at the invoke phase :
    <part  name="summary">
    <summary>oracle.fabric.common.FabricInvocationException: Unable to invoke endpoint URI "http://xxxxxxxxx/xxxx/xxxx/sendEmail" successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Bad response: 415 Unsupported Media Type from url http://xxxxxxxxx/xxxx/xxxx/sendEmail</summary> 
    </part>
    <part  name="detail">
    <detail>Unable to invoke endpoint URI "http://xxxxxxxxx/xxxx/xxxx/sendEmail" successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Bad response: 415 Unsupported Media Type from url http://xxxxxxxxx/xxxx/xxxx/sendEmail</detail> 
    </part>
    <part  name="code">
    <code>415</code> 
    </part>
    I'm guessing that it's because my payload is lacking the HTTP header content-type : application/xml. The webservice endpoint itself is working fine as I'm able to test it through other means such as POSTMan and soapUI.
    Is there a way to set the HTTP header content-type of the payload? Is there anyway to check or verify? Any help would be greatly appreciated.
    Regards,
    Mark

  • Getting 415 Unsupported Media Type error when calling a windows web service

    I have a BPEL process that invokes a windows web service. This process is working currently on the production system. When trying to run the process in a new test clustered environment, I'm getting the error below (bolded).
    We're using 10.1.3.3 Oracle Application Server and BPEL. Please advise on what config files might need to be tweaked to fix this.
    InvokeWindowsLoggingWebService(faulted)
    [2010/04/16 17:26:35] Faulted while invoking operation "WriteLog" on provider "WindowsLoggingWebService". less
    -<messages>
    -<input>
    -<InvokeWindowsLoggingWebService_InputVariable>
    -<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="parameters">
    -<WriteLog xmlns="http://tempuri.org/">
    <FileAbsolutePath>
    R:\CV & RM\upload_from_test.log
    </FileAbsolutePath>
    <Content>
    ||*************************************************************************************|Append to log file 2010-04-16T16:57:08-04:00|*************************************************************************************||START DATE: 2010-04-16T16:57:08-04:00|END DATE: 2010-04-16T17:25:58-04:00|COUNT: 106|TRANSFER OF FILES TO TAS SUCCESSFUL
    </Content>
    <NewLineDelimiter>
    |
    </NewLineDelimiter>
    </WriteLog>
    </part>
    </InvokeWindowsLoggingWebService_InputVariable>
    </input>
    -<fault>
    -<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    -<part name="summary">
    <summary>
    exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 415 Unsupported Media Type
    </summary>
    </part>
    </remoteFault>
    </fault>
    </messages>
    [2010/04/16 17:26:35] "{http://schemas.oracle.com/bpel/extension}remoteFault" has been thrown. less
    -<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    -<part name="summary">
    <summary>
    exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 415 Unsupported Media Type
    </summary>
    </part>
    </remoteFault>

    I generated a proxy service in jdev and used the same parms as was done on OAS...
    <WriteLog xmlns="http://tempuri.org/">
    <FileAbsolutePath>
    R:\CV & RM\upload_from_test.log
    </FileAbsolutePath>
    <Content>
    ||*************************************************************************************|Append to log file 2010-04-16T16:57:08-04:00|*************************************************************************************||START DATE: 2010-04-16T16:57:08-04:00|END DATE: 2010-04-16T17:25:58-04:00|COUNT: 106|TRANSFER OF FILES TO TAS SUCCESSFUL
    </Content>
    <NewLineDelimiter>
    |
    </NewLineDelimiter>
    </WriteLog>
    and was able to call the service fine and it returned successful. Just seems to be an issue on the server when I execute it from there.

  • PowerPoint Web App 415 Unsupported Media Type

    Hi,
    i had successfully deployed and configured external access via TMG to SharePoint 2013 with Office Web Apps 2013. Everything works fine, except PowerPoint Web App, when the farm is accessed externally. User becomes following error message:
    Either you´ve lost network connectivity or our server is too busy to handle your request. Please check your network connection and try again later. 
    PowerPoint Web App is working fine, when accessing SharePoint form local network or through VPN.
    Ive searched TMG Logs and found this 415 ERROR:
    Allowed Connection
    Log type: Web Proxy (Reverse)
    Status: 415 Unsupported Media Type
    Rule: (SERVER FQDN)
    Source: Internal ()
    Destination: Local Host ()
    Request: POST http://(SERVER FQDN)/p/ppt/view.https.svc/jsonNtlm/GetPresentation
    Filter information: Req ID: 0be8d6bf; Compression: client=Yes, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=yes, valid=yes, updated=no, logged off=no, client type=public, user activity=yes
    Protocol: https
    User: domain\name
    Additional information
    Client agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
    Object source: Internet (Source is the Internet. Object was added to the cache.)
    Cache info: 0x40020000 (Response includes the CACHE-CONTROL: PRIVATE header. Response should not be cached.)
    Processing time: 16 MIME type:
    Thank you for answers! 
    Regards
    Lubomir

    I'm going to move this to the TMG forum as it is more of a TMG-related issue (clearly WAC works fine when not taking TMG int account).
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Response code - 415 Unsupported Media Type

    Dear All,
    We are trying a scenario to simply receive data from one of our external partners, via HTTP, and save this data as a flat file within our landscape.
    As there is no mapping involved, no object is created/referred to in the integration repository.
    However, our partners get response "415 Unsupported Media Type" when sending data to us.
    Data that is being sent, has the following headers,
    Content-Type: application/text
    Content-Transfer-Encoding: binary
    Could one of you please help to resolve this issue?
    Kind Regards,
    Thomas.

    Could your sender system send the data in different Content-Type e.g. application/xml or text/xml. If not, then you need to use the MessageTransformBean to convert Content-Type: application/text to one of the above.
    http://help.sap.com/saphelp_nw04/helpdata/en/57/0b2c4142aef623e10000000a155106/frameset.htm
    Regards,
    Prateek

  • Add item to list gives : 415 - Unsupported Media Type

    Hello,
    I would like to add an item to a custom list using rest API.
    The request gave me : Unsupported Media Type
    I am using the list custom type name (SP.Data.%name%ListItem) as type in __metadata following the information here : http://msdn.microsoft.com/en-us/library/office/dn531433(v=office.15).aspx#bk_ListItem
    I am able to add attachments to an existing item but i can't add a new item.
    Do you have any idea?
    Thanks in advance.
    Regards,

    Rajesh,
    The error definitely says request sent by the client especially the content-type header is not a valid one. Check this trace and ask them to change accordingly:
    http://help.sap.com/saphelp_nw04/helpdata/en/8f/2f2c4142aef623e10000000a155106/content.htm
    Regards,
    ---Satish

  • 415 Unsupported Media Type - Inbound HTTP request

    Hi All,
      mY scanario is
      HTTP Request --> XI ---> FTP ( Without any IR objects..Just a file transfer )
    Whenever our partner is trying to post a file pI, they are gettig 415 unsupported type. They are using content type as application/text and we tried with as text/xml as well. No luck.
    Please adviice

    Rajesh,
    The error definitely says request sent by the client especially the content-type header is not a valid one. Check this trace and ask them to change accordingly:
    http://help.sap.com/saphelp_nw04/helpdata/en/8f/2f2c4142aef623e10000000a155106/content.htm
    Regards,
    ---Satish

  • Windows Web Services - Unsupported media type

    Hi,
    I'm trying to migrate a web service from .NET WCF to C++ Windows Web Services API. I generated .c and .h files using WSDL, create few wrappers and incorporated it into the C++ code and try it using a gSOAP client. Sadly, it wasn't working.
    Here is the response from the WWS:
    HTTP/1.1 415 Unsupported Media Type
    Server: Microsoft-HTTPAPI/2.0
    Date: Mon, 14 Jul 2014 10:50:23 GMT
    Connection: close
    Content-Length: 0
    I debug it for a while, and found out, that WWS apparentely cannot handle action parameter in Content-Type.
    Content-Type: text/xml; charset=utf-8; action="http://tempuri.org/IReferenceClockWebService/SetRecordTimeLeftDiff"
    After I remove the action parameter, everything is working.
    Why is this happening. Isn't an action parameter common part of SOAP HTTP requests? Is there any workaround?
    Thanks in advance.

    Hi,
    I'm trying to migrate a web service from .NET WCF to C++ Windows Web Services API. I generated .c and .h files using WSDL, create few wrappers and incorporated it into the C++ code and try it using a gSOAP client. Sadly, it wasn't working.
    Here is the response from the WWS:
    HTTP/1.1 415 Unsupported Media Type
    Server: Microsoft-HTTPAPI/2.0
    Date: Mon, 14 Jul 2014 10:50:23 GMT
    Connection: close
    Content-Length: 0
    I debug it for a while, and found out, that WWS apparentely cannot handle action parameter in Content-Type.
    Content-Type: text/xml; charset=utf-8; action="http://tempuri.org/IReferenceClockWebService/SetRecordTimeLeftDiff"
    After I remove the action parameter, everything is working.
    Why is this happening. Isn't an action parameter common part of SOAP HTTP requests? Is there any workaround?
    Thanks in advance.

  • Unsupported Content-Type: application/soap+xml

    I've created a simple composite application with a bpel jbi module using glassfishesbv21.
    The bpel process starts when I invoke a webservice (soap-binding).
    When I run a test case for the ca everything works fine.
    When I call the webservice from an external web application, the client (created with netbeans wizard bundled in glassfishesbv21) obtains the response as expected and doesn't report any exception while the server rises a com.sun.xml.ws.server.UnsupportedMediaException.
    Googoling I found that this maybe caused by the use of soap1.1 and soap1.2 but is also true that JAX-WS runtime should look into the WSDL to determine the binding being used and configures itself accordingly.
    the stacktrace is:
    Finished processing outbound messages.
    Request doesnt have a Content-Type
    com.sun.xml.ws.server.UnsupportedMediaException: Request doesnt have a Content-Type
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:267)
    at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
    at com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:341)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:386)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:220)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:647)
    at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
    at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
    com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
    ====[com.sun.xml.ws.assembler.server:request]====
    <?xml version="1.0" ?>
    <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">
    <soap-env:Header>
    <wsa:Action>http://schemas.xmlsoap.org/ws/2004/09/transfer/Get</wsa:Action>
    <wsa:To>http://localhost:19081/coreAnagrafeUpdateService/coreAnagrafeUpdatePort</wsa:To>
    <wsa:ReplyTo>
    <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
    </wsa:ReplyTo>
    <wsa:MessageID>uuid:778b135f-3fdf-44b2-b53e-ebaab7441e40</wsa:MessageID>
    </soap-env:Header>
    <soap-env:Body></soap-env:Body>
    </soap-env:Envelope>
    ============
    ====[com.sun.xml.ws.assembler.server:response]====
    <?xml version="1.0" ?>
    <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    <S:Body>
    <S:Fault xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns="">
    <faultcode>S:Server</faultcode>
    <faultstring>javax.jbi.messaging.MessagingException: HTTPBC-E00798: Message normalization failed</faultstring>
    </S:Fault>
    </S:Body>
    </S:Envelope>
    ============
    Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
    com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
    ====[com.sun.xml.ws.assembler.server:request]====
    <?xml version="1.0" ?>
    <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">
    <soap-env:Header>
    <wsa:Action>http://schemas.xmlsoap.org/ws/2004/09/transfer/Get</wsa:Action>
    <wsa:To>http://localhost:19081/coreAnagrafeUpdateService/coreAnagrafeUpdatePort/mex</wsa:To>
    <wsa:ReplyTo>
    <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
    </wsa:ReplyTo>
    <wsa:MessageID>uuid:778b135f-3fdf-44b2-b53e-ebaab7441e40</wsa:MessageID>
    </soap-env:Header>
    <soap-env:Body></soap-env:Body>
    </soap-env:Envelope>
    ============
    the wsdl is:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <definitions name="coreAnagrafeUpdateService"
    targetNamespace="http://service.box.nexus.com/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:tns="http://service.box.nexus.com/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <types>
         <xsd:schema>
    <xsd:import namespace="http://service.box.nexus.com/" schemaLocation="core_anagrafe.xsd"/>
    </xsd:schema>
    </types>
    <message name="coreAnagrafeUpdateOperationRequest">
    <part name="parameters" element="tns:requestParameter"/>
    </message>
    <message name="coreAnagrafeUpdateOperationResponse">
    <part name="parameters" element="tns:coreAnagrafeResponse"/>
    </message>
    <message name="coreAnagrafeUpdateOperationFault">
    <part name="part1" element="tns:faultMessage"/>
    </message>
    <portType name="coreAnagrafeUpdatePortType">
    <operation name="coreAnagrafeUpdateOperation">
    <input message="tns:coreAnagrafeUpdateOperationRequest"/>
    <output message="tns:coreAnagrafeUpdateOperationResponse"/>
    <wsdl:fault name="fault1" message="tns:coreAnagrafeUpdateOperationFault"/>
    </operation>
    </portType>
    <binding name="coreAnagrafeUpdateBinding" type="tns:coreAnagrafeUpdatePortType">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    <operation name="coreAnagrafeUpdateOperation">
    <soap:operation soapAction=""/>
    <input>
    <soap:body use="literal" />
    </input>
    <output>
    <soap:body use="literal" />
    </output>
    <wsdl:fault name="fault1">
    <soap:fault use="literal" name="fault1"/>
    </wsdl:fault>
    </operation>
    </binding>
    <service name="coreAnagrafeUpdateService">
    <port name="coreAnagrafeUpdatePort" binding="tns:coreAnagrafeUpdateBinding">
    <soap:address location="http://localhost:19081/coreAnagrafeUpdateService/coreAnagrafeUpdatePort"/>
    </port>
    </service>
    </definitions>
    Can anyone help me to understand the problem and solve it?
    Thanks in advance.

    Hi,
    Content-Type: application/xml
    ...check for the content type of the message that is sent ot the WS.....with the above mentioned content-type going to the WS currently...WS is not able to parse the req and hence the error....in other words wrong format being being passed.
    Regards,
    ABhishek.

  • Prolog with soap adapter in PI

    Dear All,
    We run a scenario Proxy=>PI=>HTTP
    The remote service accepts messages POSTed using either the form-encoded format (name, value pairs)
    or the multi-part mime format which enables the files to be passed to the web service.
    In both cases, the external service replies with a multi-part message.
    We are going to use the SOAP adapter (plain HTTP does not support attachments)
    with nosoap flagged.
    What is best approach to add a prolog before the actual XML with SOAP adapter,
    to simulate the form-encoded format?
    Example :
    USER=USER1&PASS=PASS1&DB=DB1
    In the 2nd situation, how to create the different documents before the actual XML?
    Example :
    7d924f5b0464
    Content-Disposition: form-data; name="USER"
    USER1
    7d924f5b0464
    Content-Disposition: form-data; name="PASS"
    PASS1
    7d924f5b0464
    Content-Disposition: form-data; name="DB"
    DB1
    Best regards,
    KR,
    Laurent

    Dear All,
    We run a scenario Proxy=>PI=>HTTP
    The remote service accepts messages POSTed using either the form-encoded format (name, value pairs)
    or the multi-part mime format which enables the files to be passed to the web service.
    In both cases, the external service replies with a multi-part message.
    We are going to use the SOAP adapter (plain HTTP does not support attachments)
    with nosoap flagged.
    What is best approach to add a prolog before the actual XML with SOAP adapter,
    to simulate the form-encoded format?
    Example :
    USER=USER1&PASS=PASS1&DB=DB1
    In the 2nd situation, how to create the different documents before the actual XML?
    Example :
    7d924f5b0464
    Content-Disposition: form-data; name="USER"
    USER1
    7d924f5b0464
    Content-Disposition: form-data; name="PASS"
    PASS1
    7d924f5b0464
    Content-Disposition: form-data; name="DB"
    DB1
    Best regards,
    KR,
    Laurent

  • Message Level Security with SOAP Adapter

    Hi,
    I need to use Message Level Security with my SOAP Adapter. Please let me know if anyone has done the same in the past?
    What are the steps I would need to do? How can I use WSS based security in the SOAP Adapter?

    Hi,
    Message-level security is recommended and sometimes a prerequisite for inter-enterprise communication.
    It improves communication-level security by adding security features that are particularly important for inter-enterprise
    Message-level encryption is required if message content needs to be confidential not only on the communication lines but also in intermediate message stores.
    Refer
    How to use Client Authentication with SOAP Adapter
    XML Encryption Using Web Services Security in SAP NetWeaver XI
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0650f56-7587-2910-7c99-e1b6ffbe4d50
    http://help.sap.com/saphelp_nw04/helpdata/en/a8/882a40ce93185de10000000a1550b0/frameset.htm
    Thanks
    swarup

  • Unsupported media type:application/vnd.rim.cod

    Hullo!
     I have a Blackberry Curve 8320, and am trying to download the new (and apparantly award-winning) Nimbuzz IM client to my phone via their site at http://get.nimbuzz.com  but am getting an error when I try.
     First I am told "The item you selected cannot be displayed. Do you wish to save the item?"  If I select No, I get "Unsupported media type:application/vnd.rim.cod"
     Saving the file "Nimbuzz-1.cod" and then trying to Explore to it and launch it doesn't seem to do any good either.
     I was pretty sure .cod files are the correct file type for this sort of thing, and I can't find anything on the Internet about this error message, or anyone else experiencing this problem. 
      Please help!

    Hi Im having the same problem, and i havent found anything about it. Did you fix it? can you please tell me how?
    Thanks

Maybe you are looking for