Hi Thomas! I'm not quite sure what 'uninitialised' means in that regard.
Either you have an EntityManager at hand - then *all* JPA is initialised. Or you don't, then it should already blow up with accessing ANYTHING Hibernate - not only very deep inside it. I think we will need a bit more information about how your setup works. LieGrue, strub > Am 14.11.2019 um 11:03 schrieb Thomas Frühbeck <t.fruehb...@gmail.com>: > > Hi Gerhard, > thank you for your reply, at first thought I meant to accept it for a > correct answer to my problem. > After pondering over it for some time I am less convinced. > > AFAIK the problem comes from Deltaspike Data using uninitialized > resources, where initialization needs are not really obvious to the > user. > My debugging has shown, that the repository passes objects to the jpa > layer, who's initialization I havent ever seen yet (sorry for my lack > of insight). > > The question is: is it correct for a framework like Deltaspike to use > (and pass on to lower levels) uninitialized resources, who's > initialization is generally hidden to the application, and therefore > initialization logic is typically not part of application code? > > Regards, > Thomas > > ---- dev@deltaspike.apache.org wrote ---- > >> hi thomas, >> >> since your repository works basically and the NPE occurs in hibernate, >> it sounds like a hibernate init-bug.
