December 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-797) using @LOB annotation

by Patrick Walter (JIRA)

using @LOB annotation --------------------- Key: ANN-797 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-797 Project: Hibernate Annotations Issue Type: Bug Reporter: Patrick Walter When I use the @LOB annotation it always creates only VARCHAR(255) for stringData and Binary (255) for binaryData defined below. @Lob @Basic(fetch=FetchType.LAZY) private byte[] binaryData; @Lob @Basic(fetch=FetchType.LAZY) private String stringData; Any help in resolving this would be VERRY!!! appreciated. THANKS -- 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

16 years, 3 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4735) Proxy can be associated with a new session when it is already connected to a different one

by Gail Badner (JIRA)

Proxy can be associated with a new session when it is already connected to a different one ------------------------------------------------------------------------------------------ Key: HHH-4735 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4735 Project: Hibernate Core Issue Type: Bug Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.3.x, 3.5 A proxy can be associated with a new session when it is already connected to a different one. This happens because AbstractLazyInitializer.isConnectedToSession() has a bug that causes it to always return false. -- 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

16 years, 3 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3555) Extend the query system with the ability to traverse associations

by Adam Warski (JIRA)

Extend the query system with the ability to traverse associations ----------------------------------------------------------------- Key: HHH-3555 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3555 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski Assignee: Adam Warski -- 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

16 years, 3 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4733) Allow to override collection behavior in components

by Alex Besogonov (JIRA)

Allow to override collection behavior in components --------------------------------------------------- Key: HHH-4733 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4733 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.2 Reporter: Alex Besogonov Priority: Minor Attachments: comp_prop.diff By default, Hibernate treats _all_ collections inside a <component> as always not-null. The attached patch allows to override this behavior on a component level. By setting 'ignoreCollections' meta attribute to 'true' all collections are ignored during component hydration, so if no other not-null properties are present, the whole component is skipped. -- 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

16 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2413) Offer a way to log bound jdbc parameters in a uniform way for UserType implementors

by Baptiste MATHUS (JIRA)

Offer a way to log bound jdbc parameters in a uniform way for UserType implementors ----------------------------------------------------------------------------------- Key: HHH-2413 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2413 Project: Hibernate3 Type: Improvement Versions: 3.2.2 Reporter: Baptiste MATHUS Priority: Minor At the moment, when someone implements a UserType, the bound parameters won't be displayed in not explicitly displayed via loggers. For example, here is what the code of NullableType.nullSafeGet() is : public final void nullSafeSet(PreparedStatement st, Object value, int index) throws HibernateException, SQLException { try { if ( value == null ) { if ( IS_TRACE_ENABLED ) { log().trace( "binding null to parameter: " + index ); } st.setNull( index, sqlType() ); } else { if ( IS_TRACE_ENABLED ) { log().trace( "binding '" + toString( value ) + "' to parameter: " + index ); } set( st, value, index ); } } catch ( RuntimeException re ) { log().info( "could not bind value '" + toString( value ) + "' to parameter: " + index + "; " + re.getMessage() ); throw re; } catch ( SQLException se ) { log().info( "could not bind value '" + toString( value ) + "' to parameter: " + index + "; " + se.getMessage() ); throw se; } } IMO, it would be quite a good thing to provide some method in Hibernate, something like logBoundParameter() that would do the log like above : > log().trace( "binding '" + toString( value ) + "' to parameter: " + index ); This method could then be just called by implementors so as to guaranty the display is always the same about bound parameters. Even more, I think it should use a special logger, just like the org.hibernate.SQL one to display this parameters. In fact, at the moment, I feel the reference documentation is not very clear about this : see http://www.hibernate.org/hib_docs/v3/reference/en/html/session-configurat.... It says : > org.hibernate.type Log all JDBC parameters But that's not completely true: it will only log bound parameters that are parameters typed with standard types coming from the org.hibernate.type package. Any custom UserType won't display anything until you: 1) put the right log4j line for the package where your userType is located ; 2) think about explicitly logging those parameter values in your custom UserType (cf. my first point). I'm not sure I made myself totally clear,. If so, please let me know. If you think that would be worth an improvement, I'll give a look to provide a patch for this. Thanks a lot. -- 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

16 years, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4730) Entries not deleted from join table when an entity is deleted

by Adam Warski (JIRA)

