On 08/01/2008, at 2:36 AM, Mike Schrag wrote:
NSArray<MyEO> = ec.objectsWithFetchSpecification(spec, MyEO.class)
I think generic EOFS would be better ... Passing in Class objects
to fulfill generics always feels a bit like hackery. It's really
cheating -- you're basically casting without using cast syntax,
because you can't enforce that the class you put in is actually
related to the objects of the fetch spec in any way, so it's as
unsafe as an arbitrary cast.
public <T> NSArray<T> objectsWithFetchSpecification
(EOFetchSpecification<T> fetchSpec) { ... }
then
EOFetchSpecification<Person> fetchSpec = ...;
NSArray<Person> people = ec.objectsWithFetchSpecification(fetchSpec);
The other problem this all poses (i.e., using Class objects) is what
to do when the particular class object for an entity (e.g., a
subclass of the framework's java classes) is determined at runtime
via Properties?
Any fetchspecs in the framework, if forced to pass in a class object
to either the fetchSpec or otherwise, could cause an error because WO
would not have that class registered for any entities in the runtime...
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
