search

Norqy / warp-persist

Automatically exported from code.google.com/p/warp-persist
0 stars 0 forks source link

Statically check @Finder queries at start time #13

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
We should scan all DAs registered via addAccessor() at start time and compile 
the non-named 
queries in @Finder to ensure they are OK.

This may require opening a unit of work.

Original issue reported on code.google.com by dha...@gmail.com on 23 Aug 2008 at 11:07

GoogleCodeExporter commented 9 years ago 
Does that also mean we would have to start the PersistenceService? I guess so. 
Given
that you can only start it once, this means we will _always_ open the
PersistenceService at startup. I don't think that would be acceptable.

Original comment by robbie.v...@gmail.com on 9 Sep 2008 at 10:07

GoogleCodeExporter commented 9 years ago 
Can't we check on HibernatePersistenceService.start() by injecting the list of 
accessors?

Original comment by dha...@gmail.com on 9 Sep 2008 at 11:34

GoogleCodeExporter commented 9 years ago

Original comment by robbie.v...@gmail.com on 21 Dec 2008 at 5:40