- Original Message -
From: "Rajal Shah" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 19, 2002 15:51
Subject: RE: Design question on using Java classes v/s hashes or arrays
> I see your point.. If business functionality changes though,
> -Original Message-
> From: Bill de hÓra [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 19, 2002 12:33 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Design question on using Java classes v/s hashes
> or arrays
>
>
> Garbis, Jason wrote:
>
>
-Original Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 11:06 AM
To: [EMAIL PROTECTED]
Subject: Re: Design question on using Java classes v/s hashes or arrays
- Original Message -
From: "Rajal Shah" <[EMAIL PROTECTED]>
To: &
- Original Message -
From: "Rajal Shah" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 19, 2002 10:27
Subject: RE: Design question on using Java classes v/s hashes or arrays
> Referring to more discussions on the Internet about versioning o
Referring to more discussions on the
Internet about versioning of web services, this is what I
recommend:
We need to create a versioning plan for our service that
is extensible and one that also guarantees backward compatibility. I've tried
out several approaches and that the best practic
Garbis, Jason wrote:
Your option 1 below, is pretty distasteful, since you're bypassing any typechecking, and (more importantly) excluding
important information from the WSDL metadata. That is, a user would
have to consult some external metadata to understand what is and
isn't valid input. Thi
Hi folks,
Rajal, you've hit on one of the difficulties of using WS for building a distributed
system.
WS is not a design center, it's a set of communication protocols.
That is, there's no "there" there.
Unlike OO systems (like CORBA, or COM, or even EJB) there's nothing to "hang your hat
on"
