3 Replies Latest reply on Sep 4, 2006 10:29 AM by Taciano Perez

    J2EE tutorial web services client throws

    Taciano Perez Newbie

      Hi

      I'm using JBoss 4.0.4.GA, with the "all" installation option. I'm going through the "Getting Started with JBoss 4.0" guide (release 5).

      When I reach the topic "Running the Web Service Client" (item 5.3 of the doc) and run the command "ant -f jboss-build.xml run-ws" a "java.lang.UnsupportedOperationException: setProperty must be overridden in subclasses of SOAPMessage" exception is thrown.

      The full stack trace is as follows:

      C:\temp\j2eetutorial14\examples\bank>ant -f jboss-build.xml run-ws
      Buildfile: jboss-build.xml

      run-ws:
      [java] log4j:WARN No appenders could be found for logger (org.jboss.ws.meta
      data.JSR109ClientMetaDataBuilder).
      [java] log4j:WARN Please initialize the log4j system properly.
      [java] Customer: 200
      [java] Exception in thread "main" java.rmi.RemoteException: Call invocation
      failed: setProperty must be overridden by all subclasses of SOAPMessage; nested
      exception is:
      [java] java.lang.UnsupportedOperationException: setProperty must be ove
      rridden by all subclasses of SOAPMessage
      [java] at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:719
      )
      [java] at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:398)
      [java] at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:164)
      [java] at $Proxy0.getAccountsOfCustomer(Unknown Source)
      [java] at com.jboss.ebank.WSClient.main(WSClient.java:40)
      [java] Caused by: java.lang.UnsupportedOperationException: setProperty must
      be overridden by all subclasses of SOAPMessage
      [java] at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:424)
      [java] at org.jboss.ws.soap.SOAPMessageImpl.(SOAPMessageImpl.java
      :77)
      [java] at org.jboss.ws.soap.MessageFactoryImpl.createMessage(MessageFac
      toryImpl.java:133)
      [java] at org.jboss.ws.binding.soap.SOAP11BindingProvider.createMessage
      (SOAP11BindingProvider.java:52)
      [java] at org.jboss.ws.binding.soap.SOAPBindingProvider.bindRequestMess
      age(SOAPBindingProvider.java:108)
      [java] at org.jboss.ws.binding.soap.SOAP11BindingProvider.bindRequestMe
      ssage(SOAP11BindingProvider.java:58)
      [java] at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:647
      )
      [java] ... 4 more
      [java] Java Result: 1

      BUILD SUCCESSFUL
      Total time: 19 seconds

      Everything was running smoothly up to this point. I found a bug reported on JIRA about this (http://jira.jboss.com/jira/browse/JBWS-1126?page=all), but apparently it was considered a CLASSPATH problem. Well, if there is actually a CLASSPATH problem, I'd like to know what must be done to the default JBoss configuration to make it work.

      Thanks in advance,

      Taciano Perez
      Solution Architect
      Hewlett-Packard