HunabKu

Validation Abstraction: Custom

2009-11-02T19:00:00.000-03:00

If you have read this post you know I’m having some psychological problem at work: multi-personality. My dear friend Fabio-NHV said me: hey man! I have a very good OSS validation framework strongly recommended if you are validating entities you are using with NHibernate. And I said: Cool!! but your framework is only an option for me… soon or later I’ll use something else and, btw, I need to mix

Validation through persistence: not synchronized

2009-10-31T07:00:00.000-03:00

In this series you saw mostly the configuration of NHibernate.Validator through Loquacious (our configuration based on fluent-interface). What is the ValidationDef

Validation through persistence: synchronized

2009-10-30T07:00:00.000-03:00

This post is about one possible answer to the question mememem ask me in this post (ah… nice nick). The task is create a validator to validate the uniqueness, of an entity instance, using some properties’ values instead its POID (Persistence Object ID). The implementation public class BlogPost{ public string Title { get; set; } public DateTime Date { get; set; } public string Content {

NHibernate visual Class and mapping generator integrated with VisualStudio2010

2009-10-29T13:51:00.003-03:00

Do you remember this post ? Now Microsoft gave us a step-by-step guide : POCO Templates for the Entity Framework Fantastic!!! Now we need a good soul starting the integration with NHibernate to generate POCO and mappings. There will be a little difference: The POCO template generates Entities that supports change notification.

NHibernate.Validator & NHibernate

2009-10-29T07:00:00.001-03:00

The validation is defined as a classic cross cutting concern… well… if we are talking about that we need to validate something everywhere I can agree with that definition, but if we are talking about the validation of domain entities I don’t agree. The validation of a domain-entity shouldn’t happen in the persistence-layer nor in the presentation-layer and even less in the persistence itself.

NHibernate.Validator : Customizing messages (Message Interpolator)

2009-10-28T07:00:00.001-03:00

The message interpolator is the responsible of the messages translation/composition. In the coming soon version (NHV-1.2.0) we had increase its power (and refactorized its implementation). Has default NHV has two implementations: DefaultMessageInterpolatorAggregator and DefaultMessageInterpolator. What is the usual you have seen in NHibernate’s eco-system ? Yes, you are right: Injectability!!!

NHibernate.Validator : Customizing messages (bases)

2009-10-27T07:00:00.002-03:00

One of the most powerful feature of NHibernate.Validator is its way to manage messages. In this post are the bases of the massage customization. The Price In the last moth this blog was visited from 101 countries but NHibernate.Validator has only 8 translations. The available cultures are: en, es, it, fr, de, nl, lv, pl. Are you seeing the translation in your language ? you don’t ? What you

NHibernate.Validator : Extending ValidationDef

2009-10-26T05:00:00.006-03:00

In various applications I’m using my implementation of Range. public interface IRange

NHibernate.Validator : The “Satisfy” way of custom Validators

2009-10-24T07:00:00.000-03:00

The Satisfy (perhaps it sound familiar to some SharpTestsEx users ;) ). To show how it work the example is a constraint for Person.Name: a Name is significant when it has more than three characters, is composed by letters and the first letter is in uppercase. To create a that validator, in the classic way, we should create an Attribute implementing IRuleArgs and then a class implementing

NHibernate.Validator : Fine grained and polymorphic validation

2009-10-23T07:00:00.001-03:00

If you know that you can define constraints for classes, properties and even for field, what mean “Fine grained validation” ? In NHV, when you define a validator you are defining a validator for a System.Type… well… for real you can define a validator for various types but let me simplify the concept a little bit (parafrasando lo psico nano: “mi consenta”). In OOP the Type can be polymorphic

NHibernate.Validator : Extending Loquacious configuration

2009-10-22T07:00:00.002-03:00

The needs to extend the configuration come when you having some custom and reusable validators. For this post I will use a constraint to solve : if a string property is null or empty it is valid, but if it is not empty it must satisfy the minimal required number of characters. Creating the Validator The first step is create a class to hold the information needed during validation; in this case

Advanced NHibernate.Validator

2009-10-21T02:21:00.008-03:00

Since long time ago I’m not writing posts about the usage of NHibernate.Validator. I wrote the post “Diving in NHibernate.Validator” because I saw some wrong examples, and even a wrong usage in another framework using NHV. Yesterday, talking with José Romaniello, I have realized how much poor is our documentation and how few are our examples. I have decided to begin a new series of posts on NHV

NHibernate.Validator : easy Entity Validator via Loquacious

2009-10-19T02:13:00.002-03:00

In NHV (NHibernate.Validator) we have annoying issue regarding Entity validators (a validator for an entity instance). You need an entity-validator when the constraint involves more than one property. A simple and classic example is a range: public class Range{ public int Start { get; set; } public int End { get; set; }}To validate it, before today, you must create an Attribute to mark the

Fixing issues in NHibernate

2009-10-18T18:34:00.002-03:00

Was is perhaps I can rest a little bit and begin the implementation of a new feature in NHibernate.Validator.

NHibernate & WCF : session-per-call in uNhAddIns

2009-10-12T15:56:00.002-03:00

We have added a new project in uNhAddIns to work with NHibernate and WCF. As you know the most common, and probably the most recommended, way to manage the NH’s session in WCF is session-per-call. The session-per-call pattern has the same behavior of session-per-request where, in this case, call, NH’s session and NH’s transaction has the same life cycle. There are various ways to add this

OSS has users, commercial products has customers, ergo p&p is commercial product

2009-10-08T01:38:00.004-03:00

This is a long story and I will try to make it short. In the JAVA ecosystem some projects developers are trying to find a common way to define a specification for a specific problem. After the definition each project can/will implement specification in his way. For example, have a look : JSR 303 Bean Validation I know that ask the same attitude in .NET is something really hard… hopefully the

NHibernate dialect for SQL Azure

2009-10-04T02:31:00.002-03:00

As you read in this post there was a little problem running DAOs integration tests directly with SQL-Azure: “Heaps can not be replicated tables. Please create a clustered index for the table.” The problem is generated by this fact : Because SQL Azure does not support heap tables, a table must have a clustered index. If a table is created without a clustered constraint, a clustered index

How you shouldn’t write your mapping

2009-10-03T13:46:00.003-03:00

More than one time, in my courses, in this blog and in various NH’s users list, I talked about a rule of thumb about mappings: not try to be clear because it obscures. Have a look to this mapping:

Quick news: NHibernate with SQL-Azure

2009-09-28T12:38:00.002-03:00

Just ran DAOs integration tests (the same of this post) in SQL-AZURE. All work… even the SchemaExport. well…well… Not all glitters is gold ;) Exception: “Heaps can not be replicated tables. Please create a clustered index for the table.”

