ications too
tightly coupled,
when data format evolves, object binding tends to break applications...
- Original Message - From: "Dennis Sosnoski" <[EMAIL PROTECTED]>
To:
Sent: Friday, August 18, 2006 2:44 PM
Subject: Re: [Axis2] Reading POJOs at client side
Even refl
ghtly coupled,
when data format evolves, object binding tends to break applications...
- Original Message - From: "Dennis Sosnoski" <[EMAIL PROTECTED]>
To:
Sent: Friday, August 18, 2006 2:44 PM
Subject: Re: [Axis2] Reading POJOs at client side
Even reflection-based data bind
uot;Dennis Sosnoski" <[EMAIL PROTECTED]>
To:
Sent: Friday, August 18, 2006 2:44 PM
Subject: Re: [Axis2] Reading POJOs at client side
Even reflection-based data binding can be faster than working with object
models - but in this case, it looks like the BeanUtil code used for the
co
where as I can easily create POJOs from my data.
>> Any recommendations.
>>
>>
>> -Original Message-
>> From: robert lazarski [mailto:[EMAIL PROTECTED]
>> Sent: Friday, August 18, 2006 2:51 PM
>> To: axis-user@ws.apache.org
>> Subject: Re: [Axis2] R
XML using OMElement's
>> API's where as I can easily create POJOs from my data.
>> Any recommendations.
>>
>>
>> -Original Message-
>> From: robert lazarski [mailto:[EMAIL PROTECTED]
>> Sent: Friday, August 18, 2006 2:51 PM
>> To: axis-use
PI's where as I can easily create POJOs from my data.
Any recommendations.
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Friday, August 18, 2006 2:51 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Reading POJOs at client side
AFAIK RPCMessageReceiver just f
I got my answer. Thanks a lot.
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Friday, August 18, 2006 3:35 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Reading POJOs at client side
OM has lots of performance advantages among many others so go with
that
essage-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Friday, August 18, 2006 2:51 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Reading POJOs at client side
AFAIK RPCMessageReceiver just follows the old jax-rpc JSR much in the
way axis 1.x does , and the integration tests reflect
OMElement's
API's where as I can easily create POJOs from my data.
Any recommendations.
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Friday, August 18, 2006 2:51 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Reading POJOs at client side
AFAIK RPCMessa
stions?
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Friday, August 18, 2006 1:16 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Reading POJOs at client side
In the latest source there is some integration tests:
modules/integration/test/org/apache/axi
: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Friday, August 18, 2006 1:16 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Reading POJOs at client side
In the latest source there is some integration tests:
modules/integration/test/org/apache/axis2/rpc/RPCCallTest.java
That has some array
In the latest source there is some integration tests:
modules/integration/test/org/apache/axis2/rpc/RPCCallTest.java
That has some array examples and should get you started.
HTH,
Robert
http://www.braziloutsource.com/
On 8/18/06, Charak, Vikas <[EMAIL PROTECTED]> wrote:
Using RPCMessageReceiv
Using RPCMessageReceiver I was able pass person POJO to my client from a
web service
public User[] getUsers() {
return User array;
}
Now I have ,
public void addUsers(User[]) {
}
Any idea on writing a java client to send user arrays to addUsers method
of the same
13 matches
Mail list logo
