1. JAX RPC jaxrpc-ri.xml coderanch.comAll, I've recently published an Axis service and all is fine and well with it -- but I'm now exploring JAXRPC for both client and server devlopment. Sun hasn't done much in the way of explaining the jaxrpc-ri.xml document as best I can tell -- perhaps someone can clarify? Specifically, I'm wondering exactly what targetNamespaceBase, typeNamespaceBase, and urlPatternBase are doing here. ... |
2. JAX:RS Annotarions in XML coderanch.com |
3. com.sun.xml.ws.server.UnsupportedMediaException: Request doesnt have a Content-Type in JAXWS client coderanch.comWhen i access the webservice via 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.Glassfish is used in webservice hosting [#|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) ... |