lazy-loading

I have a Lazy collection that I want to initialize at will in my service/controller. At this moment I can do: Hibernate.initialize( myEntity.getListOfThings() ); This command is hibernate dependent and does not make the implementation of JPA transparent. Is there a JPA elegant way of doing this? Master Slave No, there's no JPA equivalent. You can learn if the object is loaded and than use one of the two options, either accessing the properties while the object is still attached to persistence context, what I typically see is calling size, just for the sake of initializing the collection

I'm trying to send NH entities through the wire using WCF. I've got a complex graph of lazy-loaded objects.. I tried to implement a custom DataContractSurrogate to force initialization when serializing. Here is the code : public class HibernateDataContractSurrogate : IDataContractSurrogate { public HibernateDataContractSurrogate() { } public Type GetDataContractType(Type type) { // Serialize proxies as the base type if (typeof(INHibernateProxy).IsAssignableFrom(type)) { type = type.GetType().BaseType; } // Serialize persistent collections as the collection interface type if (typeof

When writing CodeIgniter applications my controller actions tend to begin with a few lines as below: $this->load->model('abc_model'); $this->load->library('ijk'); And then (just for completeness) they're used as follows: $this->abc_model->fetch_123(); $this->ijk->do_something(); Would there be anything too wrong about extending MY_Controller so that the following was possible? $this->model('zbc_model')->fetch_stuff(); $this->library('ijk')->do_something(); Pros: Classes aren't loaded until they're actually used Wouldn't need to auto-load any classes using config/autoload.php Slightly cleaner

If I implement a Singleton either through holder idiom or double checked locking, but instead of calling 'getInstance()', use reflection to instantiate it, and then call 'getInstance()' on it, this would create two instances, breaking the pattern. So I add a static 'counter' member to the class, increment it in the class's private constructor, and throw an exception if it crosses '1'. But in that case, if I first instantiate through reflection, nobody else would be able to call 'getInstance()' without throwing an Exception. So how do I lazy load a Singleton yet prevent it from this attack? (I

I am trying to use packery as a layout for my gallery. I am using fancybox with the isotope gallery. I don't see fancybox being the issue. I'm using isotope v2 and the latest packery download. Every single other layout works, even the ones not included in isotope js like fitRows and fitColumns. But with packery I get this error from isotope: Uncaught Error: No layout mode: packery isotope.pkgd.js line 8 Here is an example on codepen: http://codepen.io/anon/pen/QwXEvr JS: jQuery('.fancybox').fancybox({ openEffect: 'none', closeEffect: 'none' }); $('#testing').isotope({ 'layoutMode': 'packery';