Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

CXF 2.2.3 with RAD 7.5 that comes with WebSphere test server 6.1 with Servlet 2.4 spec

 
Sam Gehouse
Ranch Hand
Posts: 281
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using all the jars that come with CXF 2.2.3 to deploy a very simple Hello World proof of concept type application. The application does not get deployed in WebSphere 6.1 test server that comes with RAD 7.5 that uses Servlet 2.4 specification. I get the error below:


Publishing failed
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer had errors:
Tools for WebSphere V6.1 must be installed in order to generate WebSphere V6.1 compliant code.

Any suggestion on how to run ANY VERSION of CXF in WebSphere test server 6.1 will be appreciated.
 
Sam Gehouse
Ranch Hand
Posts: 281
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using the link below for learning purposes:

http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html

I am using CXF 2.1.6 in RAD 7.5 (WebSphere Test server 6.1, Servlet 2.4). I have placed all the jar files that come with CXF 2.1.6 in web-inf/lib folder of the application. I probably have more jar files that I need in that web-in/lib. However, that should not be an issue.

I get the following errors:

1. The server and the application (deployed in the server) both start. But I get a pop-up message saying:

Publishing failed
Deploying MyExampleWebService
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer had errors:

Tools for WebSphere V6.1 must be installed in order to generate WebSphere V6.1 compliant code.

2. When I execute the client code as per the above example, I get the error below:





Any input will be appreciated.
Regards,
Sam
 
Martijn Verburg
author
Bartender
Posts: 3275
5
Eclipse IDE Java Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Looks like the server is executing and responding with a HTML stream as opposed to a WSDL stream? Not sure, but that's what it looks like to me...
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic