[jboss-user] [JBossWS] - JAX-WS from Sessions Bean fails due to missing org/jboss/log

ejb3workshop do-not-reply at jboss.com
Mon Aug 20 09:03:45 EDT 2007


I have a standalone client jar which using JAX-WS in JDK1.6 is able to consume a webservice. I would like to invoke the webservice from a session bean, so I added the webservice client JAR to my ear file and updated the application.xml file. 

The problem is that when I try to invoce the client from within JBoss I get the following error. 

A search in the forums and the web makes suggestions to include the jboss-common-clients.jar in the classpath. I tried added this jar to the /server/default/lib folder as well as include it within the EAR / application.xml, of which neiter worked.

If JAX-WS client is not supported what other libraries can I use to consume a web service from a Session Bean. 

anonymous wrote : 
  | java.lang.NoClassDefFoundError: org/jboss/logging/Logger
  |         at javax.xml.soap.FactoryLoader.(FactoryLoader.java:47)
  |         at javax.xml.soap.SOAPFactory.newInstance(SOAPFactory.java:64)
  |         at org.jboss.ws.core.soap.SOAPFactoryImpl.createElement(SOAPFactoryImpl.java:120)
  |         at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:116)
  |         at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:85)
  |         at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:254)
  |         at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:75)
  |         at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:472)
  |         at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:304)
  |         at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135)
  |         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
  |         at org.jboss.remoting.Client.invoke(Client.java:1550)
  |         at org.jboss.remoting.Client.invoke(Client.java:530)
  |         at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:171)
  |         at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77)
  |         at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:322)
  |         at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:230)
  |         at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
  |         at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075829#4075829

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075829



More information about the jboss-user mailing list