1 Reply Latest reply on Oct 4, 2007 1:15 PM by kukeltje

    axisfault error

    amybasu

      Hi I am tring to call a Axis 1.0 client from my jbpm server, its giving me the following error:
      08:31:04,146 INFO [STDOUT] AxisFault
      faultCode: { http://schemas.xmlsoap.org/soap/envelope/}Server.userException
      faultSubcode:
      faultString: java.lang.ClassCastException: org.apache.axis.attachments.AttachmentsImpl
      faultActor:
      faultNode:
      faultDetail:
      {http://xml.apache.org/axis/}stackTrace:java.lang.ClassCastException: org.apache.axis.attachments.AttachmentsImpl
      at org.apache.axis.Message.setup(Message.java:352)
      at org.apache.axis.Message.<init>(Message.java:246)
      at org.apache.axis.client.Call.invoke(Call.java:2425)
      at org.apache.axis.client.Call.invoke (Call.java:2366)
      at org.apache.axis.client.Call.invoke(Call.java:1812)
      at WS4GetExperimentIDSOAP12BindingStub.getExperimentID(WS4GetExperimentIDSOAP12BindingStub.java :108)
      at com.sample.action.NameFileWS.invoke(NameFileWS.java:49)
      at com.sample.action.NameFileWS.execute(NameFileWS.java:68)
      at org.jbpm.graph.def.Action.execute(Action.java:123)
      at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:235)
      at org.jbpm.graph.def.GraphElement.executeActions(GraphElement.java:212)
      at org.jbpm.graph.def.GraphElement.fireAndPropagateEvent( GraphElement.java:182)
      at org.jbpm.graph.def.GraphElement.fireEvent(GraphElement.java:166)
      at org.jbpm.graph.def.Node.enter(Node.java:301)
      at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke (<generated>)

      however its running fine when i call it from a tomcat server.
      If anyone knows why I am getting this error, kindly help.
      thanks

        • 1. Re: axisfault error
          kukeltje

          Is it still on the 'client side'? Besides that since it is a classcastexception, I think you should provide way more info
          - what version is the jbpm
          - what server is it running on
          - which JDK
          - debug logging
          - a (unit) testcase demonstrating the problem