[
https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishanthan Thangarajah updated AXIS2-5379:
--
Attachment: RESTSample_1.0.0.aar
> The third URL parameter can not be proce
[
https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643515#comment-13643515
]
Kishanthan Thangarajah commented on AXIS2-5379:
---
I tried to reproduce this w
Thank you very much for the reply.
The web service was originally written with WSDL 1.1 and I got the same result
- The response was always blank.
From: Kishanthan Thangarajah
To: "[email protected]" ; Jack Sprat
Cc: "[email protected]"
Sen
On Fri, Apr 26, 2013 at 9:09 PM, Jack Sprat wrote:
> The ReST request looks like this:
> https://www.example.com/test2/services/TestService/echo?echoRequest=ping
If this is the URL format that you are going to use with REST requests,
then you don't need wsdl 2.0. These kind of REST URL are supp
The ReST request looks like this:
https://www.example.com/test2/services/TestService/echo?echoRequest=ping
The response returned is blank:
http://ws.example.com/test"; />
Can anyone tell me what may be wrong? Is ReST with Axis2 and WSDL 2.0
possible? I am trying to justify using Axis2 here but
H
i Sagara,
On Fri, Apr 26, 2013 at 4:54 PM, Sagara Gunathunga <
[email protected]> wrote:
>
> I'm not sure whether we are having duplicate features here, usually we can
> provide custom objects using "ServiceObjectSupplier" [1] parameter within
> services.xml file. This is how we supp
Hi Martin ,
On Fri, Apr 26, 2013 at 3:32 PM, Martin Gainty wrote:
> Just so we're on the same page..please create the JIRA and the format of
> the new ObjectSupplier element to services.xml
>
I was wrong, we don't need to change the services.xsd file, we can provide
ObjectSupliers as a paramete
On Fri, Apr 26, 2013 at 12:10 AM, Shameera Rathnayaka <
[email protected]> wrote:
> Hi devs,
>
> According to my inspection,
> There is no way to create a new instance from a class, which hasn't
> nullary constructor by an ObjectSupplier. see the getObject method
> declaration.
>
> Object get
Just so we're on the same page..please create the JIRA and the format of the
new ObjectSupplier element to services.xml
Also when the Object Supplier is missing it would seem "The lack of
ObjectSupplier exception" should be handled better than a stacktrace perhaps
with an informative user-fri
yuan liu created AXIS-2891:
--
Summary: generateWSDL Mapping ArrayIndexOutOfBoundsException
Key: AXIS-2891
URL: https://issues.apache.org/jira/browse/AXIS-2891
Project: Axis
Issue Type: Bug
10 matches
Mail list logo