src/NHibernate.Test/DynamicEntity/package.html

<html>
<head></head>

<body>
<p>
	Demonstration of different ways to use NHibernate to represent your domain
	model as a series of Castle dynamic proxies.  We map the interfaces and then
	use one of two approaches to get NHibernate to recognize these proxies as
	domain entities.  Really this is demonstrating various "entity representation"
	capabilities built in to NHibernate2.1.
</p>
<p>
	First we use an interceptor-based approach where we use a custom Interceptor
	implementation for interpret incoming proxies (and resolve them to the correct
	mappings) and to help NHibernate instantiate these proxy instances.  This is the
	quick-and-dirty approach.  It is fully expected that this approach will
	encounter certain limitations.
</p>
<p>
	Next we explore the notion of a Tuplizer and plug in custom Tuplizers to
	help achieve the same results.  Currently, Tuplizers do not have a chance
	to influence the resolution of entity-name given a potential entity, so we
	also use an Interceptor here and supply its GetEntityName() impl.  This is
	simply so we do not need to supply the entity name explicitly to the NHibernate Session calls.
</p>
</body>

</html>