The one in Configuration is the one used in the current code paths.
However the one in MetadataImpl will be used from 4.1 onward.
So both is best. It really should be trivial to change in both once
the actual thing to change to is in place.
On Tue 06 Sep 2011 12:19:09 PM CDT, Emmanuel Bernard wrote:
Damn so it looks like int he current codebase,
identifierGeneratorFactory is held both in MetadataImpl and Configuration. Do you know
which one is currently used in the codebase?
Should I make sure to update both?
On 6 sept. 2011, at 13:31, Emmanuel Bernard wrote:
> Hi all,
> I have the need to implement
https://hibernate.onjira.com/browse/HHH-6091 (Let people
customize identifier generator strategy mappings programmatically in Hibernate 4)
>
> and I am wondering why IdentifierGeneratorFactory is not a service and if it would
make sense for me to implement it as a service. The aternatives would be:
> - some hardcoded property based class like in 3.6
> - some service dedicated to overriding default id generators that would be called by
DefaultIdentifierGeneratorFactory
>
> Any preference?
>
> I also need to implement [
HHH-6091](https://hibernate.onjira.com/browse/HHH-6091) Let
people customize identifier generator strategy mappings programmatically in Hibernate 4
> for which I am considering using the service approach as well.
>
> Let me know if I'm on track
>
> Emmanuel
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev