December 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6537) Implement IdentifierSource for @javax.persistence.MapsId

by Hardy Ferentschik (JIRA)

Implement IdentifierSource for @javax.persistence.MapsId -------------------------------------------------------- Key: HHH-6537 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6537 Project: Hibernate Core Issue Type: Sub-task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6534) Utilize new FetchTiming and FetchStyle enums

by Steve Ebersole (JIRA)

Utilize new FetchTiming and FetchStyle enums -------------------------------------------- Key: HHH-6534 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6534 Project: Hibernate Core Issue Type: Bug Components: core, metamodel Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.next -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-6539) Validate that inheritance hierarchy is not circular

by Gail Badner (JIRA)

Validate that inheritance hierarchy is not circular --------------------------------------------------- Key: HHH-6539 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6539 Project: Hibernate Core Issue Type: Task Components: metamodel Reporter: Gail Badner Fix For: 4.0.0.next -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6538) Extract CollectionElement interface from AbstractCollectionElement

by Gail Badner (JIRA)

Extract CollectionElement interface from AbstractCollectionElement ------------------------------------------------------------------ Key: HHH-6538 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6538 Project: Hibernate Core Issue Type: Task Components: metamodel Reporter: Gail Badner Assignee: Gail Badner Fix For: 4.0.0.next -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6559) Add support for providing SQL functions as service

by Gail Badner (JIRA)

Add support for providing SQL functions as service -------------------------------------------------- Key: HHH-6559 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6559 Project: Hibernate Core Issue Type: Task Components: core Reporter: Gail Badner Fix For: 4.0.0.next Should this be provided by JdbcServices? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6652) Add ability for Integrator to prepare MetadataImplementor as part of lifecycle

by Steve Ebersole (JIRA)

Add ability for Integrator to prepare MetadataImplementor as part of lifecycle ------------------------------------------------------------------------------ Key: HHH-6652 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6652 Project: Hibernate Core Issue Type: Improvement Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.1.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6692) An Integrator cannot set NamingStrategy in the new Metamodel API (it's possible in Configuration)

by Emmanuel Bernard (JIRA)

An Integrator cannot set NamingStrategy in the new Metamodel API (it's possible in Configuration) ------------------------------------------------------------------------------------------------- Key: HHH-6692 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6692 Project: Hibernate Core Issue Type: Improvement Components: metamodel Affects Versions: 4.1.0 Reporter: Emmanuel Bernard {code} public class MyIntegrator implements Integrator, ServiceContributingIntegrator { @Override public void integrate(Configuration configuration, SessionFactoryImplementor sessionFactory, SessionFactoryServiceRegistry serviceRegistry) { configuration.setNamingStrategy( MyNamingStrategy.INSTANCE ); } @Override public void integrate(MetadataImplementor metadata, SessionFactoryImplementor sessionFactory, SessionFactoryServiceRegistry serviceRegistry) { //FIXME how to do it here? } } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6901) Avoid generating javadoc for test classes

by Sanne Grinovero (JIRA)

Avoid generating javadoc for test classes ----------------------------------------- Key: HHH-6901 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6901 Project: Hibernate Core Issue Type: Task Components: build Affects Versions: 4.0.0.Final Reporter: Sanne Grinovero Priority: Minor Fix For: 4.0.1, 4.1.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3348) loading context

by benjamin Leroux (JIRA)

loading context --------------- Key: HHH-3348 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3348 Project: Hibernate3 Issue Type: New Feature Affects Versions: 4.x Reporter: benjamin Leroux Priority: Minor this proposal is for creating a loading context into hibernate Let me explain: On an application, we often hesitating between the two major strategies of loading (eager or lazy). But for some reason there has no good choice. In fact, it depends on the context. So we do lazy loading and redefine some method with new request with some "join". In fact, it lead to complexity and decrease managability of the application. So my idea is to allow the definition of a context (like transactional context) where we we can put the loading strategie to adopt. with annotation it could be very easy to define such context. Let see this exemple : Avec les annotations, cela pourrait conduire à une ecriture de ce style : @LoadingStrategie (type=eager from="Car" get={"driver"}) public List<Car> getAllCarForDriving(){ // Some fonctions } @LoadingStrategie (type=eager from="Car" get={"driver","passengers"}) public List<Car> getAllCarForTravelling(){ // Some fonctions } In the method getAllCarForDriving when we call a hql request on car it automaticaly get driver but in the method getAllCarForTravelling passengers and the driver is loaded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6228) Build is platform dependent

by Stevo Slavic (JIRA)

Build is platform dependent --------------------------- Key: HHH-6228 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6228 Project: Hibernate Core Issue Type: Patch Components: build Affects Versions: 4.x Environment: Windows 7 x64 Reporter: Stevo Slavic Priority: Trivial Attachments: Fixes+build%2C+compile+tasks+used+platform+encoding+making+build+platform+depend.patch Build tasks generateMainLoggingClasses and compileJava were failing because default platform encoding was used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2011