This week's book giveaway is in the Java 8 forum.
We're giving away four copies of Java 8 in Action and have Raoul-Gabriel Urma, Mario Fusco, and Alan Mycroft on-line!
See this thread for details.
The moose likes Web Services and the fly likes Need info about deployment descriptors required on IBM websphere for webservice Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Need info about deployment descriptors required on IBM websphere for webservice" Watch "Need info about deployment descriptors required on IBM websphere for webservice" New topic
Author

Need info about deployment descriptors required on IBM websphere for webservice

Yogesh Gandhi
Ranch Hand

Joined: Dec 05, 2008
Posts: 206
Hi Friends,

I have a WAR file which has a web service. The webservice has been running successfully on weblogic server.

I created the WAR file using Jdev 11g (Which uses weblogic 11g as the server behind the scenes) and hence the deployment descriptor for weblogic i.e. weblogic.xml was automatically generated.

It had the following contents



Now what I need is to deploy this webservice on a IBM websphere server.

Can anyone please help me in this regard, that what all deployment descriptors I need to add in the WAR file for websphere.

I tried deploying it without any changes, i was able to deploy it and start it. But when I access the URL for WSDL, I get the following error

Error 404: javax.servlet.UnavailableException: SRVE0201E: Servlet [com.nucleus.ws.CreateCustomerServiceImpl]: not a servlet class

Anyone having any idea about deployment descriptors, it would be so nice if anyone of me having any idea can give me some directions about how to create deployment descriptors.


Yogesh Gandhi
Ranch Hand

Joined: Dec 05, 2008
Posts: 206
I got the following information from the IBM website

Developing a webservices.xml deployment descriptor for JAX-WS applications
Deployment descriptors are standard text files, formatted using XML and packaged in a Web services application. You can optionally use the webservices.xml deployment descriptor to augment or override application metadata specified in annotations within Java API for XML-Based Web Services (JAX-WS) Web services.

About this task
Similar to Java API for XML-based RPC (JAX-RPC) Web services, you can use deployment descriptors to describe JAX-WS Web services. For JAX-WS Web services, the use of the webservices.xml deployment descriptor is optional because you can use annotations to specify all of the information that is contained within the deployment descriptor file. You can use the deployment descriptor file to augment or override existing JAX-WS annotations. Any information that you define in the webservices.xml deployment descriptor overrides any corresponding information that is specified by annotations.



I am glad, because I am using JAX-WS annotations in my java code. So I think, I do not need to use the webservices.xml deployment descriptors.

I have deployed the WAR file after removing the webservices.xml file from .WAR file. I am able to start the instance on the websphere console.
But I am not able to generate/access the URL for the webservice.

When I access http://10.1.50.149:9081/QdeUpload/CreateCustomerServicePort?WSDL URL, I get the following message

Error 404: javax.servlet.UnavailableException: SRVE0201E: Servlet [com.nucleus.ws.CreateCustomerServiceImpl]: not a servlet class

Can someone please help me in this regard.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Need info about deployment descriptors required on IBM websphere for webservice
 
Similar Threads
WebLogic 9.2 clustering problem
I am getting this message : "Error 404--Not Found" while starting an app by Weblogic
Log4j in Weblogic - ClassNotFoundException please help
Deployment error NoClassDefFoundError: org.hibernate.cfg.Configuration on Oracle 11g App Server
Need sample of weblogic.xml file for supporting HttpOnly