[ http://216.121.112.228/browse/NH-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo closed NH-2680.
---------------------------
Resolution: Won't Fix
> NH does not create proxies for components on query
> --------------------------------------------------
>
> Key: NH-2680
> URL: http://216.121.112.228/browse/NH-2680
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.2.0Alpha2
> Reporter: Lucian Bargaoanu
> Priority: Minor
> Attachments: NhConfiguration.cs
>
>
> I'm using uNhAddIns which always uses proxies, not simple types. The problem is that a LINQ query doesn't return proxies for components. You can workaround the problem using a custom component tuplizer (which seems way too difficult to setup in code). I believe that the root cause is in AbstractComponentTuplizer which calls the virtual method BuildInstantiator in its constructor. The PocoComponentTuplizer ovverides BuildInstantiator and tries to use the optimizer setup in its constructor that didn't have a chance to run yet. So it finds the optimizer null and so it returns the simple type, not a proxy. I've attached my workaround.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
