I don’t get those problems in batches. But I re-use all my backend services in my batches. For me a batch is more or less just a different ‚client’. I don’t care whether my CustomerStorageService gets called by JSF, JSP, Vaadin, @WebService or a batch :) But most of the time the entry point is JSF or some other frontend technology. And batch is just a way to ’script’ this basically. (Ofc there are other kind of batches, but you get the idea - it’s all about code reuse across different parts of the app).
LieGrue, strub > Am 05.03.2015 um 19:45 schrieb Romain Manni-Bucau <[email protected]>: > > hmm think I got the idea but this doesnt work neither since then you prevent > several features of JBatch to be used (split for instance) + not sure why > you'd get lazy loading issue since chunks are done in a snigle tx > > > Romain Manni-Bucau > @rmannibucau | Blog | Github | LinkedIn | Tomitriber > > 2015-03-05 19:38 GMT+01:00 Mark Struberg <[email protected]>: > > So why having @requestScoped in your backend // let close the troll here > > for that > Because transaction scoped EM doesn’t work quite often because JPA sucks when > it comes to lazy loading :) > > LieGrue, > strub >
