Skip to main content

Caz in care IValidatableObject.Validate nu este apelat

Daca in aplicatia voastra MVC in loc de Enterprise library pentru validare o sa fiti surprinsi ca exista cazuri cand metoda pentru validare nu este apelata asa cum v-ati astepta.
Folosind atributele HasSelfValidate si SelfValidate, putem sa validam un obiect. Atributul HasSelfValidate ne spune daca obiectul curent are un mecanism propiu de validare. Metoda care face validarea in interiorul obiectului nostru trebuie sa aibe atributul SelfValidation si urmatorul antet:
void numeMetoda( ValidationResults validationResults )
In cazul in care obiectul nu este valid putem sa adaugam pe validationResults mesajul dorit impreuna cu alte informatii precum: nume propietate si referinta la obiectul care nu este valid.
[HasSelfValidate]
public class Person
{
public int Age { get; set; }

public int Name { get; set; }

[SelfValidation]
public void Validate(ValidationResults validationResults)
{
if( Age < 0 )
{
validationResults.AddResult(new ValidationResult("Varsta este negativa", this, "Age", null,null);
}
if( string.IsNullOrEmpty( Name ) )
{
validationResults.AddResult(new ValidationResult("Numele nu este valid", this, "Name", null,null);
}
}
}
In cazul unei aplicatii MVC clasa noastra o sa aibe forma urmatoare:
public class Person : IValidatableObject
{
[Required]
public int Age { get; set; }

[Required]
public int Name { get; set; }

public IEnumerable[ValidationResult] Validate(ValidationContext validationContext)
{
if( Age < 0 )
{
yield return new ValidationResult("Varsta este negativa", new [] { "Age" });
}
if( string.IsNullOrEmpty( Name ) )
{
yield return new ValidationResult("Numele nu este valid", new[] { "Name"});
}
}
}
Mecanismul este exact la fel ca si cel cu atribute, doar ca implementam o interfata. Am putea spune ca cele doua implementări au același comportament pentru orice caz. Dar din pacate nu este adevarat. Pentru a doua implementare o sa apara cazuri cand metoda noastra de validare nu se apelează.
Daca Age sau Name nu este completat o observam ca metoda Validate nu este apelata. Totul apare din cauza atributului Required, care verifica daca s-a introdus o valoarea pentru propietatea marcata, iar daca valoarea nu a fost introdusa nu o sa apeleze metoda Validate. Acest comportament apare din cauza ca prima data se face validarea propietatiilor in functie de atirbutele cu care sunt decorate, iar doar apoi daca validarea a fost cu succes se apeleaza metoda noastra
Acest caz nu ar trebuii sa ne deranjeze in general. Dar trebe sa il avem in vedere pentru anumite cazuri. De exemplu faca avem o pagina unde un user se inregistreaza si acesta nu introduce numele, dar introduce parola, poate am dorii sa apara un mesaj in care sa ii se spuna ca parola nu este destul de sigura sau ceva asemanator.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too