On Thu, 2006-08-31 at 17:30 +0800, Xinjun Chen wrote:
> Hi,
>
> I read through the Axis2 documentation about RESTful support from
> http://ws.apache.org/axis2/1_0/rest-ws.html.
>
> I have some questions here.
>
> 1. What's the motivation of RESTful web services support in Axis2? If
> the efficie
Even modifing to what u have suggested i am getting the same
exception.Is there anything wrong in my wsdd file, because of which we
are not ablre to generate the WSDL.
Anne Thomas Manes wrote:
Change this:
returnQName="searchDeviceListReturn"
to this:
returnQName="rtns:searc
We are pleased to announce the release of Apache Axis2/C version 0.93.
You can download this release from
http://ws.apache.org/axis2/c/download.cgi
Key Features
1. AXIOM, an XML object model optimized for SOAP 1.1/1.2 Messages.
This has complete XML infoset support.
2. Support for one-way me
If you are using RPC style, then the auto-generated accessor elements
created for each parameter type *must* be unqualified. If you want to
change that, you must switch to document style. Axis will always
generate elementFormDefault="unqualified".
Anne
On 9/1/06, Rajesh Narayan <[EMAIL PROTECTED
I'm sorry -- I meant to say:
Axis will always generate elementFormDefault="qualified".
On 9/1/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
If you are using RPC style, then the auto-generated accessor elements
created for each parameter type *must* be unqualified. If you want to
chan
Change this:
returnQName="searchDeviceListReturn"
to this:
returnQName="rtns:searchDeviceListReturn"
Anne
On 9/1/06, shrabank <[EMAIL PROTECTED]> wrote:
Hi,
While generating the wsdl file from wsdd configuration i am getting
this exception.My return type is an array.
He
We need to see the rest of your WSDL to diagnose the problem.
When using document style, the message may contain at most one body
part, and the part must reference an element. When using RPC style,
the message may contain any number of body parts, and the parts must
reference types.
Axis2 suppor
If it's wrapped doc/literal, then your message should not contain an
element of type soapenc:string. Are you certain the that service is
using wrapped doc/literal? What SOAP stack is the service built with?
Anne
On 9/1/06, Christian Platta <[EMAIL PROTECTED]> wrote:
Hi,
I have the following:
Ax
Hi all,
I still have this problem after some time my service is running. I
think it is a bug: any idea?
ERROR QueueSizeServiceHandler:submitRequest - Fri Sep 01 18:14:36 BST
2006:Handler [FunctionalTestService1]: send failed: Two services can
not have same name, a ser
vice with annonServi
Hi,
I have the following:
Axis 1.3
A document literal (wrapped) service that I want to use
A client generated with WSDL2Java
My problem:
When I try to deserialize a response I get an exception that says
that no deserializer is found for string (namepsace http://
schemas.xmlsoap.org/soap/encod
Hi Brian,
AFAIK, Multiple parts in your WSDL violates WS-I Basic Profile [1].
Axis2 *might* support only WS-I conformant WSDLs.
Regards,
Ali Sadik Kumlali
[1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html
- Original Message From: Brian Dillon (ext. 944) <[EMAIL PROTECTED]>To:
Title: SOAPAction
Actually I just checked and the WSDL from
the server specified that the SOAPAction should be “” (See below),
so I think this might be an Axis 2 bug that it’s still sending the SOAPAction
as “urn:Getinfo”. Anyone know a way around this?
From t
Title: SOAPAction
I’m writing a client and I have an issue where the release 1.0 version of Axis 2 works and the latest build does not. I’m using code generated from WSDL2JAVA. The problem appears to lie on the server (not Axis). For some reason if the HTTP has anything but a blank
Hi,
While generating the wsdl file from wsdd configuration i am getting
this exception.My return type is an array.
Here is my wsdd file which i am writing to generate the wsdl file.
Please help me in resolving this problem.
http://xml.apache.org/axis/wsdd/";
xmlns:java="ht
Hi,
I am
using the axis 2 wsdl2java generator and have run
into a problem. If I have request (e.g. findPerson) which takes multuple
parameters (FirstName and LastName) how can this be represented in
WSDL.
Previoulsy in Axis 1.3
we used;
>
But with
Axis 2 I get the followin
Thanks Anne for the explanation.
Another quick query: Is there a way to specify the elementFormDefault variable explicitly in wsdd? I tried having it as a parameter in globalConfiguration but it doesn't seem to work. This is what i used:
Regards,Rajesh
On 9/1/06, Anne Thomas Manes <[EMAIL P
Actually, in the response, all your child elements are qualified.
That's the effect of using the default namespace declaration -- all
child elements are qualified by the default namespace unless
specifically overrided which another namespace declaration. In other
words, this:
string
What kind of mapping do i have to do to process it.Can you give me any
example if you have with you or site that i can look upon.
Anne Thomas Manes wrote:
You should convert the arraylist to an array, and then define an
arrayMapping.
On 9/1/06, shrabank <[EMAIL PROTECTED]> wrote:
Hi,
Wh
In a RESTful system, a service has a *uniform* interface. When used in
conjunction with HTTP, the operations are GET, PUT, POST, DELETE, and
the semantics of those operations are defined by the HTTP protocol:
GET: return a representation of the resource
PUT: replace the representation of the reso
Hi Anne,
Thanks a lot for the response.
The request that I had attached was a request i had generated through a test harness and hence it is rpc/encoded.
The response however has the child elements unqualified.
We initially had rpc/encoded but changed to rpc/literal because SAP/XI did not su
You should convert the arraylist to an array, and then define an arrayMapping.
On 9/1/06, shrabank <[EMAIL PROTECTED]> wrote:
Hi,
What special mapping i have to do if i have to return an arraylist
from a service method in my wsdd.
If a bean is returned from the service method i do a Ty
Note the following errors based on your assertion that this is an
rpc/literal service:
- The input message is using RPC/encoded, and I'm quite sure that
SAP XI does not support RPC literal.
- The child element of the return wrapper element ()
is qualified, which is inconsisten
Hi All,
I am using Axis 1.3 rpc/literal style for my server and the client trying to access our webservice is an SAP XI client.
When I send the request:
http://schemas.xmlsoap.org/soap/envelope/
" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="
http://www.w3.org/2001/XMLS
Hi,
What special mapping i have to do if i have to return an arraylist
from a service method in my wsdd.
If a bean is returned from the service method i do a Type mapping
and gets the result.
This is what we do if we return a bean from a service method. Do i
have to do the similar s
Anne,
Thank you very much!
I really appreciate your responsive and insightful explanations,
arguments, and pointers.
I am also very excited to know the REST debate.
Unique interface is my first impression of REST, like the HTTP
protocol. Could I ask you another question on REST?
Is it a must tha
In my axis 1.4 web service, I send object with beansearializer, in some of them it have java.util.Date fields. If I send it as "xsd:dateTime" (java.util.Calendar) it send date and time, but with TimeZone offset changed.
If I send it as "xsd:date" (java.util.Date) it send only date and not time.¿How
Thanks for the response Ajith,
The support of JAX-WS will be very
useful! Will this feature be available in the next release of Axis
?
Regards,
Loïc
27 matches
Mail list logo
