Icefaces performance3/8/2023 ![]() You can either fix the design by having everything loaded before the transaction is closed, or you use Toplink as your persistence provider. This is not technically correct so if your application is relying on this happening, it is bad design. I'm going to take a wild guess here that Glassfish V2 was using Toplink, because Toplink has the magic trick that it can reopen transactions after they're closed so lazy loading can always succeed. In any case, each server comes with its own persistence provider. And you get no errors relating to lazy initialization? All entities relations in my project are marked as Lazy because performance reason. Collection contains records, but properties are empty. For some reasone the OneToMany relation is not loaded properly. There is a masterEntity and the relation is subRecors. And I need to create table on these subrecords. So there is a master entity which has a OneToMany relations. I need to use lazy loading for example with jsf or icefaces datatable. Vaadin is certainly superior to any other framework other than perhaps Wicket in terms of performance however this type of UI Framework has one important drawback in my mind: you are locked into coding in pure Java so the separation of skill sets which you would normally use for building a Frontend, middle and backend is not as good as for JSF. When I used Glassfish V2 server, everything was fine, but on Weblogic 10.35 this stuff does not work. I have a problem with lazy loading values with value expressions on JSF page.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |