| Forum: Web Tools Project (WTP) |
|---|
| Topic: Eclipse wsdl validator doesn't show exact error |
|---|
| Eclipse wsdl validator doesn't show exact error [message #1059420] |
Sat, 18 May 2013 03:05 |
Lasith Chandrasekara Messages: 3 Registered: July 2009 |
Junior Member |
|
|
Hi All,
Got a chance to work with eclipse WSDL validator. But it seems like it doesn't return exact error message when not having network connection to the ws-i.org site. It would be better if it can give detailed message by saying "this resource on ws-i.org can't find".
i.e. can't find resource ws-i.org/Testing/Tools/2004/12/AP10_BP11_SSBP10_TAD.xml
As I can understand the connection to ws-i.org is not mandatory for WSDL validation. But since it attempts to connect to ws-i.org, when doing validation with a machine doesn't have internet connection this may consume 2-3 minutes (depending on the DNS and proxy configuration on networks). In that case it is better to have descriptive message.
Following stack-trace might be useful to understanding,
at org.eclipse.wst.wsi.internal.core.profile.impl.ProfileAssertionsReaderImpl.readProfileAssertions(ProfileAssertionsReaderImpl.java:130)
at org.eclipse.wst.wsi.internal.core.profile.impl.ProfileAssertionsReaderImpl.readProfileAssertions(ProfileAssertionsReaderImpl.java:72)
at org.eclipse.wst.wsi.internal.WSITestToolsProperties.getProfileAssertions(WSITestToolsProperties.java:93)
at org.eclipse.wst.wsi.internal.core.analyzer.BasicProfileAnalyzer.validateConformance(BasicProfileAnalyzer.java:209)
at org.eclipse.wst.wsi.internal.core.analyzer.Analyzer.validateAll(Analyzer.java:198)
at org.eclipse.wst.wsi.internal.analyzer.WSDLAnalyzer.validateConformance(WSDLAnalyzer.java:158)
at org.eclipse.wst.wsi.internal.validate.wsdl.WSDLValidator.validate(WSDLValidator.java:291)
As my understanding here the problem is in WSITestToolsProperties.getProfileAssertions(). Where it catches the exception and return null results.
-------------------------------
catch (Exception e)
{
result = null;
}
-------------------------------
So from this point onwards we are not throwing the excact error message.
Anyway the final log message is (it don't have information about ws-r resource path),
WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.
Reagards,
-Lasith Chandrasekara
|
|
|
| Topic: offline WSDLValidator.validate() |
|---|
| offline WSDLValidator.validate() [message #1059342] |
Fri, 17 May 2013 11:05 |
Raster Mising name Messages: 75 Registered: July 2009 |
Member |
|
|
Hi,
Am trying to execute the following code.
It works quite well when I am connected to the internet.
When offline its trying to locate the http://schemas.xmlsoap.org/wsdl/ for finding <definitions/> element in the wsdl.
Error then is this: Cannot find the declaration of element 'definitions'.
How can I make this code work when offline?
R
WSDLValidator wsdlVlidator= new WSDLValidator();
IValidationReport report = wsdlVlidator.validate(pathToWsdl);
IValidationMessage[] validationMessages = report.getValidationMessages();
for (IValidationMessage iValidationMessage : validationMessages)
{
System.out.println(iValidationMessage.getLine()+","+iValidationMessage.getColumn()+"-"+iValidationMessage.getSeverity()+"["+iValidationMessage.getMessage()+"]");
}
|
|
|
| Topic: IWAB0523E Error moving resource: null |
|---|
| IWAB0523E Error moving resource: null [message #1059308] |
Fri, 17 May 2013 09:30 |
Asha Honrao Messages: 1 Registered: May 2013 |
Junior Member |
|
|
Hi There,
Am trying to generate java proxy using WSDL (present at a server) using WS client in Eclipse 3.4.1
But encountering below error :
IWAB0523E Error moving resource: null
Detailsed error is:
IWAB0523E Error moving resource: null
java.lang.NullPointerException
at org.eclipse.wst.command.internal.env.common.FileResourceUtils.makeFolderPathAtLocation(FileResourceUtils.java:790)
at org.eclipse.wst.command.internal.env.common.FileResourceUtils.makeFolderPathAtLocation(FileResourceUtils.java:833)
at org.eclipse.wst.command.internal.env.common.FileResourceUtils.createFileAtLocation(FileResourceUtils.java:765)
at org.eclipse.jst.ws.internal.axis.consumption.core.command.WSDL2JavaCommand.moveGeneratedFiles(WSDL2JavaCommand.java:327)
at org.eclipse.jst.ws.internal.axis.consumption.core.command.WSDL2JavaCommand.execute(WSDL2JavaCommand.java:250)
at org.eclipse.jst.ws.internal.axis.consumption.ui.task.ClientCodeGenOperation$ClientWSModifyOperation.execute(ClientCodeGenOperation.java:102)
at org.eclipse.jst.ws.internal.axis.consumption.ui.task.ClientCodeGenOperation.execute(ClientCodeGenOperation.java:64)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:458)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:366)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.performFinish(WizardPageManager.java:262)
at org.eclipse.wst.command.internal.env.ui.widgets.DynamicWizard.performFinish(DynamicWizard.java:382)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
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.handlers.WizardHandler$New.executeHandler(WizardHandler.java:253)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java: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:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Here am not getting whetehr the wizard is unable to locate the WSDL(provided a http URL for WSDL) or it is able to createand copy the generated files at some location.
Note: Wizard does not ask for the specific location to select under the project.
Appreciate all you help on this topic. Thanks.
|
|
|
| Topic: .classpath question: org.eclipse.jst.j2ee.internal.web.container |
|---|
| .classpath question: org.eclipse.jst.j2ee.internal.web.container [message #1059097] |
Thu, 16 May 2013 12:31 |
Craig Whynot Messages: 1 Registered: May 2013 |
Junior Member |
|
|
Hello,
I need a specific version of two jars in order to run a driver (Selenium) from inside of Eclipse:
httpclient-4.2.1,
httpcore-4.2.1
I have required projects on my classpath which specify an older version of these jars (4.0). I can't modify these projects to reference the newer jars without refactoring / requiring regression testing, etc.
When I run my Selenium driver inside of Eclipse I get NoSuchMethodError because the older jar versions (4.0) are being selected by the classloader.
The only solution that I've stumbled upon is to move the .classpath entries for the desired jars ABOVE the org.eclipse.jst.j2ee.internal.web.container declaration like this:
<classpath>
...
<classpathentry kind="lib" path="ivy/lib/ide/httpclient-4.2.1.jar"/>
<classpathentry kind="lib" path="ivy/lib/ide/httpcore-4.2.1.jar"/>
<classpathentry kind="con" path="org.eclipse.jst.j2ee.internal.web.container"/>
...
</classpath>
This appears to automagically allow eclipse to load the 4.2.1 versions, when otherwise the 4.0 versions would be loaded.
Can someone please explain exactly how and why this works?
To recap: when running an application inside of eclipse, specifying specific jars via a classpathentry above the internal.web.container entry appears to allow the specified version to trump other jar versions on the classpath.
Thanks very much in advance; I would love to be able to sell this solution to my team by explaining how the heck it works
|
|
|
Powered by
FUDForum. Page generated in 0.11682 seconds