Re: Dynamic Mapping

"Fabio Maulo" <[email protected]> Sat, 19 Jul 2008 10:26:01 -0300
Newsgroups gmane.comp.windows.dotnet.nhibernate.devel
Message-ID <[email protected]>
2008/7/19 Andreas Karlsson <[email protected]>:

> Hello everyone,
>
> after looking into it a little bit more a few other questions has
> popped up, I hope it's OK I ask them on the list, if not please direct
> me to the appropriate place.
>
> Questions I have at the moment is:
>
> 1: Should EntityName include assembly Name (to ease migration of Java
> functionality I think not but this might be an NH convention?)


The EntityName is the FullName only when the user don't specify nothing else
in the mapping.
This mean:
class name="MyEnterprise.MyProduct.MyNS.MyClass" entity-name="MyEntityName"
In this case the entityName is "MyEntityName".


>
>
> 2: Caching today uses (Configuration.SetCacheConcurrencyStrategy(..)
> uses Type as parameter but Java uses string, Type doesn't work very
> well with Dynamic mapping as the only type is Hashtable. Should it be
> rewritten to use strings, or overload to allow strings as well. Just
> removing current implementation would brake backwards compatibility.


Take care because you have an overload using strings (the overload for
collection roles).
In H3.2 the method for collection is setCollectionCacheConcurrencyStrategy.
On the trunk we are working to enable the 3 entity mode :
        Poco,  Map,   Xml
where "Map" is Hashtable.


>
> 3: How would I go by sharing my work with someone who has commit
> status, start a JIRA task and add the diff there and someone would
> take a look? These functions has the effect of me having to change
> code a bit every here and there...


Like you can see in trunk there are a lot of work done to support
EntityMode.Map.
To real enable it we need to write (port) tests to be sure we are supporting
same behavior of H3.2.
If you want help us please start from tests.
Contact me in private to coordinate the work to do.


>
>
> 4: When I checked out the latest SVN 3-5 test didn't execute properly,
> is this expected behavior at the moment?


Which tests ? There are some specific test that not work in MSSQL2005
dialect but they are marked with "Ignore" (look at the message of the
failing test if you are using R# )

Thanks for your help.
Fabio Maulo

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Nhibernate-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nhibernate-development