October 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Closed: (HBX-597) New Hibernate Configuration wizard is missing the Classpath list

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-597?page=all ] Max Rydahl Andersen closed HBX-597: ----------------------------------- Resolution: Fixed rearranged so the (now optional) mappings and classpath is on seperate tabs. > New Hibernate Configuration wizard is missing the Classpath list > ---------------------------------------------------------------- > > Key: HBX-597 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-597 > Project: Hibernate Tools > Type: Improvement > Reporter: Christian Bauer > Priority: Critical > Fix For: 3.2beta9 > > > The "New Hibernate Configuration" wizard that opens up when I click "Create Console Configuration" in the "New Hibernate XML Configuration file" wizard does not have the "Classpath" list. The created Hibernate Console configuration is therefore unusable. You have to actually Edit it again in the Console perspective and add the POJO classpath. This additional Edit step has to be avoided, either the created console configuration works or the wizard is useless. -- 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

19 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (ANN-28) @Any

by Alexander Portnov (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-28?page=all ] Alexander Portnov updated ANN-28: --------------------------------- Attachment: annotations-any-patch.txt Implementation of @Any and @ManyToAny annotations. Following are syntax examples: @Any(idType="integer", metaType="string", metaValues={ @MetaValue(value="S",targetEntity=StringProperty.class), @MetaValue(value="I",targetEntity=IntegerProperty.class)}, columns = { @Column(name="property_type"), @Column(name="property_id")}, cascade= CascadeType.ALL) public Property getSomeProperty() { return someProperty; } @ManyToAny(idType="integer", metaType="string", metaValues={ @MetaValue(value="S", targetEntity=StringProperty.class), @MetaValue(value="I", targetEntity=IntegerProperty.class)}, columns = { @Column(name="property_type"), @Column(name="property_id")}) @Cascade({org.hibernate.annotations.CascadeType.ALL}) @JoinTable(name="obj_properties", joinColumns = {@JoinColumn(name="obj_id")}) public List<Property> getGeneralProperties() { return generalProperties; } @ManyToAny(idType="integer", metaType="string", metaValues={ @MetaValue(value="S", targetEntity=StringProperty.class), @MetaValue(value="I", targetEntity=IntegerProperty.class)}, columns = { @Column(name="property_type"), @Column(name="property_id")}) @Cascade({org.hibernate.annotations.CascadeType.ALL}) @JoinTable(name="map_properties", joinColumns = {@JoinColumn(name="map_id")}) @MapKey(columns = {@Column(name="map_key")}) public Map<String, Property> getProperties() { return properties; } > @Any > ---- > > Key: ANN-28 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-28 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Versions: 3.1beta3 > Reporter: Emmanuel Bernard > Priority: Trivial > Attachments: annotations-any-patch.txt > > > @AnyValue(value="", class="") //or MetaValue? > @Any(idType="", metaType="", metaValues={@MetaValue()}, columns={@Column()}) -- 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

19 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1740) Build-time instrumentation breaks lazy="proxy"

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=c... ] Max Rydahl Andersen commented on HHH-1740: ------------------------------------------ there is no relase of 3.1.x planned. > Build-time instrumentation breaks lazy="proxy" > ---------------------------------------------- > > Key: HHH-1740 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2 > Reporter: Frank Grimes > Assignee: Steve Ebersole > Priority: Critical > Fix For: 3.2.0.cr4 > Attachments: 312Document.class, Document.class, HHH-1740.diff, Hibernate3-Branch_3_2.diff, TestLazyManyToOne-Branch_3_2.diff > > > I have a mapping that contains a many-to-one lazy="proxy". > This alone works fine: I see $$EnhancerByCGLIB$$ as the type when I do a load > Once I add a lazy property to the mapping and do build-time cglib enhancement, it breaks. > Not only is the lazy property listed in $CGLIB_READ_WRITE_CALLBACK, but also my lazy="proxy" association. (i.e. no more proxy object) > This works fine in hibernate-3.1.2. > This was originally brought up here: http://forums.hibernate.org/viewtopic.php?t=958881 > Please let me know if more info or a test case is needed. -- 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

