This discussion is archived
1 Reply Latest reply: Jul 30, 2009 9:32 AM by 843830 RSS

Request doesnt have a Content-Type in webservice

843830 Newbie
Currently Being Moderated
When i access the webservice via webservice client code below exception is came in the hosted side.

Other details are
1.Webservice client was created using JAXWS.
2.Webservice is access via the ESB layer.
3.webservices are hosted in Glassfish server

[#|2009-05-13T18:24:25.654+0530|SEVERE|sun-appserver9.1|com.sun.xml.ws.transport.http.HttpAdapter|_ThreadID=31;_ThreadName=httpWorkerThread-8085-1;_RequestID=2a76f011-614d-45a7-adde-1267f1463a8a;|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:373)
     at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:228)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
     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)
  • 1. Re: Request doesnt have a Content-Type in webservice
    843830 Newbie
    Currently Being Moderated
    Hi,

    Could you please get more clear on your question. if i am right you are saying
    You are using a webservice that is called in BPEL, and you created an CASA Application ,
    now you are calling this deployed CASA. and you are getting exception.

    When you create CASA you have to define a SOAP address of the soap node in CASA files. and you have to call that link which u have provide in the soap node(WSDL PORT).
    or you can define that soap address in wsdl which is created in BPEL module.


    Thanks

    Kumar