Re: Point of discussion - attempts to use non-typesafe contructs overXML-RPC

[Steve Loughran <st...@iseran.com>]

----- Original Message -----
From: "Benjamin Tomasini" <bt...@neteverything.com>
To: <ax...@xml.apache.org>
Sent: Thursday, January 30, 2003 09:13
Subject: Point of discussion - attempts to use non-typesafe contructs
overXML-RPC


> In reading this list for a while, I have noticed that a lot of people
> have trouble (de)serializing things like Vectors, Lists, Maps, etc...
>
> I have found that the best way to use Axis / XML-RPC is to only use real
> typed objects such as arrays and concrete objects such as JavaBeans.  I
> don't see how Axis could operate well using a late-binding approach.
>
> So, with this trend, I have a couple of questions.  Feel free to state
> your opinion.
>
> In regards to XML-RPC

you mean SOAP, surely :)

>
> 1. Is it practical to consider serializing any of the Collection
> interfaces?  If so, is it safe?  When should this be considered?

depends on whether you want the far end to understand it or not...I prefer
not to send collections until there is a uniform standard in how the stuff
gets marshalled.

> 2. Should Axis users be encouraged to avoid such constructs over the
> wire and stick with strictly typed objects?

yep

>
> 3. Should this be made a part of the documentation?

what, like we add a section called  "What Axis can not send via SOAP" in the
user guide, say under this section?

http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-axis/java/docs/user-guide.h
tml#DataMapping

-steve

Re: Point of discussion - attempts to use non-typesafe contructs overXML-RPC

[Benjamin Tomasini <bt...@neteverything.com>]

On Thu, 2003-01-30 at 12:46, Steve Loughran wrote:
> 
> ----- Original Message -----
> From: "Benjamin Tomasini" <bt...@neteverything.com>
> To: <ax...@xml.apache.org>
> Sent: Thursday, January 30, 2003 09:13
> Subject: Point of discussion - attempts to use non-typesafe contructs
> overXML-RPC
> 
> 
> > In reading this list for a while, I have noticed that a lot of people
> > have trouble (de)serializing things like Vectors, Lists, Maps, etc...
> >
> > I have found that the best way to use Axis / XML-RPC is to only use real
> > typed objects such as arrays and concrete objects such as JavaBeans.  I
> > don't see how Axis could operate well using a late-binding approach.
> >
> > So, with this trend, I have a couple of questions.  Feel free to state
> > your opinion.
> >
> > In regards to XML-RPC
> 
> you mean SOAP, surely :)

I guess I mean non-document type services.

> 
> >
> > 1. Is it practical to consider serializing any of the Collection
> > interfaces?  If so, is it safe?  When should this be considered?
> 
> depends on whether you want the far end to understand it or not...I prefer
> not to send collections until there is a uniform standard in how the stuff
> gets marshalled.
> 
> > 2. Should Axis users be encouraged to avoid such constructs over the
> > wire and stick with strictly typed objects?
> 
> yep
> 
> >
> > 3. Should this be made a part of the documentation?
> 
> what, like we add a section called  "What Axis can not send via SOAP" in the
> user guide, say under this section?
> 
> http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-axis/java/docs/user-guide.h
> tml#DataMapping

I see.  It is the "limited" section where I think most people get
stuck.  I see the suggestion on arrays, too.

There are enough people that get stuck on this point, that I think some
best practices might be in order.  I am willing to work on some of them,
however, I don't consider myself an expert.

The main issue, I think, is for developers to realize that SOAP
endpoints ought to expose high level APIs, not lower-level
implementations.

> 
> -steve
>