New Posts New Posts RSS Feed: GlobalCache - EntityManagerProvider doesn't fire ManagerCreated
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

GlobalCache - EntityManagerProvider doesn't fire ManagerCreated
 Post Reply Post Reply
Author
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
cefernan View Drop Down
Groupie
Groupie


Joined: 13-Jul-2012
Posts: 70 		Post Options Post Options   Quote cefernan Quote  Post ReplyReply Direct Link To This Post Topic: GlobalCache - EntityManagerProvider doesn't fire ManagerCreated
    Posted: 02-Apr-2013 at 4:03pm
I chose the third option.

Thank you again.
Back to Top
mgood View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 18-Nov-2010
Location: Emeryville, CA
Posts: 583 		Post Options Post Options   Quote mgood Quote  Post ReplyReply Direct Link To This Post Posted: 02-Apr-2013 at 3:08pm
You have a few options to safely configure the EntityManagers once they are created. 

1. You can subclass the EntityManagerProvider and override the CreateEntityManager method. 

2. You can handle the static EntityManager.EntityManagerCreated event.

3. Or you can do it in the EntityManagerProvider.ManagerCreated event just like how the repository is populating the cache. 
Back to Top
cefernan View Drop Down
Groupie
Groupie


Joined: 13-Jul-2012
Posts: 70 		Post Options Post Options   Quote cefernan Quote  Post ReplyReply Direct Link To This Post Posted: 02-Apr-2013 at 2:30pm
Marcel, you are completely right!

I found my mistake. This line in the constructor of UnitOfWorkBase was the problem:
entityManagerProvider.Manager.VerifierEngine.PropertyNameToDisplayNameTranslator += PropertyNameToDisplayNameTranslator;
I was accessing the Manager before install the OnManagerCreated handler. I removed this line and now everything is perfect.

Thank you!!!

Now, I'll find a better place to translate the property names.
Back to Top
mgood View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 18-Nov-2010
Location: Emeryville, CA
Posts: 583 		Post Options Post Options   Quote mgood Quote  Post ReplyReply Direct Link To This Post Posted: 02-Apr-2013 at 1:49pm
Also, the TempHire Harness is not using the global cache. The Harness uses a single shared EntityManager instead. You will see that the GlobalCache class is not part of the Harness project, so it's not being found at runtime and in addition the Harness bootstrapper registers the EntityManagerProvider as a singleton.
Back to Top
mgood View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 18-Nov-2010
Location: Emeryville, CA
Posts: 583 		Post Options Post Options   Quote mgood Quote  Post ReplyReply Direct Link To This Post Posted: 02-Apr-2013 at 1:43pm
That means the EntityManager has already been created at the time you install the OnManagerCreated handler. The EntityManager gets created the first time the Manager property of the EntityManagerProvider is accessed. Your application must be accessing the Manager property before you get a chance to install the handler. 

Make sure that each UnitOfWork actually gets a new instance of the EntityManagerProvider injected and that its Manager property is not accessed before each of the repositories is fully instantiated. 

To ensure that you get a new instance make sure you have attributed the entityManagerProvider parameter with the NonShared creation policy as it is done in TempHire.

        [ImportingConstructor]
        public ResourceMgtUnitOfWork(
            [Import(RequiredCreationPolicy = CreationPolicy.NonShared)] IEntityManagerProvider<TempHireEntities>
                entityManagerProvider,
            [Import(AllowDefault = true)] IGlobalCache globalCache = null)
            : base(entityManagerProvider)
        {
	   ...
        }
Back to Top
cefernan View Drop Down
Groupie
Groupie


Joined: 13-Jul-2012
Posts: 70 		Post Options Post Options   Quote cefernan Quote  Post ReplyReply Direct Link To This Post Posted: 02-Apr-2013 at 12:55pm
Hi guys,

I've written a structure of global cache exactly like TempHire does. 

So, in the constructor of my GlobalCacheRepository:
entityManagerProvider.ManagerCreated += new EventHandler<EntityManagerCreatedEventArgs>(OnManagerCreated)
    .MakeWeak(eh => entityManagerProvider.ManagerCreated -= eh);
And:
internal void OnManagerCreated(object sender, EntityManagerCreatedEventArgs e)
{
    if (_globalCache == null) return;
 
    Seed(e.EntityManager);
 
    e.EntityManager.Cleared += new EventHandler<EntityManagerClearedEventArgs>(OnCleared)
        .MakeWeak(eh => e.EntityManager.Cleared -= eh);
}
internal void OnCleared(object sender, EntityManagerClearedEventArgs e)
{
    Seed(e.EntityManager);
}
private void Seed(EntityManager entityManager)
{
    var entities = _globalCache.Get<T>();
    entityManager.ImportEntities(entities, MergeStrategy.OverwriteChanges);
}
But, when I run the app I realize that the method  OnManagerCreated is never fired. Consequently, the ViewModel loads no results in my objects that read my global cache entities.

The method LoadAsync() in GlobalCache contains the cached entities that I need.

So, if I implement IDiscoverableViewModel in the same ViewModel and run the app through Harness, the global cache starts to work.

I think my mistake is something related to MEF.
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down