I'm wanting to use Hibernate, but at least on of my classes is usually fetched via a Stored Procedure, not directly from a table.

To support SPs I'm using SpringFramework's JDBC support. Part of that lets me write a simple method that maps a single row of a ResultSet to an object and Spring takes care of the rest.

It occurs to me that Hibernate in its bowels must do the same thing: take a row of a ResultSet and return an object. I'm hoping some kind soul can point me to the write entry point of the source code -- possibly a class to subclass or at least to invoke as a helper...?

I've started digging on my own, but it got a bit dense and a pointer from someone more intimately familiar with the code would be a big help.

Loader does this.

However, usually this problem is solved using a custom persister, not a new Loader.

We will almost certainly add a standard StoredProcedurePersister in 2.2.

[quote="gavinHowever, usually this problem is solved using a custom persister, not a new Loader.[/quote]

Could you elaborate on the differences (or point to a link which goes into details)? I'm interested in the reading from the DB, so from the names of things Loader sounds right. What is the difference in this case?

Is there an easay way (e.g., via Configuration) to have Hibernate use a custom persister?

<class persister="...">

Yes, for a class, but I just want the persister to be used when a particular parent<->child relationship is traversed.... any pointers? The short of it is, the stored procedure in question must have the foreign key's value.