DevForce Community Forum : EntityServerSaveInterceptor + Verifier / Validate http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce 2010 : EntityServerSaveInterceptor + Verifier / Validate Wed, 13 May 2026 10:03:55 -700 Tue, 31 Jan 2012 11:54:47 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=3239 DevForce Community Forum http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ EntityServerSaveInterceptor + Verifier / Validate : Re: instance verifier not executed,... http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12588#12588 Author: DenisK
Subject: 3239
Posted: 31-Jan-2012 at 11:54am

Re: instance verifier not executed, I will be adding a feature request for this.

Re: Principal, yes, this issue has been previously brought up by others as well. We're going to be reviewing the design. For the time being, the most consistent way to access the Principal is to use Thread.CurrentPrincipal

No problem on the posting. It can go either way actually. :)


Edited by DenisK - 31-Jan-2012 at 1:56pm]]> Tue, 31 Jan 2012 11:54:47 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12588#12588 EntityServerSaveInterceptor + Verifier / Validate : Correct me if I'm wrong,... http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12582#12582 Author: midnit
Subject: 3239
Posted: 31-Jan-2012 at 5:37am

Correct me if I'm wrong, but, in this use case, are you asking for a way to access the user's principal inside your verifier?
 
Yes. In intial testing client-side I had used entity.EntityManager.Principal but of course this does not work once the verifier hits the server. We have had this basic discussion before regarding EntityManager.Principal being null on the server but I wasn't using Verifiers in that discussion. I believe another user chimed in saying it would be nice if it was populated.
 
Is there any way that already exists that I can access the Principal in a consistent manner between client and server in a verifier? I have worked around this but would love to remove the code :)
 
Sorry I kinda posted this in the wrong forum...it wasn't so Verifier specific when I first started thinking about it.
]]> Tue, 31 Jan 2012 05:37:56 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12582#12582 EntityServerSaveInterceptor + Verifier / Validate : Hi midnit, Ok, I added triggers... http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12579#12579 Author: DenisK
Subject: 3239
Posted: 30-Jan-2012 at 7:23pm

Hi midnit,

Ok, I added triggers and see that the verifier fires if a trigger is tripped - but the instance verifiers don't. I can call VerifierEngine.Execute(entity) but should I have to or do I have something wrong? 

I'm not sure if this is a bug or a feature request but looking at the code, it seems that the behavior is correct. We don't execute instance verifiers for entities queried in the EntityServerSaveInterceptor. For the time being, you have to call VerifierEngine.Execute(entity). Let me find out if this is something we can fix, implement or if this is intentional.

[snip]..........My instance verifier performs different validation based on the users security preferences - which are stored in the principal...except the principal is empty. These verifiers are only server side.

Correct me if I'm wrong, but, in this use case, are you asking for a way to access the user's principal inside your verifier?


Edited by DenisK - 30-Jan-2012 at 7:42pm]]> Mon, 30 Jan 2012 19:23:45 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12579#12579 EntityServerSaveInterceptor + Verifier / Validate : I will lump this in here since... http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12570#12570 Author: midnit
Subject: 3239
Posted: 28-Jan-2012 at 1:37pm

I will lump this in here since its all the same general area of code. When I fire the VerifierEngine.Execute(entity) in the ValidateSave method via the saveinterceptor I am not seeing a way to know who the user is performing the save. In the interceptor I know I can use this.Principal, but the EntityManager on the entity has no Principal value. My instance verifier performs different validation based on the users security preferences - which are stored in the principal...except the principal is empty. These verifiers are only server side.



Edited by midnit - 30-Jan-2012 at 6:50am]]> Sat, 28 Jan 2012 13:37:37 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12570#12570 EntityServerSaveInterceptor + Verifier / Validate : Ok, I added triggers and see that... http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12569#12569 Author: midnit
Subject: 3239
Posted: 27-Jan-2012 at 9:21pm

Ok, I added triggers and see that the verifier fires if a trigger is tripped - but the instance verifiers don't. I can call VerifierEngine.Execute(entity) but should I have to or do I have something wrong?

Edited by midnit - 30-Jan-2012 at 6:49am]]> Fri, 27 Jan 2012 21:21:33 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12569#12569 EntityServerSaveInterceptor + Verifier / Validate : It just hit me that it could also... http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12568#12568 Author: midnit
Subject: 3239
Posted: 27-Jan-2012 at 8:14pm

It just hit me that it could also be how I have declared the Verifiers. Here is one...
 

private static Verifier<NominationTbl> VerifyReceiptTransferPointDates()

{

DelegateVerifier<NominationTbl> v = new DelegateVerifier<NominationTbl>(null, VerifyReceiptTransferPointDatesCondition);

v.VerifierOptions.ExecutionModes = VerifierExecutionModes.Instance;

return v;

}

]]> Fri, 27 Jan 2012 20:14:19 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12568#12568 EntityServerSaveInterceptor + Verifier / Validate : I am using DevForce 6.1.0. I... http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12567#12567 Author: midnit
Subject: 3239
Posted: 27-Jan-2012 at 8:04pm

I am using DevForce 6.1.0.
 
I am saving an entity from the client, intercepting the save on the server, loading additional items and modifying them based on that entity, then saving all the changes.
 
What I am seeing is that after modifying the entities in the interceptor the verifiers don't fire on anything except the initial entity. I then moved the code to the ValidateSave (as opposed to ExecuteSave) and called base.ValidateSave after all my manipulation and it still only fires the verifiers on the initial entity that was trigger via the client.
 
They all commit to the database, but only one gets verified.
 
Is there any way to get the verifiers to fire on all the entities that I loaded up and modified in the interceptor? The entities are the same type as the initial one.


Edited by midnit - 27-Jan-2012 at 8:15pm]]> Fri, 27 Jan 2012 20:04:38 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=3239&PID=12567#12567