- This topic has 14 replies, 4 voices, and was last updated 10 years, 9 months ago by
.
-
Posts
-
Hi,
I am using MyEclipse Blue IDE for developing the application since last 3 years. The Application server configured is Websphere 7.0. Earlier the same webservices project was able to deploy from the IDE. Now since last few days Its throwing error during deployment of the EAR file which contains a JAX-WS webservices project. Its strange it was working fine earlier. It shows it culdn’t locate the servlet class inside the war file.
I have verified the war file, where I couldnt find the .class files. It is not able to generate the servlet class files. Can anybody help on this matter. I am strugling from a long time to fix this.
Thanks in advance.
DibyenduDibyendu,
Sorry that you are seeing this issue.
Can you please answer some more questions for us ?
1. Please copy paste the Installation Details from MyEclipse > Installation Summary > Installation Details ?
2. Can you please let us know exactly what class it is complaining about ?
3. Can you also try to deploy the ear manually to the Websphere server by exporting the ear file and let us know what exact error you see ?
4. Please attach the deployment.log file and also copy paste the contents of the .log file which is located at <workspace dir>/.metadata/.log to help us investigate further.
Hi Swapna,
1. The installation summary is attached.
2. There are 4 servlet classes present inside the WebServices project. During deployment it shows the following error for each Servlet class.
[4/5/13 15:45:25:412 IST] 00000023 annotations W fi.mela.masha.print.ws.AsianhallintaTulostusImpl addServlet class [fi.mela.masha.print.ws.AsianhallintaTulostusImpl] for servlet [PrintDocumentServlet] cannot be found
com.ibm.wsspi.amm.exception.NoSuchClassException: unable to locate class fi.mela.masha.print.ws.AsianhallintaTulostusImpl in module MASHAWebService.war
at com.ibm.ws.amm.scan.util.info.impl.DelayedClassInfo.getClassInfo(DelayedClassInfo.java:253)Due to these errors the application failed to start.
3. Same error is displayed in case of exporting the ear manually and deploy it on server.
But it is deployed successfully when I build the ear file through ant script written by our developers.4. deployment.log file and workspace log files are attached too.
Thanks
DibyenduDibyendu,
Thank you for the details.
1. Can you please send us all .* files (.project, .classpath, .settings folder, etc.) and Deployment Descriptors for EAR and WAR along with server.log to help us investigate further ?
2. I strongly recommend you switch to MyEclipse 2013, which is our latest version to take advantage of over 3-4 years of development and enhancements made to MyEclipse. You can download the MyEclipse 2013 GA from here :
https://www.myeclipseide.com/module-htmlpages-display-pid-4.htmlHello Swapna,
1. The files are attached here. Where can I find the deployment descriptor file. Let me know.
2. I am using MyEclipse Blue which is license version. Is it recomended to use MyEclipse 2013 as a replacement of Blue? Can I use the same license over there?
Regards,
DibyenduDibyendu,
Thank you for the files.
1. For EAR the deployment descriptor is application.xml (META-INF/application.xml) and for WAR it is web.xml (WEB-INF/web.xml).
2. You can use the same license that you currently have with MyEclipse Blue 2013. Here is the link for MyEclipse Blue 2013 :
https://www.myeclipseide.com/index.php?name=Recommend_Us&req=Download&version=MEBlueLet us know if you see any issues.
Dibyendu,
The configuration files for the EAR project are missing.
1.Can you please check if the “Build Automatically” is turned on ? If no, please turn it on and check if the issue persists.
2. If you are still seeing issues, can you please make a copy of all the projects, remove source code and JSP/HTML files from the projects, zip them send it to us for further investigation?
Hi,
1. ‘Build Automatically’ option is ON.
2. Sending you the zip file with project settings. The wsdl and source codes are removed from the project.
Regards,
DibyenduHi Swapna,
As per your suggestion I have started using the MyEclipse 2013 version. The goood news is that, I am able to deploy the project without any errors. Its working fine for me as it was working before in Blue 8.5. Though I have some Project Migration issues but its not affecting my work. Thanks for the suggestion.
Kindly do let me know about the reported bug’s status.
Regards,
DibyenduDibyendu,
The dev team is looking into the bug report. We will post as soon as we have any information on the bug status.
Sorry for inconvenience caused.
Do let us know if you see any issues.
Dibyendu,
I want to make sure I understand your application configuration well. What was the role of EJB project? Was it working as JAX-WS client?
Hi,
The EJB project is called from the JAX-WS project. EJB project is used as the reference project for the JAX-WS project. Client calls are routed from webservices to EJB layer.
Regards,
DibyenduDibyendu,
Thank you for your reply. The EJB project is incorrectly scheduled for migration of JAX-WS facet. We will fix that issue in the next release.
Thank you very much for your help with determining the source of the issue!
