Hi Anne,

Thanks for your reply.   Very good question.   I would
say the biggest reason is for use through firewalls.   My web
services are distributed around the world, and they are behind
firewalls.   RMI doesn't work well with this environment.   What
are your thoughts about that?   Do you have any other suggestions
about transmitting large amounts of data via web services?  Or
other better means?



Thanks,

A


----- Original Message ----
From: Anne Thomas Manes <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Saturday, June 9, 2007 2:27:08 PM
Subject: Re: Axis2 1.2 sanity check: Can generated POJO service/client handle 
0-length array?

Why aren't you just using RMI?

On 6/9/07, Airline Pedestal <[EMAIL PROTECTED]> wrote:
>
> Hi Anne,
>
> I completely agree with you points about interoperability and
> clean separation.
>
> Although, I have a situation where extremely large return pay loads
> make using XML very slow and sometimes impossible.   So I've started
> shipping Java Serialized objects via attachments with Axis2.
> My main goal is to handle very large pay load quickly.   Interoperability
> is second priority.   What are your thoughts about that?
>
>
> Thanks,
>
> A
>
>
>
> ----- Original Message ----
> From: Anne Thomas Manes <[EMAIL PROTECTED]>
> To: axis-user@ws.apache.org
> Sent: Saturday, June 9, 2007 1:12:32 PM
> Subject: Re: Axis2 1.2 sanity check: Can generated POJO service/client handle 
> 0-length array?
>
> I have to disagree with you -- at least if your goal is
> interoperability. XML is the external interface to your service, and
> it's a useful practice to maintain a clean separation of concern
> between your interface and your implementation. I trust you recognize
> the value of clean separation between your application object model
> and a database data model and the DAO design pattern. The same
> benefits exist when maintaining the separation between your externally
> facing XML model and your internal object model.
>
> There is an impedance mismatch between XML data structures and Java
> object models, just as there is an impedance mismatch between SQL data
> models and Java object models. In many cases the mismatch is
> insignificant, but it's a bad idea to assume that it doesn't exist.
>
> I agree that Axis2 could handle POJO deployment better, but even if it
> were the best that it could be, I seriously doubt that it could handle
> everything automatically.
>
> Anne
>
>
>
>
>
>
>
>
> ____________________________________________________________________________________
> Sick sense of humor? Visit Yahoo! TV's
> Comedy with an Edge to see what's on, when.
> http://tv.yahoo.com/collections/222
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






       
____________________________________________________________________________________
Moody friends. Drama queens. Your life? Nope! - their life, your story. Play 
Sims Stories at Yahoo! Games.
http://sims.yahoo.com/  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to