facebook

[Closed] Web Service Explorer has Issues?

  1. MyEclipse Archived
  2.  > 
  3. Web Services
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #265677 Reply

    Russ
    Member

    I have a Simple Web Service that deploys to JBoss 4.0.5. This web service was created earlier and ported over to MyEclipse. We are doing a hot deployment to JBoss and a simple jax-rpc service call.

    I can see the web service WSDL and I can see the service is creating the SOAP Message for sending, but it never makes it to the Server as it fails in the creating of the SOAPMessage.

    This is the error I am getting:

    
    [13:22:28,074] [DEBUG] [SOAPFaultException] [new SOAPFaultException [code={http://schemas.xmlsoap.org/soap/envelope/}Client,string=setProperty must be overridden by all subclasses of SOAPMessage,actor=null,detail=null]]
    [13:22:28,074] [ERROR] [SOAPFaultExceptionHelper] [SOAP request exception]
    java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
    

    I do not see where this issue is anything I am doing with the web service because I am using the Web Service Explorer. Is there an issue with Eclipse? I do not see any errors from the pde runtime error log.

    Thank you for reading my post. Any suggestions would be greatly appreciated.

    Russ

    #265690 Reply

    Russ
    Member

    The issue is JDK1.6 related!!!

    http://www.jboss.com/index.html?module=bb&op=viewtopic&t=99036 Once I changed the JDK, it worked fine

    #265765 Reply

    Russ
    Member

    Okay, I swapped out the JDK to 1.5.11 and got pass the original issue.

    What is happening now is the Explorer is having problems. When I send the message I received this error. This is not related to what my application is doing. Note this is strictly a XML message in the payload with no attachments. This is a simple JAX-RPC web service.

    
    13:29:41,681] [DEBUG] [SOAPMessage] [Incomming SOAPMessage
    <soapenv:Envelope xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
    <soapenv:Header/>
    <soapenv:Body>
    <ns0:getDepartments xmlns:ns0='http://workflow.company.com/'>
    <userId>me</userId>
    <operId>me_pwd</operId>
    </ns0:getDepartments></soapenv:Body></soapenv:Envelope>]
    
    

    This is the error I and getting when I send the message:

    
    [13:29:42,196] [ERROR] [[WebServiceImpl]] [Servlet.service() for servlet WebServiceImpl threw exception]
    java.lang.ExceptionInInitializerError
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:164)
        at org.jboss.ws.soap.attachment.ContentHandlerRegistry.<clinit>(ContentHandlerRegistry.java:51)
        at org.jboss.ws.xop.XOPUnmarshallerImpl.<clinit>(XOPUnmarshallerImpl.java:59)
        at org.jboss.ws.jaxrpc.encoding.SimpleDeserializer.deserialize(SimpleDeserializer.java:52)
        at org.jboss.ws.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:235)
        at org.jboss.ws.binding.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:233)
        at org.jboss.ws.binding.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:103)
        at org.jboss.ws.binding.EndpointInvocation.getRequestPayload(EndpointInvocation.java:117)
        at org.jboss.ws.server.ServiceEndpointInvokerJSE.invokeServiceEndpoint(ServiceEndpointInvokerJSE.java:94)
        at org.jboss.ws.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:115)
        at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:209)
        at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355)
        at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
        at org.apache.catalina.valves.FastCommonAccessLogValve.invoke(FastCommonAccessLogValve.java:495)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
        at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
        at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
        at java.lang.Thread.run(Thread.java:595)
    Caused by: java.lang.IllegalArgumentException: failed to parse:image/bmp, image/x-bmp, image/x-windows-bmp
        at java.awt.datatransfer.DataFlavor.<init>(DataFlavor.java:292)
        at javax.activation.ActivationDataFlavor.<init>(ActivationDataFlavor.java:81)
        at org.jboss.ws.soap.attachment.ImageDataContentHandler.buildFlavors(ImageDataContentHandler.java:77)
        at org.jboss.ws.soap.attachment.ImageDataContentHandler.<clinit>(ImageDataContentHandler.java:63)
        ... 37 more
    

    Any suggestions? When I go looking at JBoss, they have issues when sending attachments.

    #265771 Reply

    Riyad Kalla
    Member

    Russ I’m gonna see if Brian has any insight into this.

    #265975 Reply

    Russ
    Member

    Is Brian around or is he tied up? I haven’t heard from you guys on over five days….

    #265976 Reply

    Riyad Kalla
    Member

    He is definitely busy, I just pinged him to see if he’s still alive, sorry for the wait.

    #265988 Reply

    Brian Fernandes
    Moderator

    Russ,

    Sorry for the delay. I need to clarify a few points:
    1) I assume this is not an XFire Web service, am I right?

    2) I’m a little confused regarding the nature of this problem: You’re sending a message through the WS explorer to your JBoss JAX-RPC web service, after which the JBoss server throws up the stack trace you pasted above? I’m not sure I see where the WS explorer has issues.

    #266016 Reply

    Russ
    Member

    Brian:

    Yes, you are correct. We are using the default settings from JBoss and sending the infomation via Web Service Explorer. My understanding is JAX-RPC is nothing more than a kluge for tricking the web server into thinking it is dealing with a servlet.

    I am not sure what you are driving at…..are you casting doubt on JBoss configuration for web services?

    Russ

    #266076 Reply

    Brian Fernandes
    Moderator

    Russ,

    I’m trying to figure out if there’s something wrong with the WS Explorer. As I said in my last post, I don’t see where the WS-Explorer has issues, it’s sending your message and your WS implementation or JBoss can’t handle it.
    Then this becomes a JBoss / WS implementation issue, not a WS Explorer issue. If you’re asking for assistance with your JBoss WS configuration or implementation, I’m afraid I can’t help you with that.

    However, if I’ve misunderstood and there still is an issue with the WS Explorer, do let me know.

    Sorry I couldn’t be of more assistance.

    #266084 Reply

    Russ
    Member

    thanks Brian…. you help point me in the right direction…..

Viewing 10 posts - 1 through 10 (of 10 total)
Reply To: [Closed] Web Service Explorer has Issues?

You must be logged in to post in the forum log in