Community
Participate
Working Groups
Hi, I have created Enterprise application project, in this I have Client and Web project created, I was trying to create webservice using Bottom up using the Java bean I have created in my client project. However when I create new webservices, in webservice bean Identify screen, it showing me list of all methods created in my java bean CourseWebserviceBean.java, but when I try finish webservice creation. I'm getting below exception WAB0398E Error in generating WSDL from Java: java.lang.ClassNotFoundException: training.webservice.CourseWebServiceBean java.lang.ClassNotFoundException: training.webservice.CourseWebServiceBean at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:506) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(Unknown Source) at org.apache.tools.ant.AntClassLoader.findBaseClass(AntClassLoader.java:1425) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1101) at java.lang.ClassLoader.loadClass(Unknown Source) at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:187) at java.security.AccessController.doPrivileged(Native Method) at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:160) at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100) at org.apache.axis.wsdl.fromJava.Emitter.setCls(Emitter.java:2079) at org.apache.axis.tools.ant.wsdl.Java2WsdlAntTask.execute(Java2WsdlAntTask.java:188) at org.eclipse.jst.ws.internal.axis.consumption.core.command.Java2WSDLCommand.executeAntTask(Java2WSDLCommand.java:180) at org.eclipse.jst.ws.internal.axis.consumption.core.command.Java2WSDLCommand.execute(Java2WSDLCommand.java:95) at org.eclipse.jst.ws.internal.axis.creation.ui.command.BUCodeGenOperation$BottomUpWSModifyOperation.execute(BUCodeGenOperation.java:122) at org.eclipse.jst.ws.internal.axis.creation.ui.command.BUCodeGenOperation.execute(BUCodeGenOperation.java:86) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419) at Note: My Client project is referenced in web project, also I tried exporting jar of Client project to web project, still I get this error. -- Configuration Details -- Product: Eclipse 1.3.2.20110218-0812 (org.eclipse.epp.package.jee.product) Installed Features: org.eclipse.jdt 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
Do you have automatic builds enabled on the Project menu?
(In reply to comment #1) > Do you have automatic builds enabled on the Project menu? Yes, I do. However I tried without auto build after your comment, still I have same problem
(In reply to comment #1) > Do you have automatic builds enabled on the Project menu? More information, I'm running my application in JBoss server 6.0.0. Do you think this may have come environmental conflict?
Did anyone find anything related to this exception? Could you please tell me what fix it requires.
Mark please have a look. Ganesh, if possible, please attach your projects.
It sounds like for some reason your training.webservice.CourseWebServiceBean is not on the classpath that we pass into Apache Axis. Where in your project is the CourseWebServiceBean.class located? Can you place the attached .options file in the same directory as your eclipse executable, and run eclipse with the -debug option? This should output some more verbose output to help us figure out what's going on. Re-run your scenario and have a look in the eclipse error log (located in <your workspace>\.metadata\.log and look for a line starting with "IWAB5008I ()::executeAntTask: object=Class Path =" Is your CourseWebServiceBean class on that classpath?
Created attachment 198145 [details] debug options file
Oops! I found what was the problem, there was issue exporting jar file from my client project, therefore my CourseWebServiceBean wasn't exported properly into the jar file, after exporting the project again, it seems the file exported successfuly. I do not know the reason why it wasn't able to export earlier (Infact I tried multiple type of export, due to some minor changes I made in the Bean class). Now, I'm getting different error when I try to deploy the webservice in JBOSS6.0 Server. IWAB0489E Error when deploying Web service to Axis runtime axis-admin failed with {http://xml.apache.org/axis/}HTTP (404)Not Found
Processing file C:\Users\kganeshk\workspace\TrainingWeb\WebContent\WEB-INF\Cours eWebServiceBeanService\training\webservice\deploy.wsdd axis-admin failed with {http://xml.apache.org/axis/}HTTP (404)Not Found at org.apache.axis.tools.ant.axis.AdminClientTask.logOrThrow(AdminClient Task.java:379) at org.apache.axis.tools.ant.axis.AdminClientTask.executeInCurrentVM(Adm inClientTask.java:365) at org.apache.axis.tools.ant.axis.AdminClientTask.execute(AdminClientTas k.java:316) at org.eclipse.jst.ws.internal.axis.consumption.core.command.AxisDeployC ommand.executeAntTask(AxisDeployCommand.java:128) at org.eclipse.jst.ws.internal.axis.consumption.core.command.AxisDeployC ommand.execute(AxisDeployCommand.java:89) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEng ine.runCommand(CommandFragmentEngine.java:419) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEng ine.visitTop(CommandFragmentEngine.java:359) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEng ine.moveForwardToNextStop(CommandFragmentEngine.java:254) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineMa nager$6.run(SimpleCommandEngineManager.java:294) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalCont ext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1008) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineMa nager.runForwardToNextStop(SimpleCommandEngineManager.java:264) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.run ForwardToNextStop(WizardPageManager.java:91) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.per formFinish(WizardPageManager.java:262) at org.eclipse.wst.command.internal.env.ui.widgets.DynamicWizard.perform Finish(DynamicWizard.java:382) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java :811) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java :430) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java: 234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizard ShortcutAction.java:135) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection (ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContri butionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionC ontributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.ja va:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.jav a:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEAppli cation.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandl e.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runAppli cation(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Ec lipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.ja va:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.ja va:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
Should I INVALIDATE this defect? or should we keep this open for the Jar export failure???
Let's mark it as invalid. If you can provide more details about your jar export failure then we can track it is a separate defect, since that likely a different component than WTP WebServices/jst.ws