Entries not deleted from join table when an entity is deleted ------------------------------------------------------------- Key: HHH-4730 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4730 Project: Hibernate Core Issue Type: Bug Components: envers Reporter: Adam Warski Assignee: Adam Warski Priority: Minor In a many-to-many unidirectional (A->B) relation, if the B entity is deleted, without removing it from the collection in A, then the entry in the join table isn't removed. This only causes a desynchronization between "norma" and audit tables if there's a foreign key with a on delete cascade in the join table. -- 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

16 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4720) AttributeFactory uses Type.getReturnedClass() for the attribute's javatype

by Steve Ebersole (JIRA)

AttributeFactory uses Type.getReturnedClass() for the attribute's javatype -------------------------------------------------------------------------- Key: HHH-4720 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4720 Project: Hibernate Core Issue Type: Bug Components: entity-manager, metamodel Affects Versions: 3.5.0-Beta-2 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5 o.h.ejb.metamodel.AttributeFactory is currently using Type.getReturnedClass() from the o.h.type.Type associated with the attibute as it's javaType. That is not accurate in all cases, especially in subclassing scenarios like java.util.Date and the java.sql variants. We should instead look at the Member for the attribute to determine the java type (perhaps applying some validation of the "assignability"). -- 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

16 years, 3 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4728) Envers test suite failing with OutOfMemoryError

by Hardy Ferentschik (JIRA)

Envers test suite failing with OutOfMemoryError ----------------------------------------------- Key: HHH-4728 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4728 Project: Hibernate Core Issue Type: Bug Components: envers Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik It does not occur on all systems, but the idea is to increase the heap size for the surefire plugin. However, this cannot be done via the MAVEN_OPTS variable, since the default fork mode for the surefire plugin is {{once}}, meaning a new JVM is getting started for the tests. The JVM arguments have to be passed via the surefire configuration. -- 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

16 years, 3 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HBX-1110) Support for abstract/concrete pairs of POJO generation for hbm2java

by Jeff Walker (JIRA)

Support for abstract/concrete pairs of POJO generation for hbm2java ------------------------------------------------------------------- Key: HBX-1110 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1110 Project: Hibernate Tools Issue Type: Patch Components: ant, hbm2java, reverse-engineer Affects Versions: 3.2.4 Beta1 Environment: Hibernate 3.3.1GA, DB2 8.2, ant 1.6.5, Java 5.0 b11, eclipse (myEclipse blue 7.0) on windows xp sp3 Reporter: Jeff Walker Priority: Minor Attachments: HibernateExt.patch I wanted hbm2java to be able to produce pairs of both abstract base classes and concrete classes for each POJO when reverse engineering. I altered the ant tasks to allow this syntax: <hbm2java ejb3="true" jdk5="true"> <base transform="{package-name}/base/{class-name}Base"/> <concrete transform="{package-name}/{class-name}"/> </hbm2java> I then extended the POJO exporter (used only when base or concrete are present). This new exporter takes the meta model and runs once for all components, and then twice for each entity. The first entity run is for the base classes. Using the meta property overrides in the exporter, I force the class to be abstract, and change the generated class name according to the "transform" attribute. I also save the name of the generated class name in a hash, mapped to the original name for use in the second phase. Then for the second run (still inside of the exporter), I force the generated class name (again via the "transform" attribute), and have the class extend the base class that was generated in the first phase. I also introduce two new variables into the template context: basePartOfPair and concretePartOfPair. Set to true or false for the respective phase. They default to false for when the regular exporter is used. In the templates I forced the properties to be protected (instead of private), and turned off the property generation for the concrete class. I have code in the method (exportPersistentClass) to override these at meta properties, but that didn't work, as those properties need to be set on the property level, not the class level. You may refer to the following forum post for more background: http://forum.hibernate.org/viewtopic.php?t=994243 Note that there is no test case for this functionality yet. I'm not sure where to put it or what to do with that, but I will keep looking at that. -- 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

16 years, 3 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-411) Get a feature complete mapping (Amin Mohammed-Coleman)

by Emmanuel Bernard (JIRA)

Get a feature complete mapping (Amin Mohammed-Coleman) ------------------------------------------------------ Key: HSEARCH-411 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-411 Project: Hibernate Search Issue Type: Sub-task Components: mapping Reporter: Emmanuel Bernard Fix For: 3.2.0.Beta3 -- 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

16 years, 3 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2009