Menu
▾
▴
nhibernate-issues
|
From: Jeff G. (JIRA) <nh...@gm...> - 2011-03-10 00:05:29
|
Cannot Create Custom Persister for Collection Type
--------------------------------------------------
Key: NH-2568
URL: http://216.121.112.228/browse/NH-2568
Project: NHibernate
Issue Type: Bug
Components: Core
Affects Versions: 3.0.0.GA
Reporter: Jeff Greenland
Priority: Blocker
Encountered issue where setting a Persister Type on a collection property (specifically a type of List) would throw a NullPointerException when NHibernate initialized. Our persister, called MyPersister as a test, extended OneToManyPersister and only had a constructor defined which matched the constructor in the base class (OneToManyPersister). Here's our analysis as to why it looks like a bug:
Tracing through the code revealed that a constructor was not found on MyPersister matching the expected arguments. Those arguments are defined on line 34 of PersisterFactory.cs for CollectionPersister types and are Mapping.Collection, ICacheConcurrencyStrategy, and ISessionFactoryImplementor.
In the CreateCollectionPersister() method (line 68), if there is no persister class defined, it calls the OneToManyPersister implementation of ICollectionPersister with Mapping.Collection, ICacheConcurrencyStrategy, Configuration, and ISessionFactoryImplementor parameters. However, if a custom persister class is defined, it calls the Create() method (line 124) with the Configuration parameter missing, and consequently the Create() method does not invoke a matching constructor with that parameter.
It seems to us that since the default persister class of OneToManyPersister accepts the 4 argument constructor, and if you specified a custom persister that extends OneToManyPersister, the custom persister should accept the same 4 arguments. In other words, if I specify a custom persister on my class as OneToManyPersister (the same as the default), NHibernate would fail to initialize because it couldn't construct OneToManyPersister.
Looks related to NH-1957, which appears to have been immediately closed. I've included our diff below that seems to have fixed the issue.
Diff:
Index: PersisterFactory.cs
===================================================================
--- PersisterFactory.cs (revision 31412)
+++ PersisterFactory.cs (revision 31413)
@@ -31,14 +31,15 @@
// TODO: is it really necessary to provide Configuration to CollectionPersisters ? Should it not be enough with associated class ?
// or why does ClassPersister's not get access to configuration ?
- private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
+ private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
{
typeof(Mapping.Collection),
typeof(ICacheConcurrencyStrategy),
+ typeof(Configuration),
typeof(ISessionFactoryImplementor)
};
- /// <summary>
+ /// <summary>
/// Creates a built in Entity Persister or a custom Persister.
/// </summary>
public static IEntityPersister CreateClassPersister(PersistentClass model, ICacheConcurrencyStrategy cache,
@@ -78,10 +79,11 @@
}
else
{
- return Create(persisterClass, model, cache, factory);
+ return (ICollectionPersister) Create(persisterClass, model, cache, cfg, factory);
}
}
+
/// <summary>
/// Creates a specific Persister - could be a built in or custom persister.
/// </summary>
@@ -122,7 +124,7 @@
}
public static ICollectionPersister Create(System.Type persisterClass, Mapping.Collection model,
- ICacheConcurrencyStrategy cache, ISessionFactoryImplementor factory)
+ ICacheConcurrencyStrategy cache, Configuration cfg, ISessionFactoryImplementor factory)
{
ConstructorInfo pc;
try
@@ -136,8 +138,8 @@
try
{
- return (ICollectionPersister) pc.Invoke(new object[] {model, cache, factory});
- }
+ return (ICollectionPersister)pc.Invoke(new object[] { model, cache, cfg, factory });
+ }
catch (TargetInvocationException tie)
{
Exception e = tie.InnerException;
@@ -155,5 +157,6 @@
throw new MappingException("Could not instantiate collection persister " + persisterClass.Name, e);
}
}
+
}
}
--
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
|
|
[nhibernate-issues] [NHJIRA] Commented: (NH-2568) Cannot Create
Custom Persister for Collection Type
From: Jeff G. (JIRA) <nh...@gm...> - 2011-03-10 00:07:34
|
[ http://216.121.112.228/browse/NH-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20645#action_20645 ]
Jeff Greenland commented on NH-2568:
------------------------------------
Marked as a blocker because we were unable to find any way to specify a custom persister for a collection.
> Cannot Create Custom Persister for Collection Type
> --------------------------------------------------
>
> Key: NH-2568
> URL: http://216.121.112.228/browse/NH-2568
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0.0.GA
> Reporter: Jeff Greenland
> Priority: Blocker
>
> Encountered issue where setting a Persister Type on a collection property (specifically a type of List) would throw a NullPointerException when NHibernate initialized. Our persister, called MyPersister as a test, extended OneToManyPersister and only had a constructor defined which matched the constructor in the base class (OneToManyPersister). Here's our analysis as to why it looks like a bug:
> Tracing through the code revealed that a constructor was not found on MyPersister matching the expected arguments. Those arguments are defined on line 34 of PersisterFactory.cs for CollectionPersister types and are Mapping.Collection, ICacheConcurrencyStrategy, and ISessionFactoryImplementor.
> In the CreateCollectionPersister() method (line 68), if there is no persister class defined, it calls the OneToManyPersister implementation of ICollectionPersister with Mapping.Collection, ICacheConcurrencyStrategy, Configuration, and ISessionFactoryImplementor parameters. However, if a custom persister class is defined, it calls the Create() method (line 124) with the Configuration parameter missing, and consequently the Create() method does not invoke a matching constructor with that parameter.
> It seems to us that since the default persister class of OneToManyPersister accepts the 4 argument constructor, and if you specified a custom persister that extends OneToManyPersister, the custom persister should accept the same 4 arguments. In other words, if I specify a custom persister on my class as OneToManyPersister (the same as the default), NHibernate would fail to initialize because it couldn't construct OneToManyPersister.
> Looks related to NH-1957, which appears to have been immediately closed. I've included our diff below that seems to have fixed the issue.
> Diff:
> Index: PersisterFactory.cs
> ===================================================================
> --- PersisterFactory.cs (revision 31412)
> +++ PersisterFactory.cs (revision 31413)
> @@ -31,14 +31,15 @@
>
> // TODO: is it really necessary to provide Configuration to CollectionPersisters ? Should it not be enough with associated class ?
> // or why does ClassPersister's not get access to configuration ?
> - private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> + private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> {
> typeof(Mapping.Collection),
> typeof(ICacheConcurrencyStrategy),
> + typeof(Configuration),
> typeof(ISessionFactoryImplementor)
> };
>
> - /// <summary>
> + /// <summary>
> /// Creates a built in Entity Persister or a custom Persister.
> /// </summary>
> public static IEntityPersister CreateClassPersister(PersistentClass model, ICacheConcurrencyStrategy cache,
> @@ -78,10 +79,11 @@
> }
> else
> {
> - return Create(persisterClass, model, cache, factory);
> + return (ICollectionPersister) Create(persisterClass, model, cache, cfg, factory);
> }
> }
>
> +
> /// <summary>
> /// Creates a specific Persister - could be a built in or custom persister.
> /// </summary>
> @@ -122,7 +124,7 @@
> }
>
> public static ICollectionPersister Create(System.Type persisterClass, Mapping.Collection model,
> - ICacheConcurrencyStrategy cache, ISessionFactoryImplementor factory)
> + ICacheConcurrencyStrategy cache, Configuration cfg, ISessionFactoryImplementor factory)
> {
> ConstructorInfo pc;
> try
> @@ -136,8 +138,8 @@
>
> try
> {
> - return (ICollectionPersister) pc.Invoke(new object[] {model, cache, factory});
> - }
> + return (ICollectionPersister)pc.Invoke(new object[] { model, cache, cfg, factory });
> + }
> catch (TargetInvocationException tie)
> {
> Exception e = tie.InnerException;
> @@ -155,5 +157,6 @@
> throw new MappingException("Could not instantiate collection persister " + persisterClass.Name, e);
> }
> }
> +
> }
> }
--
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
|
|
From: Julian M. (JIRA) <nh...@gm...> - 2011-03-10 10:00:37
|
[ http://216.121.112.228/browse/NH-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Maughan updated NH-2568:
-------------------------------
Priority: Major (was: Blocker)
> Cannot Create Custom Persister for Collection Type
> --------------------------------------------------
>
> Key: NH-2568
> URL: http://216.121.112.228/browse/NH-2568
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0.0.GA
> Reporter: Jeff Greenland
> Priority: Major
>
> Encountered issue where setting a Persister Type on a collection property (specifically a type of List) would throw a NullPointerException when NHibernate initialized. Our persister, called MyPersister as a test, extended OneToManyPersister and only had a constructor defined which matched the constructor in the base class (OneToManyPersister). Here's our analysis as to why it looks like a bug:
> Tracing through the code revealed that a constructor was not found on MyPersister matching the expected arguments. Those arguments are defined on line 34 of PersisterFactory.cs for CollectionPersister types and are Mapping.Collection, ICacheConcurrencyStrategy, and ISessionFactoryImplementor.
> In the CreateCollectionPersister() method (line 68), if there is no persister class defined, it calls the OneToManyPersister implementation of ICollectionPersister with Mapping.Collection, ICacheConcurrencyStrategy, Configuration, and ISessionFactoryImplementor parameters. However, if a custom persister class is defined, it calls the Create() method (line 124) with the Configuration parameter missing, and consequently the Create() method does not invoke a matching constructor with that parameter.
> It seems to us that since the default persister class of OneToManyPersister accepts the 4 argument constructor, and if you specified a custom persister that extends OneToManyPersister, the custom persister should accept the same 4 arguments. In other words, if I specify a custom persister on my class as OneToManyPersister (the same as the default), NHibernate would fail to initialize because it couldn't construct OneToManyPersister.
> Looks related to NH-1957, which appears to have been immediately closed. I've included our diff below that seems to have fixed the issue.
> Diff:
> Index: PersisterFactory.cs
> ===================================================================
> --- PersisterFactory.cs (revision 31412)
> +++ PersisterFactory.cs (revision 31413)
> @@ -31,14 +31,15 @@
>
> // TODO: is it really necessary to provide Configuration to CollectionPersisters ? Should it not be enough with associated class ?
> // or why does ClassPersister's not get access to configuration ?
> - private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> + private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> {
> typeof(Mapping.Collection),
> typeof(ICacheConcurrencyStrategy),
> + typeof(Configuration),
> typeof(ISessionFactoryImplementor)
> };
>
> - /// <summary>
> + /// <summary>
> /// Creates a built in Entity Persister or a custom Persister.
> /// </summary>
> public static IEntityPersister CreateClassPersister(PersistentClass model, ICacheConcurrencyStrategy cache,
> @@ -78,10 +79,11 @@
> }
> else
> {
> - return Create(persisterClass, model, cache, factory);
> + return (ICollectionPersister) Create(persisterClass, model, cache, cfg, factory);
> }
> }
>
> +
> /// <summary>
> /// Creates a specific Persister - could be a built in or custom persister.
> /// </summary>
> @@ -122,7 +124,7 @@
> }
>
> public static ICollectionPersister Create(System.Type persisterClass, Mapping.Collection model,
> - ICacheConcurrencyStrategy cache, ISessionFactoryImplementor factory)
> + ICacheConcurrencyStrategy cache, Configuration cfg, ISessionFactoryImplementor factory)
> {
> ConstructorInfo pc;
> try
> @@ -136,8 +138,8 @@
>
> try
> {
> - return (ICollectionPersister) pc.Invoke(new object[] {model, cache, factory});
> - }
> + return (ICollectionPersister)pc.Invoke(new object[] { model, cache, cfg, factory });
> + }
> catch (TargetInvocationException tie)
> {
> Exception e = tie.InnerException;
> @@ -155,5 +157,6 @@
> throw new MappingException("Could not instantiate collection persister " + persisterClass.Name, e);
> }
> }
> +
> }
> }
--
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
|
|
[nhibernate-issues] [NHJIRA] Commented: (NH-2568) Cannot Create
Custom Persister for Collection Type
From: Julian M. (JIRA) <nh...@gm...> - 2011-03-10 10:03:35
|
[ http://216.121.112.228/browse/NH-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20646#action_20646 ]
Julian Maughan commented on NH-2568:
------------------------------------
The Priority reflects the importance/seriousness of the issue in the context of NHibernate, not the impact on your project.
> Cannot Create Custom Persister for Collection Type
> --------------------------------------------------
>
> Key: NH-2568
> URL: http://216.121.112.228/browse/NH-2568
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0.0.GA
> Reporter: Jeff Greenland
> Priority: Major
>
> Encountered issue where setting a Persister Type on a collection property (specifically a type of List) would throw a NullPointerException when NHibernate initialized. Our persister, called MyPersister as a test, extended OneToManyPersister and only had a constructor defined which matched the constructor in the base class (OneToManyPersister). Here's our analysis as to why it looks like a bug:
> Tracing through the code revealed that a constructor was not found on MyPersister matching the expected arguments. Those arguments are defined on line 34 of PersisterFactory.cs for CollectionPersister types and are Mapping.Collection, ICacheConcurrencyStrategy, and ISessionFactoryImplementor.
> In the CreateCollectionPersister() method (line 68), if there is no persister class defined, it calls the OneToManyPersister implementation of ICollectionPersister with Mapping.Collection, ICacheConcurrencyStrategy, Configuration, and ISessionFactoryImplementor parameters. However, if a custom persister class is defined, it calls the Create() method (line 124) with the Configuration parameter missing, and consequently the Create() method does not invoke a matching constructor with that parameter.
> It seems to us that since the default persister class of OneToManyPersister accepts the 4 argument constructor, and if you specified a custom persister that extends OneToManyPersister, the custom persister should accept the same 4 arguments. In other words, if I specify a custom persister on my class as OneToManyPersister (the same as the default), NHibernate would fail to initialize because it couldn't construct OneToManyPersister.
> Looks related to NH-1957, which appears to have been immediately closed. I've included our diff below that seems to have fixed the issue.
> Diff:
> Index: PersisterFactory.cs
> ===================================================================
> --- PersisterFactory.cs (revision 31412)
> +++ PersisterFactory.cs (revision 31413)
> @@ -31,14 +31,15 @@
>
> // TODO: is it really necessary to provide Configuration to CollectionPersisters ? Should it not be enough with associated class ?
> // or why does ClassPersister's not get access to configuration ?
> - private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> + private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> {
> typeof(Mapping.Collection),
> typeof(ICacheConcurrencyStrategy),
> + typeof(Configuration),
> typeof(ISessionFactoryImplementor)
> };
>
> - /// <summary>
> + /// <summary>
> /// Creates a built in Entity Persister or a custom Persister.
> /// </summary>
> public static IEntityPersister CreateClassPersister(PersistentClass model, ICacheConcurrencyStrategy cache,
> @@ -78,10 +79,11 @@
> }
> else
> {
> - return Create(persisterClass, model, cache, factory);
> + return (ICollectionPersister) Create(persisterClass, model, cache, cfg, factory);
> }
> }
>
> +
> /// <summary>
> /// Creates a specific Persister - could be a built in or custom persister.
> /// </summary>
> @@ -122,7 +124,7 @@
> }
>
> public static ICollectionPersister Create(System.Type persisterClass, Mapping.Collection model,
> - ICacheConcurrencyStrategy cache, ISessionFactoryImplementor factory)
> + ICacheConcurrencyStrategy cache, Configuration cfg, ISessionFactoryImplementor factory)
> {
> ConstructorInfo pc;
> try
> @@ -136,8 +138,8 @@
>
> try
> {
> - return (ICollectionPersister) pc.Invoke(new object[] {model, cache, factory});
> - }
> + return (ICollectionPersister)pc.Invoke(new object[] { model, cache, cfg, factory });
> + }
> catch (TargetInvocationException tie)
> {
> Exception e = tie.InnerException;
> @@ -155,5 +157,6 @@
> throw new MappingException("Could not instantiate collection persister " + persisterClass.Name, e);
> }
> }
> +
> }
> }
--
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
|
|
[nhibernate-issues] [NHJIRA] Commented: (NH-2568) Cannot Create
Custom Persister for Collection Type
From: Fabio M. (JIRA) <nh...@gm...> - 2011-03-21 14:26:53
|
[ http://216.121.112.228/browse/NH-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20682#action_20682 ]
Fabio Maulo commented on NH-2568:
---------------------------------
Which is the session-factory configuration value you have to read ?
> Cannot Create Custom Persister for Collection Type
> --------------------------------------------------
>
> Key: NH-2568
> URL: http://216.121.112.228/browse/NH-2568
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0.0.GA
> Reporter: Jeff Greenland
> Priority: Major
>
> Encountered issue where setting a Persister Type on a collection property (specifically a type of List) would throw a NullPointerException when NHibernate initialized. Our persister, called MyPersister as a test, extended OneToManyPersister and only had a constructor defined which matched the constructor in the base class (OneToManyPersister). Here's our analysis as to why it looks like a bug:
> Tracing through the code revealed that a constructor was not found on MyPersister matching the expected arguments. Those arguments are defined on line 34 of PersisterFactory.cs for CollectionPersister types and are Mapping.Collection, ICacheConcurrencyStrategy, and ISessionFactoryImplementor.
> In the CreateCollectionPersister() method (line 68), if there is no persister class defined, it calls the OneToManyPersister implementation of ICollectionPersister with Mapping.Collection, ICacheConcurrencyStrategy, Configuration, and ISessionFactoryImplementor parameters. However, if a custom persister class is defined, it calls the Create() method (line 124) with the Configuration parameter missing, and consequently the Create() method does not invoke a matching constructor with that parameter.
> It seems to us that since the default persister class of OneToManyPersister accepts the 4 argument constructor, and if you specified a custom persister that extends OneToManyPersister, the custom persister should accept the same 4 arguments. In other words, if I specify a custom persister on my class as OneToManyPersister (the same as the default), NHibernate would fail to initialize because it couldn't construct OneToManyPersister.
> Looks related to NH-1957, which appears to have been immediately closed. I've included our diff below that seems to have fixed the issue.
> Diff:
> Index: PersisterFactory.cs
> ===================================================================
> --- PersisterFactory.cs (revision 31412)
> +++ PersisterFactory.cs (revision 31413)
> @@ -31,14 +31,15 @@
>
> // TODO: is it really necessary to provide Configuration to CollectionPersisters ? Should it not be enough with associated class ?
> // or why does ClassPersister's not get access to configuration ?
> - private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> + private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> {
> typeof(Mapping.Collection),
> typeof(ICacheConcurrencyStrategy),
> + typeof(Configuration),
> typeof(ISessionFactoryImplementor)
> };
>
> - /// <summary>
> + /// <summary>
> /// Creates a built in Entity Persister or a custom Persister.
> /// </summary>
> public static IEntityPersister CreateClassPersister(PersistentClass model, ICacheConcurrencyStrategy cache,
> @@ -78,10 +79,11 @@
> }
> else
> {
> - return Create(persisterClass, model, cache, factory);
> + return (ICollectionPersister) Create(persisterClass, model, cache, cfg, factory);
> }
> }
>
> +
> /// <summary>
> /// Creates a specific Persister - could be a built in or custom persister.
> /// </summary>
> @@ -122,7 +124,7 @@
> }
>
> public static ICollectionPersister Create(System.Type persisterClass, Mapping.Collection model,
> - ICacheConcurrencyStrategy cache, ISessionFactoryImplementor factory)
> + ICacheConcurrencyStrategy cache, Configuration cfg, ISessionFactoryImplementor factory)
> {
> ConstructorInfo pc;
> try
> @@ -136,8 +138,8 @@
>
> try
> {
> - return (ICollectionPersister) pc.Invoke(new object[] {model, cache, factory});
> - }
> + return (ICollectionPersister)pc.Invoke(new object[] { model, cache, cfg, factory });
> + }
> catch (TargetInvocationException tie)
> {
> Exception e = tie.InnerException;
> @@ -155,5 +157,6 @@
> throw new MappingException("Could not instantiate collection persister " + persisterClass.Name, e);
> }
> }
> +
> }
> }
--
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
|
|
[nhibernate-issues] [NHJIRA] Commented: (NH-2568) Cannot Create
Custom Persister for Collection Type
From: Fabio M. (JIRA) <nh...@gm...> - 2011-03-21 14:33:54
|
[ http://216.121.112.228/browse/NH-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20683#action_20683 ]
Fabio Maulo commented on NH-2568:
---------------------------------
btw Jeff, what we need is not the patch (that will be another), what we need is a little tests or at least needed classes and mappings (at least...).
> Cannot Create Custom Persister for Collection Type
> --------------------------------------------------
>
> Key: NH-2568
> URL: http://216.121.112.228/browse/NH-2568
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0.0.GA
> Reporter: Jeff Greenland
> Priority: Major
>
> Encountered issue where setting a Persister Type on a collection property (specifically a type of List) would throw a NullPointerException when NHibernate initialized. Our persister, called MyPersister as a test, extended OneToManyPersister and only had a constructor defined which matched the constructor in the base class (OneToManyPersister). Here's our analysis as to why it looks like a bug:
> Tracing through the code revealed that a constructor was not found on MyPersister matching the expected arguments. Those arguments are defined on line 34 of PersisterFactory.cs for CollectionPersister types and are Mapping.Collection, ICacheConcurrencyStrategy, and ISessionFactoryImplementor.
> In the CreateCollectionPersister() method (line 68), if there is no persister class defined, it calls the OneToManyPersister implementation of ICollectionPersister with Mapping.Collection, ICacheConcurrencyStrategy, Configuration, and ISessionFactoryImplementor parameters. However, if a custom persister class is defined, it calls the Create() method (line 124) with the Configuration parameter missing, and consequently the Create() method does not invoke a matching constructor with that parameter.
> It seems to us that since the default persister class of OneToManyPersister accepts the 4 argument constructor, and if you specified a custom persister that extends OneToManyPersister, the custom persister should accept the same 4 arguments. In other words, if I specify a custom persister on my class as OneToManyPersister (the same as the default), NHibernate would fail to initialize because it couldn't construct OneToManyPersister.
> Looks related to NH-1957, which appears to have been immediately closed. I've included our diff below that seems to have fixed the issue.
> Diff:
> Index: PersisterFactory.cs
> ===================================================================
> --- PersisterFactory.cs (revision 31412)
> +++ PersisterFactory.cs (revision 31413)
> @@ -31,14 +31,15 @@
>
> // TODO: is it really necessary to provide Configuration to CollectionPersisters ? Should it not be enough with associated class ?
> // or why does ClassPersister's not get access to configuration ?
> - private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> + private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> {
> typeof(Mapping.Collection),
> typeof(ICacheConcurrencyStrategy),
> + typeof(Configuration),
> typeof(ISessionFactoryImplementor)
> };
>
> - /// <summary>
> + /// <summary>
> /// Creates a built in Entity Persister or a custom Persister.
> /// </summary>
> public static IEntityPersister CreateClassPersister(PersistentClass model, ICacheConcurrencyStrategy cache,
> @@ -78,10 +79,11 @@
> }
> else
> {
> - return Create(persisterClass, model, cache, factory);
> + return (ICollectionPersister) Create(persisterClass, model, cache, cfg, factory);
> }
> }
>
> +
> /// <summary>
> /// Creates a specific Persister - could be a built in or custom persister.
> /// </summary>
> @@ -122,7 +124,7 @@
> }
>
> public static ICollectionPersister Create(System.Type persisterClass, Mapping.Collection model,
> - ICacheConcurrencyStrategy cache, ISessionFactoryImplementor factory)
> + ICacheConcurrencyStrategy cache, Configuration cfg, ISessionFactoryImplementor factory)
> {
> ConstructorInfo pc;
> try
> @@ -136,8 +138,8 @@
>
> try
> {
> - return (ICollectionPersister) pc.Invoke(new object[] {model, cache, factory});
> - }
> + return (ICollectionPersister)pc.Invoke(new object[] { model, cache, cfg, factory });
> + }
> catch (TargetInvocationException tie)
> {
> Exception e = tie.InnerException;
> @@ -155,5 +157,6 @@
> throw new MappingException("Could not instantiate collection persister " + persisterClass.Name, e);
> }
> }
> +
> }
> }
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-17 18:59:45
|
[ http://216.121.112.228/browse/NH-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo updated NH-2568:
----------------------------
Priority: Minor (was: Major)
Issue Type: Improvement (was: Bug)
Summary: Create Custom Persister for Collection Type inherited from OneToManyPersister (was: Cannot Create Custom Persister for Collection Type)
> Create Custom Persister for Collection Type inherited from OneToManyPersister
> -----------------------------------------------------------------------------
>
> Key: NH-2568
> URL: http://216.121.112.228/browse/NH-2568
> Project: NHibernate
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.0.0.GA
> Reporter: Jeff Greenland
> Priority: Minor
>
> Encountered issue where setting a Persister Type on a collection property (specifically a type of List) would throw a NullPointerException when NHibernate initialized. Our persister, called MyPersister as a test, extended OneToManyPersister and only had a constructor defined which matched the constructor in the base class (OneToManyPersister). Here's our analysis as to why it looks like a bug:
> Tracing through the code revealed that a constructor was not found on MyPersister matching the expected arguments. Those arguments are defined on line 34 of PersisterFactory.cs for CollectionPersister types and are Mapping.Collection, ICacheConcurrencyStrategy, and ISessionFactoryImplementor.
> In the CreateCollectionPersister() method (line 68), if there is no persister class defined, it calls the OneToManyPersister implementation of ICollectionPersister with Mapping.Collection, ICacheConcurrencyStrategy, Configuration, and ISessionFactoryImplementor parameters. However, if a custom persister class is defined, it calls the Create() method (line 124) with the Configuration parameter missing, and consequently the Create() method does not invoke a matching constructor with that parameter.
> It seems to us that since the default persister class of OneToManyPersister accepts the 4 argument constructor, and if you specified a custom persister that extends OneToManyPersister, the custom persister should accept the same 4 arguments. In other words, if I specify a custom persister on my class as OneToManyPersister (the same as the default), NHibernate would fail to initialize because it couldn't construct OneToManyPersister.
> Looks related to NH-1957, which appears to have been immediately closed. I've included our diff below that seems to have fixed the issue.
> Diff:
> Index: PersisterFactory.cs
> ===================================================================
> --- PersisterFactory.cs (revision 31412)
> +++ PersisterFactory.cs (revision 31413)
> @@ -31,14 +31,15 @@
>
> // TODO: is it really necessary to provide Configuration to CollectionPersisters ? Should it not be enough with associated class ?
> // or why does ClassPersister's not get access to configuration ?
> - private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> + private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> {
> typeof(Mapping.Collection),
> typeof(ICacheConcurrencyStrategy),
> + typeof(Configuration),
> typeof(ISessionFactoryImplementor)
> };
>
> - /// <summary>
> + /// <summary>
> /// Creates a built in Entity Persister or a custom Persister.
> /// </summary>
> public static IEntityPersister CreateClassPersister(PersistentClass model, ICacheConcurrencyStrategy cache,
> @@ -78,10 +79,11 @@
> }
> else
> {
> - return Create(persisterClass, model, cache, factory);
> + return (ICollectionPersister) Create(persisterClass, model, cache, cfg, factory);
> }
> }
>
> +
> /// <summary>
> /// Creates a specific Persister - could be a built in or custom persister.
> /// </summary>
> @@ -122,7 +124,7 @@
> }
>
> public static ICollectionPersister Create(System.Type persisterClass, Mapping.Collection model,
> - ICacheConcurrencyStrategy cache, ISessionFactoryImplementor factory)
> + ICacheConcurrencyStrategy cache, Configuration cfg, ISessionFactoryImplementor factory)
> {
> ConstructorInfo pc;
> try
> @@ -136,8 +138,8 @@
>
> try
> {
> - return (ICollectionPersister) pc.Invoke(new object[] {model, cache, factory});
> - }
> + return (ICollectionPersister)pc.Invoke(new object[] { model, cache, cfg, factory });
> + }
> catch (TargetInvocationException tie)
> {
> Exception e = tie.InnerException;
> @@ -155,5 +157,6 @@
> throw new MappingException("Could not instantiate collection persister " + persisterClass.Name, e);
> }
> }
> +
> }
> }
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-17 21:22:47
|
[ http://216.121.112.228/browse/NH-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo resolved NH-2568.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.2.0Beta1
Thanks Jeff to put all this effort in this issue which was so important (blocker) for your own commercial project.
We really appreciate the attitude and overall the clear test you provides.
P.S. Today I took a chamomile.
> Create Custom Persister for Collection Type inherited from OneToManyPersister
> -----------------------------------------------------------------------------
>
> Key: NH-2568
> URL: http://216.121.112.228/browse/NH-2568
> Project: NHibernate
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.0.0.GA
> Reporter: Jeff Greenland
> Priority: Minor
> Fix For: 3.2.0Beta1
>
>
> Encountered issue where setting a Persister Type on a collection property (specifically a type of List) would throw a NullPointerException when NHibernate initialized. Our persister, called MyPersister as a test, extended OneToManyPersister and only had a constructor defined which matched the constructor in the base class (OneToManyPersister). Here's our analysis as to why it looks like a bug:
> Tracing through the code revealed that a constructor was not found on MyPersister matching the expected arguments. Those arguments are defined on line 34 of PersisterFactory.cs for CollectionPersister types and are Mapping.Collection, ICacheConcurrencyStrategy, and ISessionFactoryImplementor.
> In the CreateCollectionPersister() method (line 68), if there is no persister class defined, it calls the OneToManyPersister implementation of ICollectionPersister with Mapping.Collection, ICacheConcurrencyStrategy, Configuration, and ISessionFactoryImplementor parameters. However, if a custom persister class is defined, it calls the Create() method (line 124) with the Configuration parameter missing, and consequently the Create() method does not invoke a matching constructor with that parameter.
> It seems to us that since the default persister class of OneToManyPersister accepts the 4 argument constructor, and if you specified a custom persister that extends OneToManyPersister, the custom persister should accept the same 4 arguments. In other words, if I specify a custom persister on my class as OneToManyPersister (the same as the default), NHibernate would fail to initialize because it couldn't construct OneToManyPersister.
> Looks related to NH-1957, which appears to have been immediately closed. I've included our diff below that seems to have fixed the issue.
> Diff:
> Index: PersisterFactory.cs
> ===================================================================
> --- PersisterFactory.cs (revision 31412)
> +++ PersisterFactory.cs (revision 31413)
> @@ -31,14 +31,15 @@
>
> // TODO: is it really necessary to provide Configuration to CollectionPersisters ? Should it not be enough with associated class ?
> // or why does ClassPersister's not get access to configuration ?
> - private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> + private static readonly System.Type[] CollectionPersisterConstructorArgs = new System.Type[]
> {
> typeof(Mapping.Collection),
> typeof(ICacheConcurrencyStrategy),
> + typeof(Configuration),
> typeof(ISessionFactoryImplementor)
> };
>
> - /// <summary>
> + /// <summary>
> /// Creates a built in Entity Persister or a custom Persister.
> /// </summary>
> public static IEntityPersister CreateClassPersister(PersistentClass model, ICacheConcurrencyStrategy cache,
> @@ -78,10 +79,11 @@
> }
> else
> {
> - return Create(persisterClass, model, cache, factory);
> + return (ICollectionPersister) Create(persisterClass, model, cache, cfg, factory);
> }
> }
>
> +
> /// <summary>
> /// Creates a specific Persister - could be a built in or custom persister.
> /// </summary>
> @@ -122,7 +124,7 @@
> }
>
> public static ICollectionPersister Create(System.Type persisterClass, Mapping.Collection model,
> - ICacheConcurrencyStrategy cache, ISessionFactoryImplementor factory)
> + ICacheConcurrencyStrategy cache, Configuration cfg, ISessionFactoryImplementor factory)
> {
> ConstructorInfo pc;
> try
> @@ -136,8 +138,8 @@
>
> try
> {
> - return (ICollectionPersister) pc.Invoke(new object[] {model, cache, factory});
> - }
> + return (ICollectionPersister)pc.Invoke(new object[] { model, cache, cfg, factory });
> + }
> catch (TargetInvocationException tie)
> {
> Exception e = tie.InnerException;
> @@ -155,5 +157,6 @@
> throw new MappingException("Could not instantiate collection persister " + persisterClass.Name, e);
> }
> }
> +
> }
> }
--
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
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X