Testing DAOs : the SetUpFixture Attribute

2009-09-27T16:07:00.005-03:00

Usually I’m testing DAOs for CRUD operations. Using NHibernate, as persistent layer, what we are testing, in practice, is the mapping and all behavior we have defined in it (cascade, associations, types, user-types, custom-collections and so on). For CRUD operation I mean single entity instance CRUD without test complex queries (to test complex-queries I’m using a different test suite with a

Sharp Tests Ex 0.3.0 : fluent and lambda assertions for MsTests, NUnit and xUnit

2009-09-23T02:34:00.002-03:00

#TestsEx 0.3.0 was released yesterday. News The first news is that #TestsEx is no more a “one-man-show”; Jason Diamond is now part of the team. The second news is that the new syntax, based on lambda expression, is now available (similar to the one available in NUnitEx). You can see an example in the download page. var var2 = 2;2.Satisfy(a => var2 == a);1.Satisfy(a => a == 1 || a != 0);The

Repository or DAO?: DAO

2009-09-19T19:03:00.004-03:00

such question, no? DAO is the anachronism of Data Access Object. On the cloud you can find various definitions of what is a DAO. The follow come from Java ecosystem and is the most complete I found: The DAO implements the access mechanism required to work with the data source. The data source could be a persistent store like an RDBMS, an external service like a B2B exchange, a repository like an

Configure SessionFactory Providers

2009-09-17T01:38:00.003-03:00

This is about a pending task from long time ago… sorry for those waiting for it. In the AOP example of CpBT you probably saw a class named SessionFactoryProvider; that class was wrote before CpBT and it can be used in others Contexts (ICurrentSessionContext). ISessionFactoryProvider The ISessionFactoryProvider is the contract for the implementation responsible for providing NHibernate’s

Repository or DAO?: Repository

2009-09-13T17:25:00.004-03:00

such question, no? The definition of Repository pattern is extremely clear (as usual coming from where it come). What was not absolutely clear is how developers are using it… perhaps my interpretation of these words is a little bit extreme. A Repository mediates between the domain and data mapping layers, acting like an in-memory domain object collection. In .NET a Repository should look like:

NHibernate: Tree Re-parenting

2009-09-11T16:15:00.003-03:00

Did you heard about NHibernate and Hibernate re-parenting issue? I heard it many times in these years including in our JIRA. Depending on how you are managing your system there are various solutions to manage the re-parenting issue. The most common is set the cascade style to “all” and manage orphaned nodes in some way. The last time the user said: Nhibernate should handle cases where