19 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1740) Build-time instrumentation breaks lazy="proxy"

by Oleg Byelkin (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=c... ] Oleg Byelkin commented on HHH-1740: ----------------------------------- I have a question to Hibernate team: Any plans fix that issue in version 3.1? It will be nice for our project (we are satisfied with 3.1 functionality and don't want urgently migrate to 3.2). > Build-time instrumentation breaks lazy="proxy" > ---------------------------------------------- > > Key: HHH-1740 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2 > Reporter: Frank Grimes > Assignee: Steve Ebersole > Priority: Critical > Fix For: 3.2.0.cr4 > Attachments: 312Document.class, Document.class, HHH-1740.diff, Hibernate3-Branch_3_2.diff, TestLazyManyToOne-Branch_3_2.diff > > > I have a mapping that contains a many-to-one lazy="proxy". > This alone works fine: I see $$EnhancerByCGLIB$$ as the type when I do a load > Once I add a lazy property to the mapping and do build-time cglib enhancement, it breaks. > Not only is the lazy property listed in $CGLIB_READ_WRITE_CALLBACK, but also my lazy="proxy" association. (i.e. no more proxy object) > This works fine in hibernate-3.1.2. > This was originally brought up here: http://forums.hibernate.org/viewtopic.php?t=958881 > Please let me know if more info or a test case is needed. -- 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

19 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1409) Packaging of Hibernate binaries

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1409?page=c... ] Max Rydahl Andersen commented on HHH-1409: ------------------------------------------ fyi build.xml already contains the jar task for building the same hibernate-client.jar...but not finalized yet (so just for testing) .....feel free to give feedback on it. > Packaging of Hibernate binaries > ------------------------------- > > Key: HHH-1409 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1409 > Project: Hibernate3 > Type: Improvement > Components: build > Reporter: Markus Jessenitschnig > Priority: Minor > > > We are using Hibernate in a typical client/server environment. Up to now we need to have the hibernate.jar file on the classpath of both JVMs because on the client side, Hibernate Exception classes as well as Collection classes needs to be found at runtime. Well, it would be possible to take care, that all exceptions are converted into application exceptions (no hibernate exceptions set as cause) and all collections are copied into collections of type java.util.Collection. Obviously this will remove the need of a hibernate.jar file on the client side, but the advantages of e.g. persistent collections are lost. > To keep the size of the client side distribution small, it would be nice to have only classes on the client side classpath which are really needed (I'm not sure if exception and collection classes are enough). For that reason I would suggest to split the hibernate3.jar of the distribution into two parts. A hibernate-common.jar which contains classes needed on the client and the server side of the application, and a hibernate-server.jar which only contains classes needed on the server side of the application. > kind regards > Markus Jessenitschnig -- 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

19 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HB-864) Provide separate hibernate2-collection.jar

by Oliver Siegmar (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HB-864?page=com... ] Oliver Siegmar commented on HB-864: ----------------------------------- HHH-1409 is about the same topic, but for Hibernate3. > Provide separate hibernate2-collection.jar > ------------------------------------------ > > Key: HB-864 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-864 > Project: Hibernate2 > Type: Improvement > Components: core > Versions: 2.1.2 > Reporter: Juergen Hoeller > > > It would be good to provide a separate hibernate2-collection.jar which just contains the minimal set of classes that's required to handle Hibernate's collection implementations. The typical usage would be remote clients that receive serialized persistent objects via RMI: They need to know about Hibernate's collection classes but do not have any other Hibernate dependencies. > Juergen -- 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

19 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2168) SQLQuery - use rowIndex for scalar queries

by Luiz dos Santos Faias Junior (JIRA)

