RE: [sdo] ISSUE 27: Add generics to API

Hi Everyone,

If we give up on the HelperContext<DataObject> approach, at least for now, then I thing the least painful approach is to separate the get<T> and set<T> methods into a superinterface, say OldDataObjectAccessors, and have DataObject inherit from that. This at least gives us reasonable looking JavaDoc, even if it doesn’t help during code completion.

I will argue that we should then deprecate the OldDataObjectAccessor class, even if it is odd to create something and deprecate it in the same release. I know that users will experience a lot of yellow lines, but that’s simply reflecting the reality that they are using methods for which a better alternative now exists, and they should migrate.

If there’s agreement with the approach, I will generate the interfaces before next week’s call.

Best Regards,

Ron

From: Blaise Doughan [mailto:blaise.doughan@oracle.com]
Sent: Dienstag, 2. Februar 2010 13:30
To: sdo@lists.oasis-open.org
Subject: [sdo] Unable to attend today's call

Hello all,

I will not be able to attend today's call.

I prototyped the use generics to carve out a new "DataObject" class. The result was many "raw" class warnings and some duplicate methods. At this point I suggest we consider other approaches to refine the DataObject interface.

-Blaise

On 2010-01-26, at 1:53 PM, Frank Budinsky <frankb@ca.ibm.com> wrote:

Hi Blaise,

This is the old email (March 2008!) that had a proposal for a new simplified DataObject interface.

http://markmail.org/message/hvizk46vkesyjhvo?q=API+Cleanup+list:org.oasis-open.lists.sdo+date:200803+&page=1

There were a couple of new ideas in it that we decided not to pursue, but otherwise I think it's a good first pass at a much simplified DataObject API.

Frank.

sdo message