test.
> AxisService2WSDL20 fails to return the WSDL 2.0 styles when the schema has a
> ComplexElement with XmlSchemaAny
> -
>
> Key: AXIS2-5391
>
8 PM:
Attached are my aar package file, and wsdl and xml files.
was (Author: saurjk):
Here are my aar package file, and wsdl and xml files.
> Getting message "Trouble processing wsdl file :null" when deploying wsd
KWSHeader.xsd
tmkennunglesenService.aar
Here are my aar package file, and wsdl and xml files.
> Getting message "Trouble processing wsdl file :null" when deploying wsdl 2.
Saurab Rajkarnikar created AXIS2-5651:
-
Summary: Getting message "Trouble processing wsdl file :null" when
deploying wsdl 2.0 aar file
Key: AXIS2-5651
URL: https://issues.apache.org/jira/browse/
based on last comment.
> The third URL parameter can not be processed (REST web service with WSDL 2.0)
> -
>
> Key: AXIS2-5379
> URL: https://issues.apache.
ter 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
>
rams an send back) :
> 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/
ixed with
this issue/ticket. Is there already an existing JIRA issue/ticket for the
NoSuchMethodError?
Thank you very much
> The third URL parameter can not be processed (REST web service with WSDL 2.0)
> --
JIRA
issue/ticket) is necessary in any case, when the error shouldn't be fixed with
this issue/ticket. Is there already an existing JIRA issue/ticket for the
NoSuchMethodError?
Thank you very much
> The third URL parameter can not be processed (RES
ter 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
>
arameter 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
>
Util passes to AxisEngine a
constructor with
org.apache.axis2.context.ConfigurationContext parameter is expected
Options
1)rollback to Axis2-1.4
2)file JIRA
Martin Gainty
> The third URL parameter can not be processed (REST web service with W
thor: novanic):
Attached all generated files/sources from the wsdl2code Maven plugin
(including HelloWebServiceRESTSkeletonInterface.java and
HelloWebServiceRESTMessageReceiverInOut.java).
> The third URL parameter can not be processed (REST web service with W
wsdl2code Maven plugin (including
HelloWebServiceRESTSkeletonInterface.java and
HelloWebServiceRESTMessageReceiverInOut.java). This was generated from the
attached hello-rest.wsdl (WSDL 2.0).
> The third URL parameter can not be processed (REST web service with WSDL
Maven plugin (including
HelloWebServiceRESTSkeletonInterface.java and
HelloWebServiceRESTMessageReceiverInOut.java).
> The third URL parameter can not be processed (REST web service with WSDL
ocessed (REST web service with WSDL 2.0)
> -
>
> Key: AXIS2-5379
> URL: https://issues.apache.org/jira/browse/AXIS2-5379
> Project: Axis2
> Issue Type:
tach
HelloWebServiceRESTSkeletonInterface.java
Martin
> The third URL parameter can not be processed (REST web service with WSDL 2.0)
> -
>
> Key: AXIS2-5379
> URL: https://issues.apache.or
Helloresponse.java attached
> The third URL parameter can not be processed (REST web service with WSDL 2.0)
> -
>
> Key: AXIS2-5379
> URL: https://issues.apache.
ated java files
hello_ws_rest.Hellorequest.java
hello_ws_rest.Helloresponse.java
Martin
> The third URL parameter can not be processed (REST web service with WSDL 2.0)
> -
>
>
sed (REST web service with WSDL 2.0)
> -
>
> Key: AXIS2-5379
> URL: https://issues.apache.org/jira/browse/AXIS2-5379
> Project: Axis2
> Issue Type: Bug
ue
I'm running the webservice in an OSGi environment, but I think this doesn't
matter because everything else is working.
I'm using version 1.6.2. Which version do you use?
Thanks again for your support! :-)
&
> 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
>
calhost:8080/axis2/services/helloWebServiceREST/getHello?input=test&second=test2&third=test3
And the response for this (based on my skeleton implementation) :
> The third URL parameter can not be processed (REST we
be processed (REST web service with WSDL 2.0)
> -
>
> Key: AXIS2-5379
> URL: https://issues.apache.org/jira/browse/AXIS2-5379
> Project: Axis2
>
> 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
&
ce with WSDL 2.0)
> -
>
> Key: AXIS2-5379
> URL: https://issues.apache.org/jira/browse/AXIS2-5379
> Project: Axis2
> Issue Type: Bug
> C
koennen wir keine Haftung
fuer den Inhalt uebernehmen.
> Date: Sat, 27 Apr 2013 07:00:21 +
> From: [email protected]
> To: [email protected]
> Subject: [jira] [Comment Edited] (AXIS2-5379) The third URL parameter can not
> be processed (REST web servic
ess.webservice.XYAccessWebServiceRESTMessageReceiverInOut"/>
xy.access.webservice.XYAccessWebServiceREST
true
true
http://www.w3.org/ns/wsdl/in-out&quo
w.w3.org/ns/wsdl/in-out";
class="xy.access.webservice.XYAccessWebServiceRESTMessageReceiverInOut"/>
xy.access.webservice.XYAccessWebServiceREST
true
true
http://www.w3.org/ns/wsdl/in-out&quo
w.w3.org/ns/wsdl/in-out";
class="xy.access.webservice.XYAccessWebServiceRESTMessageReceiverInOut"/>
xy.access.webservice.XYAccessWebServiceREST
true
true
http://www.w3.org/ns/wsdl/in-out&qu
quot;/>
xy.access.webservice.XYAccessWebServiceREST
true
true
http://www.w3.org/ns/wsdl/in-out";
namespace="xy-ws-rest">
\"\"
urn:accessResponse
w.w3.org/ns/wsdl/in-out";
class="xy.access.webservice.XYAccessWebServiceRESTMessageReceiverInOut"/>
xy.access.webservice.XYAccessWebServiceREST
true
true
http://www.w3.org/ns/wsdl/in-out&quo
be processed (REST web service with WSDL 2.0)
> -
>
> Key: AXIS2-5379
> URL: https://issues.apache.org/jira/browse/AXIS2-5379
> Project: Axis2
>
ema generated for this is
> 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
Kishanthan,
Thank you very much for the reply. I thought WSDL 2.0 was required to use ReST
with Axis2 but never got an answer before now.
Do I need a different WSDL to process ReST and SOAP requests for the same
service? Is that where I would use the 'servicePath' and
On Thu, Apr 18, 2013 at 2:32 AM, Jack Sprat wrote:
> Thank you for the reply.
>
> This [1] is one of the articles I read and noted in a previous reply. See
> my message from April 2 below. This article notes that WSDL 2.0 must be
> used for ReST services with Axis2. Is this tr
Check this [1]. It will be helpful on creating RESTful services with Axis2.
Also you have to give WSDL version as 2 when running wsdl2java for WSDL
2.0.
For example : ./wsdl2java.sh -uri /tmp/sample.wsdl -o /tmp/output *-wv 2*
Thanks,
Kishanthan.
[1] http://wso2.org/library/3726
On Wed, Apr 10
ect: Re: [Axis2] wsdl2java with WSDL 2.0
Martin and all,
Can you please specify exactly what instructions to follow to make the Axis2
web service work for both SOAP and ReST requests?
The last reply noted 3 different parameters, 1 of which
(enableRESTInAxis2MainServlet) has been deprecated. Th
last reply below on those 3 parameters.
Has anyone created an Axis2 web service that works for both SOAP and ReST
requests? Does the WSDL need to be version 2.0 for this to work? If so, does
the wsdl2java command support WSDL 2.0? All attempts to run wsdl2java with a
version 2.0 WSDL have f
2java with WSDL 2.0
yes ...if you follow the instructions in the previous email
Viel Gluck,
Martin
Date: Wed, 3 Apr 2013 14:34:25 -0700
From: [email protected]
Subject: Re: [Axis2] wsdl2java with WSDL 2.0
To: [email protected]
CC: java-dev@axis.
y, April 2, 2013 7:56 PM
Subject: RE: [Axis2] wsdl2java with WSDL 2.0
AxisRESTServlet has been deprecated in recent versions
you'll need to dial back to Axis2-1.1
http://grepcode.com/snapshot/repo1.maven.org/maven2/org.apache.axis2/axis2-kernel/1.1/
Otherwise you'll be playing wit
Does the wsdl2java command work with a version 2.0 WSDL? I have created a
version 2.0 WSDL and validated it with Woden (included with Axis2 1.6.1). The
WSDL also passed validation using Altova XML Spy. However, an error is thrown
when I try to create the code stubs using wsdl2java. Below is
wso2.org/library/3715
[2] http://wso2.org/library/3725
> The third URL parameter can not be processed (REST web service with WSDL 2.0)
> -
>
> Key: AXIS2-5379
>
commented on AXIS2-5279
WSDL customization API for Axis2 and stabilize WSDL 2.0 features
Gunathunga
resolved AXIS2-5279 as Fixed
WSDL customization API for Axis2 and stabilize WSDL 2.0 features
Gunathunga
commented on AXIS2-5279
WSDL customization API for Axis2 and stabilize WSDL 2.0 features
[
https://issues.apache.org/jira/browse/AXIS2-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranjana Prasad updated AXIS2-5279:
--
Attachment: wsdl2.patch.txt
Patch for WSDL 2.0 customization and test cases
sed (REST web service with WSDL 2.0)
> -
>
> Key: AXIS2-5379
> URL: https://issues.apache.org/jira/browse/AXIS2-5379
> Project: Axis2
> Issue Type: Bug
>
[email protected]
> Subject: [jira] [Created] (AXIS2-5391) AxisService2WSDL20 fails to return the
> WSDL 2.0 styles when the schema has a ComplexElement with XmlSchemaAny
>
> lakmali erandi baminiwatta created AXIS2-5391:
> -
-trunk) which fixes the issue.
> AxisService2WSDL20 fails to return the WSDL 2.0 styles when the schema has a
> ComplexElement with XmlSchemaAny
> -
>
>
lakmali erandi baminiwatta created AXIS2-5391:
-
Summary: AxisService2WSDL20 fails to return the WSDL 2.0 styles
when the schema has a ComplexElement with XmlSchemaAny
Key: AXIS2-5391
URL: https
k at this issue? I think it's very critical...
> The third URL parameter can not be processed (REST web service with WSDL 2.0)
> -
>
> Key: AXIS2-5379
>
[
https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Strohschein updated AXIS2-5379:
Description:
I have developed a simple "hello world" REST web service with WS
-rest.wsdl
> The third URL parameter can not be processed (REST web service with WSDL 2.0)
> -
>
> Key: AXIS2-5379
> URL: https://issues.apache.org/jira/br
[
https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Strohschein updated AXIS2-5379:
Description:
Hi,
I have developed a simple "hello world" REST web service wit
[
https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Strohschein updated AXIS2-5379:
Summary: The third URL parameter can not be processed (REST web service
with WSDL 2.0
Sven Strohschein created AXIS2-5379:
---
Summary: The 3. 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
Gunathunga )
Fixed in r1358607.
> Axis2 should support to use "useOriginalWSDL" property for WSDL 2.0
> ---
>
> Key: AXIS2-5191
> URL: https://issues.apache.o
.
> WSDLSupplier should support for both WSDL 1.1 and WSDL 2.0
> ---
>
> Key: AXIS2-5278
> URL: https://issues.apache.org/jira/browse/AXIS2-5278
> Project: Axis2
> Is
e on r1358606.
> WSDL customization API for Axis2 and stabilize WSDL 2.0 features
> -
>
> Key: AXIS2-5279
> URL: https://issues.apache.org/jira/browse/AXIS2-5279
>
for test classes.
> WSDL customization API for Axis2 and stabilize WSDL 2.0 features
> -
>
> Key: AXIS2-5279
> URL: https://issues.apache.org/jira/browse/AXIS2-5279
>
sing in your patch please attach them.
TestWSDL11SupplierTemplate
TestWSDL20Supplier
> WSDL customization API for Axis2 and stabilize WSDL 2.0 features
> -
>
> Key: AXIS2-5279
>
[
https://issues.apache.org/jira/browse/AXIS2-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranjana Prasad updated AXIS2-5279:
--
Attachment: WSDL-1.patch
> WSDL customization API for Axis2 and stabilize WSDL
atch which contains my progress so far.
Thanks,
> WSDL customization API for Axis2 and stabilize WSDL 2.0 features
> -
>
> Key: AXIS2-5279
> URL: https://issues.apache.or
[
https://issues.apache.org/jira/browse/AXIS2-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra updated AXIS2-3768:
--
Component/s: wsdl
> WSDL20ToAxisServiceBuilder does not read policies in WSDL 2.0 d
and provide your feedback.
> Axis2 should support to use "useOriginalWSDL" property for WSDL 2.0
> ---
>
> Key: AXIS2-5191
> URL: https://issues.apache.o
ring requestIP) method to understand
this logic, it is required to apply same logic to printWSDL2() method.
In WSDL 1.1 we use WSDLConstants.WSDL_4_J_DEFINITION to retrieve the document,
in WSDL 2.0 you have to use WSDLConstants.WSDL_20_DESCRIPTION to retrieve
the document then it should be seri
o use "useOriginalWSDL" property for WSDL 2.0
> ---
>
> Key: AXIS2-5191
> URL: https://issues.apache.org/jira/browse/AXIS2-5191
> Project: Axis2
>
vide more insight on this project.
Also this will add some positive points to you during the selection process.
Since you have previous experience with Woden IMO it's better to try out for
few WSDL 2.0 related issue first.
> WSDL customization API for Axis2 and s
s my GSoC project. I have some previous
experience on Apache Woden project, I'm curious to know do I have to fix all
issues mentioned above ? Also any advice on proposal structure ?
> WSDL customization API for Axis2 and stabilize WSDL
features and mainly focus on following two areas.
1.) Introduce a API to customize default WSDL generation behavior of Axis2 and
this need to be supported to both WSDL 1.1 and WSDL 2.0.
2.) Stabilize WSDL 2.0 features and add missing features.
Following are the set of issues that have been
WSDL customization API for Axis2 and stabilize WSDL 2.0 features
-
Key: AXIS2-5279
URL: https://issues.apache.org/jira/browse/AXIS2-5279
Project: Axis2
Issue Type: Improvement
WSDLSupplier should support for both WSDL 1.1 and WSDL 2.0
---
Key: AXIS2-5278
URL: https://issues.apache.org/jira/browse/AXIS2-5278
Project: Axis2
Issue Type: Improvement
Axis2 should support to use "useOriginalWSDL" property for WSDL 2.0
---
Key: AXIS2-5191
URL: https://issues.apache.org/jira/browse/AXIS2-5191
Project: Axis2
Hi all,
Can you help please...
I went through the following steps to develop a axis2 webservice from
a wsdl 2.0 file and a set of corresponding xsd files
1) run the command wsdl2java on my wsdl 2.0 file to generate the server code:
wsdl2java -uri C:\workspace\UserService\myService.wsdl -o
c
th service side code including skeleton...
>>and client side code including stub...
>> - deploy the service to local Tomcat/Axis2
>> - in browser,
>>http://localhost:8080/axis2/services/xxxWSDL11?wsdl =>
>> will display
xis2/services/xxxWSDL11?wsdl =>
> will display WSDL 1.1 definition of the service
> http://localhost:8080/axis2/services/xxxWSDL11?wsdl2 =>
> will display WSDL 2.0 definition of the service
>
>
> Scenario 2
>
> - use WSDL 2.0 document to generate code
>
ces/xxxWSDL11?wsdl =>
> will display WSDL 1.1 definition of the service
> http://localhost:8080/axis2/services/xxxWSDL11?wsdl2 =>
> will display WSDL 2.0 definition of the service
>
>
> Scenario 2
>
> - use WSDL 2.0 document to generat
the service to local Tomcat/Axis2
- in browser,
http://localhost:8080/axis2/services/xxxWSDL11?wsdl =>
will display WSDL 1.1 definition of the service
http://localhost:8080/axis2/services/xxxWSDL11?wsdl2 =>
will display WSDL 2.0 definition of the s
t: The endpoint reference (EPR) for
>> the Ope
>> ration not found is
>> http://localhost:8080/axis2/services/reservationService and
>> the WSA Action = null. If this EPR was previously reachable, please
>> contact the
>> server administrator.*
>>
>&
WSDL20 and the WSA
Action = null. If this EPR was previously reachable, please contact the
server administrator.*
StockQuoteServiceWSDL20 generates service code and client code based on *WSDL
2.0* format.
Thanks!
Ping
On Sun, May 1, 2011 at 11:52 PM, Ping Liu wrote:
> Hi Sagara,
>
> Thank
stub...) based on the given WSDL (which is in WSDL 2.0 format). My goal is
to verify whether these generated Java code actually work correctly.
To do so, I try to write a service client just like the ADBClient described
in QuickStart Guide in Axis2 website at
http://axis.apache.org/axis2/java/core
es/reservationService
> and
> the WSA Action = null. If this EPR was previously reachable, please contact
> the
> server administrator.
>
> The service itself is generated by WSDL 2.0 and the WSDL can be viewed
> successfully at
>
> http://localhost:8080/axis2/service
On Wed, Apr 27, 2011 at 11:04 AM, Ping Liu wrote:
>
> Like Axis2 QuickStart Guide
>
> http://axis.apache.org/axis2/java/core/docs/quickstartguide.html
> (this is for WSDL 1.1)
>
> But does anybody know where and whether there is a similar guide for WSDL
> 2.0?
Like Axis2 QuickStart Guide
http://axis.apache.org/axis2/java/core/docs/quickstartguide.html
(this is for WSDL 1.1)
But does anybody know where and whether there is a similar guide for WSDL
2.0?
In particular, I am trying to write a service client like ADB client (
http
eservationService and
> the WSA Action = null. If this EPR was previously reachable, please contact
> the
> server administrator.*
>
> The service itself is generated by WSDL 2.0 and the WSDL can be viewed
> successfully at
>
> http://localhost:8080/axis2/services/reservationS
, please contact
the
server administrator.*
The service itself is generated by WSDL 2.0 and the WSDL can be viewed
successfully at
http://localhost:8080/axis2/services/reservationService?wsdl2
However, if don't explicitly spell out wsdl2, that is if using
http://localhost:8080/axis2/ser
message.
> Cannot turn off stdout messages when using WSDL 2.0
> ---
>
> Key: AXIS2-4334
> URL: https://issues.apache.org/jira/browse/AXIS2-4334
> Project: Axis2
> Issue T
Axis2 provide excellent support for WSDL 2.0 , by default when you query
with ?wsdl it will generate WSDL 1.1 document but with ?wsdl2 you can
generate WSDL 2.0 documents.
e.g - http://localhost:8080/services/SimpleService?wsdl2
Also to generate source codes from WSDL 2.0 document you can use
Any Axis2 version (since it's inception) generates and supports WSDL 2.0?
Is this by default or is a setting somewhere required for generating a
particular
version of WSDL? In other words if I query an Axis2 1.3 WS would I be
getting back a 2.0 WSDL by default?
Thanks
Demetris wrote:
a manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Fri, 2 Apr 2010 00:00:05 -0400
Subject: Re: WSDL 2.0 for mobiles
From: [email protected]
To: [email protected]
Wo
on, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Fri, 2 Apr 2010 00:00:05 -0400
Subject: Re: WSDL 2.0 for mobiles
From: [email protected]
To: [email protected]
Woden is the only parser that I'm aware of.
Thanks,
Keith.
On Wed, Mar 31, 2010 at
Woden is the only parser that I'm aware of.
Thanks,
Keith.
On Wed, Mar 31, 2010 at 4:01 PM, Demetris wrote:
>
> Does anyone happen to know of any WSDL 2.0 parsers that can run
> under J2ME CDC? I tried Woden (which compiles on Java 1.4) but no
>
Does anyone happen to know of any WSDL 2.0 parsers that can run
under J2ME CDC? I tried Woden (which compiles on Java 1.4) but no
luck.
Thanks
-
To unsubscribe, e-mail: [email protected]
For additional
s.html
[2] - http://wso2.org/library/175
Thanks,
Thanks
Sagara Gunathunga wrote:
Hi,
It is possible to use WSDL 2.0 to represent any REST service
in the same way as SOAP services [1] , if you want to parse
WSDL 2.0 manually you can use Apache Woden [2] for
1/rest-ws.html
[2] - http://wso2.org/library/175
Thanks,
>
> Thanks
>
> Sagara Gunathunga wrote:
>
>> Hi,
>>
>> It is possible to use WSDL 2.0 to represent any REST service in the same
>> way as SOAP services [1] , if you want to parse WSDL 2.0 manually you can
&g
which means the application needs to use them
to implement the invocations?
Thanks
Sagara Gunathunga wrote:
Hi,
It is possible to use WSDL 2.0 to represent any REST service in the
same way as SOAP services [1] , if you want to parse WSDL 2.0 manually
you can use Apache Woden [2] for that ,
Hi,
It is possible to use WSDL 2.0 to represent any REST service in the same way
as SOAP services [1] , if you want to parse WSDL 2.0 manually you can use
Apache Woden [2] for that , as an example have look at this class used in
Axis2 [3].
Thanks,
[1] - http://www.ibm.com/developerworks
Hi all,
Are there any examples of parsing the WSDL 2.0 manually at the
application level (instead of
the Axis engine doing it?). I am assuming the parsing of a WSDL 2.0
representing a SOAP
service would be different than the REST one - where are these
capabilities in the distribution
so that
99 matches
Mail list logo
