Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » creating a top down web service with eclipse
creating a top down web service with eclipse [message #204069] Fri, 09 November 2007 16:46 Go to next message
Massimo Tivoli is currently offline Massimo Tivoli
Messages: 6
Registered: July 2009
Junior Member
Hi,

as for some of you, I am trying to create a first web service from a
..wsdl definition.
I am following "the top down web services" tutorial.
At generation time, the wizard give me the error reported below. I am
using Apache Tomcat v6.0,
Axis2 v1.3, Eclispe Europa v3.3.1, WTP v1.1.1, and Java 5. Do you have
experienced a similar problem
before? Some suggestion to solve it?

Thank all in advance,
-Massimo.


Exception occurred while code generation for the WSDL :
java.lang.AbstractMethodError:
org.apache.xerces.dom.DeferredDocumentImpl.getInputEncoding( )Ljava/lang/String;
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.eclipse.jst.ws.axis2.consumption.core.utils.WSDL2JavaGen erator.getAxisService(WSDL2JavaGenerator.java:379)
at
org.eclipse.jst.ws.axis2.creation.core.command.Axis2WSDL2Jav aCommand.execute(Axis2WSDL2JavaCommand.java:80)
at
org.eclipse.wst.command.internal.env.core.fragment.CommandFr agmentEngine.runCommand(CommandFragmentEngine.java:419)
at
org.eclipse.wst.command.internal.env.core.fragment.CommandFr agmentEngine.visitTop(CommandFragmentEngine.java:359)
at
org.eclipse.wst.command.internal.env.core.fragment.CommandFr agmentEngine.moveForwardToNextStop(CommandFragmentEngine.jav a:254)
at
org.eclipse.wst.command.internal.env.ui.widgets.SimpleComman dEngineManager$6.run(SimpleCommandEngineManager.java:294)
at
org.eclipse.jface.operation.ModalContext.runInCurrentThread( ModalContext.java:369)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.ja va:313)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java: 934)
at
org.eclipse.wst.command.internal.env.ui.widgets.SimpleComman dEngineManager.runForwardToNextStop(SimpleCommandEngineManag er.java:264)
at
org.eclipse.wst.command.internal.env.ui.widgets.WizardPageMa nager.runForwardToNextStop(WizardPageManager.java:91)
at
org.eclipse.wst.command.internal.env.ui.widgets.WizardPageMa nager.getNextPage(WizardPageManager.java:154)
at
org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizard Page.getNextPage(SimpleWizardPage.java:136)
at
org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDial og.java:813)
at
org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:369)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.jav a:616)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1495)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1519)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1504)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1 295)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3350)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2954)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
at org.eclipse.jface.window.Window.open(Window.java:796)
at org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.j ava:182)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498 )
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:546)
at
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:490)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:402)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1495)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1519)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1504)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1 295)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3350)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2954)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 19)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:289)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:76)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:363)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
Caused by: java.lang.AbstractMethodError:
org.apache.xerces.dom.DeferredDocumentImpl.getInputEncoding( )Ljava/lang/String;
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.ws.commons.schema.utils.DOMUtil.getInputEncoding( DOMUtil.java:594)
at
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSch emaCollection.java:348)
at
org.apache.axis2.description.WSDLToAxisServiceBuilder.getXML Schema(WSDLToAxisServiceBuilder.java:140)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.copy ExtensibleElements(WSDL11ToAxisServiceBuilder.java:2186)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.proc essTypes(WSDL11ToAxisServiceBuilder.java:306)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.proc essTypes(WSDL11ToAxisServiceBuilder.java:297)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.popu lateService(WSDL11ToAxisServiceBuilder.java:265)
... 62 more
Re: creating a top down web service with eclipse [message #204164 is a reply to message #204069] Sat, 10 November 2007 16:17 Go to previous messageGo to next message
Lawrence Mandel is currently offline Lawrence Mandel
Messages: 486
Registered: July 2009
Senior Member
Hi Massimo,

Are you using WTP 2.0? WTP v1.1.1 is not a valid release number. (Note
that plug-in version numbers no longer correspond to WTP version numbers.)

WRT to your error, I'm just taking a stab in the dark based on the stack
and a quick Google search, do you have an interface defined with no
corresponding binding? Do you have existing classes defined that cannot be
overridden by the service generator?

Lawrence

>Hi,
>
>as for some of you, I am trying to create a first web service from a
>..wsdl definition.
>I am following "the top down web services" tutorial.
>At generation time, the wizard give me the error reported below. I am
>using Apache Tomcat v6.0,
>Axis2 v1.3, Eclispe Europa v3.3.1, WTP v1.1.1, and Java 5. Do you have
>experienced a similar problem
>before? Some suggestion to solve it?
>
>Thank all in advance,
>-Massimo.
Re: creating a top down web service with eclipse [message #204212 is a reply to message #204164] Mon, 12 November 2007 07:43 Go to previous messageGo to next message
Massimo Tivoli is currently offline Massimo Tivoli
Messages: 6
Registered: July 2009
Junior Member
This is a multi-part message in MIME format.
--------------030509050508010306050100
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Lawrence,
first of all thank you for your reply and your clarification about the
plug-in versions... sorry for that but I am
quite new of this stuff. Basing on what you say, I don't really know the
exact version but it is the one obtained
by performing the automatic update feature provided with Eclipse Europa,
thus I think it is one of the latest ones
(maybe the 2.0 as you say).

About the binding, I am just following the tutorial at the URL:

http://www.eclipse.org/webtools/jst/components/ws/1.5/tutori als/TopDownWebService/TopDownWebService.html

and, hence, I am using the provided wsdl sample called
"AreaService.wsdl". I am also new about wsdl... as far as
I know, it seems to me that a SOAP binding is defined. I am attaching
this wsdl file, just in case you want to
have a look at it. I don't have any existing class. If I understood
well, I just need the wsdl file to perform the
tutorial steps until code generation. Is it right?

Are you able to perform the steps in that tutorial using that wsdl file?

Thank you very much for your support,
cheers,
-Massimo.



lmandel@ca.ibm.com wrote:
> Hi Massimo,
>
> Are you using WTP 2.0? WTP v1.1.1 is not a valid release number. (Note
> that plug-in version numbers no longer correspond to WTP version numbers.)
>
> WRT to your error, I'm just taking a stab in the dark based on the stack
> and a quick Google search, do you have an interface defined with no
> corresponding binding? Do you have existing classes defined that cannot be
> overridden by the service generator?
>
> Lawrence
>
>> Hi,
>>
>> as for some of you, I am trying to create a first web service from a
>> ..wsdl definition.
>> I am following "the top down web services" tutorial.
>> At generation time, the wizard give me the error reported below. I am
>> using Apache Tomcat v6.0,
>> Axis2 v1.3, Eclispe Europa v3.3.1, WTP v1.1.1, and Java 5. Do you have
>> experienced a similar problem
>> before? Some suggestion to solve it?
>>
>> Thank all in advance,
>> -Massimo.


--------------030509050508010306050100
Content-Type: text/xml; x-mac-type="0"; x-mac-creator="0";
name="AreaService.wsdl"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="AreaService.wsdl"

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://tempuri.org/AreaService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="AreaService" targetNamespace="http://tempuri.org/AreaService/">
<wsdl:types>
<xsd:schema targetNamespace="http://tempuri.org/AreaService/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="area" type="xsd:float"/>
<xsd:element name="parameters" type="tns:dimensions"/>
<xsd:complexType name="dimensions">
<xsd:sequence>
<xsd:element name="width" type="xsd:float"></xsd:element>
<xsd:element name="height" type="xsd:float"></xsd:element>
</xsd:sequence>
</xsd:complexType>

</xsd:schema>
</wsdl:types>
<wsdl:message name="CalculateRectAreaResponse">
<wsdl:part element="tns:area" name="area"/>
</wsdl:message>
<wsdl:message name="CalculateRectAreaRequest">
<wsdl:part element="tns:parameters" name="parameters"/>
</wsdl:message>
<wsdl:portType name="AreaService">
<wsdl:operation name="CalculateRectArea">
<wsdl:input message="tns:CalculateRectAreaRequest"/>
<wsdl:output message="tns:CalculateRectAreaResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="AreaServiceSOAP" type="tns:AreaService">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="CalculateRectArea">
<soap:operation soapAction="http://tempuri.org/AreaService/NewOperation"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="AreaService">
<wsdl:port binding="tns:AreaServiceSOAP" name="AreaServiceSOAP">
<soap:address location="http://tempuri.org"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

--------------030509050508010306050100--
Re: creating a top down web service with eclipse [message #204243 is a reply to message #204164] Mon, 12 November 2007 12:25 Go to previous messageGo to next message
Massimo Tivoli is currently offline Massimo Tivoli
Messages: 6
Registered: July 2009
Junior Member
Hi Lawrence,
just to let you know... I tried with Axis 1.4 (instead of Axis2 1.3 as
done in the previous days) and it works!
BTW, I still do not understand what is missing for Axis2 that is not for
Axis.

Cheers,
-Massimo.


lmandel@ca.ibm.com wrote:
> Hi Massimo,
>
> Are you using WTP 2.0? WTP v1.1.1 is not a valid release number. (Note
> that plug-in version numbers no longer correspond to WTP version numbers.)
>
> WRT to your error, I'm just taking a stab in the dark based on the stack
> and a quick Google search, do you have an interface defined with no
> corresponding binding? Do you have existing classes defined that cannot be
> overridden by the service generator?
>
> Lawrence
>
>> Hi,
>>
>> as for some of you, I am trying to create a first web service from a
>> ..wsdl definition.
>> I am following "the top down web services" tutorial.
>> At generation time, the wizard give me the error reported below. I am
>> using Apache Tomcat v6.0,
>> Axis2 v1.3, Eclispe Europa v3.3.1, WTP v1.1.1, and Java 5. Do you have
>> experienced a similar problem
>> before? Some suggestion to solve it?
>>
>> Thank all in advance,
>> -Massimo.
Re: creating a top down web service with eclipse [message #204283 is a reply to message #204243] Mon, 12 November 2007 22:24 Go to previous message
Lawrence Mandel is currently offline Lawrence Mandel
Messages: 486
Registered: July 2009
Senior Member
Hi Massimo,

Without trying the tutorial I don't know the exact reason it fails with
Axis2 however Axis2 and Axis are completely different code bases (Axis2 is
a complete rewrite) so it doesn't surprise me that the instructions should
change in this case.

Lawrence

>Hi Lawrence,
>just to let you know... I tried with Axis 1.4 (instead of Axis2 1.3 as
>done in the previous days) and it works!
>BTW, I still do not understand what is missing for Axis2 that is not for
>Axis.
>
>Cheers,
>-Massimo.
>
>
>lmandel@ca.ibm.com wrote:
>> Hi Massimo,
>>
>> Are you using WTP 2.0? WTP v1.1.1 is not a valid release number. (Note
>> that plug-in version numbers no longer correspond to WTP version
numbers.)
>>
>> WRT to your error, I'm just taking a stab in the dark based on the
stack
>> and a quick Google search, do you have an interface defined with no
>> corresponding binding? Do you have existing classes defined that cannot
be
>> overridden by the service generator?
>>
>> Lawrence
>>
>>> Hi,
>>>
>>> as for some of you, I am trying to create a first web service from a
>>> ..wsdl definition.
>>> I am following "the top down web services" tutorial.
>>> At generation time, the wizard give me the error reported below. I am
>>> using Apache Tomcat v6.0,
>>> Axis2 v1.3, Eclispe Europa v3.3.1, WTP v1.1.1, and Java 5. Do you have

>>> experienced a similar problem
>>> before? Some suggestion to solve it?
>>>
>>> Thank all in advance,
>>> -Massimo.
Previous Topic:JSP version mismatch using WTP with BEA?
Next Topic:using jasper standalone
Goto Forum:
  


Current Time: Wed Oct 01 00:13:32 GMT 2014

Powered by FUDForum. Page generated in 0.06696 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software