Sven its difficult to see whats going on here with so many pieces missing could you please post hello_ws_rest.Hellorequest.java hello_ws_rest.Helloresponse.java
also could you please display the exact command you are using to create services.xml HelloWebServiceREST.java Please display which command and which parameters you are using to create RESTSample_1.0.0.aar Which specific URLS you are using to test against Takk, Martin ______________________________________________ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > Date: Sat, 27 Apr 2013 07:00:21 +0000 > From: j...@apache.org > To: java-dev@axis.apache.org > Subject: [jira] [Comment Edited] (AXIS2-5379) The third URL parameter can not > be processed (REST web service with WSDL 2.0) > > > [ > https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643569#comment-13643569 > ] > > Sven Strohschein edited comment on AXIS2-5379 at 4/27/13 7:00 AM: > ------------------------------------------------------------------ > > Hi, > > Thank you for the continuous and constructive support. :-) Could you please > also post your WSDL file? > > I just tried to apply your configurations of the services.xml (with the > working variant with only two parameters to check if the changes are > generally working). I see differences in the message receiver configurations > and I have some more configurations like the "operation" element and more > parameters. When I only apply the message receivers instead of using the > generated InOut receiver, Axis2 throws "wrong number of arguments": > > {code:xml} > <soapenv:Reason xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> > <soapenv:Text xml:lang="en-US">wrong number of arguments</soapenv:Text> > </soapenv:Reason> > {code} > > When I also try to remove all the parameters and the "operation" element > which you doesn't have within your services.xml, the whole service isn't > found anymore: "The service cannot be found for the endpoint reference (EPR) > /services/XYAccessWebServiceREST/getAccess?account=demo&pin=1234". > > Here is my services.xml which is working with two, but not three parameters: > > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <!-- This file was auto-generated from WSDL --> > <!-- by the Apache Axis2 version: 1.6.2 Built on : Apr 17, 2012 (05:33:49 > IST) --> > <serviceGroup> > <service name="XYAccessWebServiceREST"> > <messageReceivers> > <messageReceiver mep="http://www.w3.org/ns/wsdl/in-out"; > class="xy.access.webservice.XYAccessWebServiceRESTMessageReceiverInOut"/> > </messageReceivers> > <parameter > name="ServiceClass">xy.access.webservice.XYAccessWebServiceREST</parameter> > <parameter name="useOriginalwsdl">true</parameter> > <parameter name="modifyUserWSDLPortAddress">true</parameter> > <operation name="getAccess" mep="http://www.w3.org/ns/wsdl/in-out"; > namespace="xy-ws-rest"> > <actionMapping>\"\"</actionMapping> > <outputActionMapping>urn:accessResponse</outputActionMapping> > </operation> > </service> > </serviceGroup> > {code} > > > was (Author: novanic): > Hi, > > Thank you for the continuous and constructive support. :-) Could you please > also post your WSDL file? > > I just tried to apply your configurations of the services.xml (with the > working variant with only two parameters to check if the changes are > generally working). I see differences in the message receiver configurations > and I have some more configurations like the "operation" element and more > parameters. When I only apply the message receivers instead of using the > generated InOut receiver, Axis2 throws "wrong number of arguments": > > {code:xml} > <soapenv:Reason xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> > <soapenv:Text xml:lang="en-US">wrong number of arguments</soapenv:Text> > </soapenv:Reason> > {code} > When I also try to remove all the parameters and the "operation" element > which you doesn't have within your services.xml, the whole service isn't > found anymore: "The service cannot be found for the endpoint reference (EPR) > /services/XYAccessWebServiceREST/getAccess?account=demo&pin=1234". > > Here is my services.xml which is working with two, but not three parameters: > > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <!-- This file was auto-generated from WSDL --> > <!-- by the Apache Axis2 version: 1.6.2 Built on : Apr 17, 2012 (05:33:49 > IST) --> > <serviceGroup> > <service name="XYAccessWebServiceREST"> > <messageReceivers> > <messageReceiver mep="http://www.w3.org/ns/wsdl/in-out"; > class="xy.access.webservice.XYAccessWebServiceRESTMessageReceiverInOut"/> > </messageReceivers> > <parameter > name="ServiceClass">xy.access.webservice.XYAccessWebServiceREST</parameter> > <parameter name="useOriginalwsdl">true</parameter> > <parameter name="modifyUserWSDLPortAddress">true</parameter> > <operation name="getAccess" mep="http://www.w3.org/ns/wsdl/in-out"; > namespace="xy-ws-rest"> > <actionMapping>\"\"</actionMapping> > <outputActionMapping>urn:accessResponse</outputActionMapping> > </operation> > </service> > </serviceGroup> > {code} > > > > The third URL parameter can not be processed (REST web service with WSDL > > 2.0) > > ----------------------------------------------------------------------------- > > > > Key: AXIS2-5379 > > URL: https://issues.apache.org/jira/browse/AXIS2-5379 > > Project: Axis2 > > Issue Type: Bug > > Components: wsdl > > Affects Versions: 1.6.2 > > Reporter: Sven Strohschein > > Priority: Blocker > > Attachments: hello-rest.wsdl, HelloWebServiceREST.java, > > RESTSample_1.0.0.aar, services.xml > > > > > > I have developed a simple "hello world" REST web service with WSDL 2.0 and > > Axis2. > > There are three URL parameters defined, but the third URL parameter can not > > be processed (ADBException regarding unexpected element). The first two > > parameters are processed correctly. > > I could not get an answer via the axis2 mailing list regarding this problem > > ( > > http://mail-archives.apache.org/mod_mbox/axis-java-user/201207.mbox/%3C500F0ADF.1050108%40gmx.de%3E > > ), could not find any examples, tutorials or documentation for a REST web > > service with WSDL 2.0 and more than two parameters. > > The full example code, wsdl, etc. is attached to this issue. > > URL calls > > http://localhost:8080/services/helloWebServiceREST/getHello?input=test -> > > working > > http://localhost:8080/services/helloWebServiceREST/getHello?input=test&second=test2 > > -> working > > http://localhost:8080/services/helloWebServiceREST/getHello?input=test&second=test2&third=test3 > > -> not working ("org.apache.axis2.databinding.ADBException: Unexpected > > subelement second") > > http://localhost:8080/services/helloWebServiceREST/getHello?input=test&third=test3 > > -> not working ("org.apache.axis2.databinding.ADBException: Unexpected > > subelement input") > > Request element > > <xsd:element name="hellorequest"> > > <xsd:complexType> > > <xsd:sequence> > > <xsd:element minOccurs="0" name="input" nillable="true" > > type="xsd:string"/> > > <xsd:element minOccurs="0" name="second" nillable="true" > > type="xsd:string"/> > > <xsd:element minOccurs="0" name="third" nillable="true" > > type="xsd:string"/> > > </xsd:sequence> > > </xsd:complexType> > > </xsd:element> > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org > For additional commands, e-mail: java-dev-h...@axis.apache.org >
