Ok.  I don't expect that generic will add value to extser, but they can be used to strongly type some of its internal collections. -b


From: jdbm-developer-bounces@lists.sourceforge.net [mailto:jdbm-developer-bounces@lists.sourceforge.net] On Behalf Of 'Kevin Day'
Sent: Monday, July 14, 2008 5:33 PM
To: JDBM Developer listserv
Subject: Re: [Jdbm-developer] Generics migration

I think a 2 week delay is just fine (things compile).
 
I'm still waiting on responses from the others to my question about whether it makes sense to attempt to genericize the caches...
 
- K
 
----------------------- Original Message -----------------------
  
From: "Bryan Thompson" <bryan@systap.com>
To: "'Kevin Day'" <kevin@trumpetinc.com>, "'JDBM Developer listserv'" <jdbm-developer@lists.sourceforge.net>
Cc: 
Date: Mon, 14 Jul 2008 04:43:46 -0400
Subject: RE: [Jdbm-developer] Generics migration
  
Kevin,
 
I can do it, but it will be at least two weeks.  I'm currently on the road and I need my own desk and some clear space to do this.
 
Do things compile?  Generics often add little value.  if they compile, then I hope my being on the road is not going to hold anyone back.  Or is the situation more dire?
 
-bryan


From: jdbm-developer-bounces@lists.sourceforge.net [mailto:jdbm-developer-bounces@lists.sourceforge.net] On Behalf Of 'Kevin Day'
Sent: Monday, July 14, 2008 12:03 PM
To: JDBM Developer listserv
Subject: Re: [Jdbm-developer] Generics migration

I think at this point, what is needed is someone to go through and add generics to extSer.  The other packages are all areas that many of us are familiar with, and are comfortable changing.  extSer is really your baby, and I don't think anyone else on the dev list has even worked with it.  Any chance of your taking an hour and genericizing the extSer packages?
 
Thanks!
 
- K
 
----------------------- Original Message -----------------------
  
From: "Bryan Thompson" <bryan@systap.com>
To: "'Kevin Day'" <kevin@trumpetinc.com>, "'JDBM Developer listserv'" <jdbm-developer@lists.sourceforge.net>
Cc: 
Date: Fri, 11 Jul 2008 11:59:18 -0400
Subject: RE: [Jdbm-developer] Generics migration
  
Kevin,
 
Sure - you can add default serializer ids.
 
Anything specific that you need help on with generics for extSer?
 
You don't have to worry about backward compatibility on my sake.
 
-bryan


From: jdbm-developer-bounces@lists.sourceforge.net [mailto:jdbm-developer-bounces@lists.sourceforge.net] On Behalf Of Kevin Day
Sent: Tuesday, July 08, 2008 10:41 AM
To: JDBM Developer listserv
Subject: [Jdbm-developer] Generics migration

I did some more genericizing work this evening.  Came up with three points that I think need to be discussed a tad.  Also, Bryan - we are going to need your help with genericizing the extser stuff - I don't think anyone else has used it, and I don't want to mess up backwards compatability with anything.
 
Item 1:
I think that a decision needs to be made on CachePolicy (and various sub-classes) about whether
this should be genericised or not.  The issue is that in the grand
scheme of things, CachePolicy represents a truly arbitrary mapping
between any key type and any value type.  I suspect that attempting to
add generics to this area of jdbm may not be desirable.

Item 2:
Because generics aren't covariant, it's going to be a right bugger to
adjust things so there are no warnings.  We'd have to basically ditch
the user of arrays (replacing them with ArrayList) in order to make this
work.  I'm not sure if there is any overhead in doing so, or if it is
even worth it.  Might be better off just suppressing the warning on
certain classes once we know they are properly genericised.  BPage is
one such example.

Item 3:
 
In the extser stuff, I'm getting warnings about missing serialversionid - is it OK to just add a default value of 0, or are these classes ever actually serialized using standard Java serialization?