Hello all,

I was just moving the new catalog in, and with the api / main (interface / impl) split, I have run into a problem. Some of the catalog "api" is abstract classes. I could stick them in api but all of api is interfaces so I thought I should bring it up on the list.

Would people like to be able to :

1. Allow abstract classes as part of api, or
2. Force api to be only interfaces, and make people double up with interface/ abstract class pairs.

Personally I like 2, having api be all interfaces. Anyone else have any thoughts.

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to