lazy-loading

Is it possible to initialize the Instance of a Singleton when it is really needed? Consider this pattern taken from the famous "Design Patterns": class Singleton { public: static Singleton* Instance(); protected: Singleton(); private: static Singleton* _instance; } Singleton* Singleton::_instance = 0; // unit.cpp static Singleton* Singleton::Instance() { if (_instance == 0) { _instance = new Singleton; } return _instance; } Now, I think there is a problem in the pattern there, if one desires to provide the Singleton in a library to others: if the user calls Singleton::Instance() from another

Hey I am developing an desktop application using Spring and Hibernate, and I have a problem with lazy initiation. I looked in the web and every solution is related to the open session in view pattern, but I can't use this pattern. I've also tried to get the sessionfactory from the HibernateTemplate , but it returns to me a disconnected session. Does anyone know other solution? I would suggest that you basically have two solutions: Make arrangements to keep a Hibernate session open when you access a lazy-initialized object or collection. That means you're going to have to carefully mark your

I am having issues with the lazy loading. I have the following dbcontext. public virtual DbSet<AccountGroupMst> AccountGroupMst {get; set;} I have enabled the lazy loading. services.AddDbContext<DBContext>(x => x.UseSqlServer(Configuration.GetConnectionString("Test")) .UseLazyLoadingProxies()); Model, I have virtual and it is a self referencing table. public class AccountGroupMst { [Key] [Required] public int AccountGroupId { get; set; } [MaxLength(255)] [StringLength(255)] [Required] public string AccountGroupName { get; set; } [ForeignKey("ParentAccountGroupId")] public int?

app define(['angular', 'angular-ui-router', 'ocLazyLoad', 'config/common', 'layout/services/menuService'], function(angular) { 'use strict'; var $stateProviderRef = null; var $urlRouterProviderRef = null; return angular.module('app', ['ui.router', 'oc.lazyLoad', 'app.common', 'app.layout']); }); app.config define(['app'],function(app){ app.config(function($locationProvider, $stateProvider, $urlRouterProvider, $ocLazyLoadProvider) { $urlRouterProviderRef = $urlRouterProvider; $stateProviderRef = $stateProvider; $urlRouterProviderRef.otherwise('/'); $locationProvider.html5Mode({enable: true,

According to what I've read in the documentation and forums , you enable deep-linking via : forRoot(appRoot, config, deepLinkConfig) @ngModule({ .. IonicModule.forRoot(MyApp, {}, { links:[{ component: ContactPage, name: "contact", segment: "contact"}, { component: HelloPage, name: "hello", segment: "hello" } ] }) ... }) ... This leads to adding ContactPage and HelloPage to declarations and entryComponents arrays within @ngModule , which would not be lazy-loaded. So, this leads to the question, can you substitute strings, doing away with the imports and double array declaration, and have this?

I would like to get some clarification regarding lazy loading and session boundaries etc. My code structure is as follows @Entity class A { .... @OneToOne(fetch=LAZY) private B b; .. } @Entity class B { private id; private name; } @Transactional(SUPPORTS) ADao { A findById(int id); } @Transactional(SUPPORTS) LayerDB { A getAForId(int i) { return adao.findById(i); } } //Note that there is no transactional attribute here LayerB { public boolean doSomethingWithAandB(int aId) { A a = LayerDB.getAForId(aId); if(a.getB().getName().equals("HIGH")) return true; return false; } } //start transaction

My Solution consists of 3 different projects: EJB project with Netbeans auto-generated Facades to manage Entity classes and the persistence.xml Class-Library that holds all @Entity annotated and statically weaved database classes and the remote interfaces for the facade ejb's (shared between EJB and stand-alone client) Stand-alone Client that consists mainly of Swing GUI classes I use Glassfish 3.1.2, Eclipselink 2.3 as JPA-provider, Netbeans 7.1.1 and a MySQL database. I configured an Ant-task that statically weaves my entity classes on the basis of the persistence.xml. I have several