SQLQuery - use rowIndex for scalar queries ------------------------------------------ Key: HHH-2168 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2168 Project: Hibernate3 Type: Improvement Components: query-sql Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga Oracle 10g Database Reporter: Luiz dos Santos Faias Junior Priority: Minor When org.hibernate.SQLQuery is used the default column types are java.sql.Date and java.math.BigDecimal. If I need to specify the types I use addScalar for all columns, but if I'm making a report probably there will be a few columns I want the default type. So my suggestion is to create a method : addScalar(java.lang.String columnAlias, org.hibernate.type.Type type, int columnIndex); or addScalar(int columnIndex, org.hibernate.type.Type type); Example : SQLQuery query = session.createSQLQuery( " select user_id, user_name, last_login from users " ); where last_login should be a java.sql.Timestamp. I want the first and second columns to use the default type ( int and String ), and the third column I want to specify Timestamp instead of java.sql.Date So I could only write : query.addScalar("last_login", Hibernate,.TIMESTAMP, 2); or addScalar(2, Hibernate.TIMESTAMP); (using the columnIndex). thanks, Luiz Faias São Paulo - Brasil -- 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

19 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-471) lazily resolve default messages in DefaultMessageInterpolator

by Emmanuel Bernard (JIRA)

lazily resolve default messages in DefaultMessageInterpolator ------------------------------------------------------------- Key: ANN-471 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-471 Project: Hibernate Annotations Type: Bug Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: 3.2.1 There is no need to resolved the message during classValidator.apply() -- 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

19 years, 5 months

1
2
0 / 0

[Hibernate-JIRA] Created: (ANN-458) Hibernate Validator initialization always requires keys in ValidatorMessges.properties

by Christian Bauer (JIRA)

Hibernate Validator initialization always requires keys in ValidatorMessges.properties -------------------------------------------------------------------------------------- Key: ANN-458 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-458 Project: Hibernate Annotations Type: Bug Components: binder Reporter: Christian Bauer Priority: Critical Seam + Hibernate Validator doesn't work. When AnnotationConfiguration boots, it always uses the DefaultMessageInterpolator (this is actually a separate problem, not only the event listeners should use the configured interpolator) and the default interpolator always throws an exception if the message key can't be found. This is an even bigger problem if you don't want or have a ValidatorMessages.properties file, like in a typical Seam application where everything is in messages.properties (Seam managed component). You can't override or set the resource bundle that is used on startup. A quick fix would be to not throw an exception in DefaultMessageInterpolator if the key can't be found in the resource bundle. The key should then be returned as the message. I see no reason why that shouldn't work, it's the users own fault if he forgot the key. It's also the regular behavior in JSF. This is my quick hack to make it work, in DefaultMessageInterpolator: String string = null; try { string = messageBundle != null ? messageBundle.getString( token ) : null; } catch( MissingResourceException e ) { //give a second chance with the default resource bundle } if (string == null) { try { string = defaultMessageBundle.getString( token ); } catch( MissingResourceException e) { return message; /* We don't want that: throw new MissingResourceException( "Can't find resource in validator bundles, key " + token, defaultMessageBundle.getClass().getName(), token ); */ } } I'm writing now about this in the JPwH book, so I expect that I can in the future simply have messages.properties for Seam with my Hibernate Validator messages. This fix has to be in 3.2.1. -- 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

19 years, 5 months

2
9
0 / 0

[Hibernate-JIRA] Created: (HBX-782) extends org.hibernate.tool.ant.HibernateToolTask

by jacky hua (JIRA)

extends org.hibernate.tool.ant.HibernateToolTask ------------------------------------------------ Key: HBX-782 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-782 Project: Hibernate Tools Type: Improvement Versions: 3.2beta8 Reporter: jacky hua I wanted to extends HibernateToolTask class to add some customerized ant tasks, but this class has some private property like "generator", so I think these properties should be changed to protected. -- 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

19 years, 5 months

2
3
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 October 2006