March 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-32) Download Lucene 2.1.0

by Emmanuel Bernard (JIRA)

Download Lucene 2.1.0 --------------------- Key: HSEARCH-32 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-32 Project: Hibernate Search Type: Sub-task Components: engine Reporter: Emmanuel Bernard Fix For: FIRST -- 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

18 years, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-27) Ability to index associated / embedded objects

by Emmanuel Bernard (JIRA)

Ability to index associated / embedded objects ---------------------------------------------- Key: HSEARCH-27 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-27 Project: Hibernate Search Type: New Feature Components: mapping, engine Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: FIRST @indexedEmbedded(prefix, depth) Note that the field are embedded into the root entity index. @*ToOne associations as well as @Embedded relation can be annotated as @indexedEmbedded -- 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

18 years, 6 months

1
2
0 / 0

[Hibernate-JIRA] Created: (ANN-583) generator class with <composite-id>

by sai sirisha (JIRA)

generator class with <composite-id> ----------------------------------- Key: ANN-583 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-583 Project: Hibernate Annotations Type: New Feature Versions: 3.1beta9 Environment: Version 3.1, database is oracle Reporter: sai sirisha Priority: Critical Attachments: DsEpsdDietProfileHdr.hbm.xml We have a requirement in our project that along with composite keys we have to put one attribute as autoincrement or sequence.How can we do this. e.g <class name="xyz"> <composite-id name="id" class="com.iba.ehis.dobj.DsEpsdDietProfileHdrId" > <key-many-to-one name="prEncounter" class="com.iba.ehis.dobj.PrEncounter"> <column name="OPERATING_FACILITY_ID" length="6" /> <column name="ENCOUNTER_ID" precision="12" scale="0" /> </key-many-to-one> <key-property name="profileSl" type="java.lang.Long"> <column name="PROFILE_SL" precision="2" scale="0" /> </key-property> </composite-id> </class> In the above code i want key-property "profileSl" as autoincriment field.How can i achive this. -- 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

18 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2491) criteria failing with custom user type

by Luca Dall'Olio (JIRA)

criteria failing with custom user type -------------------------------------- Key: HHH-2491 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2491 Project: Hibernate3 Type: Bug Environment: hibernate 3.2.2-GA hsqldb 8.0.1 Reporter: Luca Dall'Olio When executing a criteria query with a custom <id> type, hibernate ignores the custom type trying to set a primitive type instead; whereas load() works succesfully : Below is some code that helps reproducing this problem : Example of a custom Identifier Generator : package sample; ... public class CustomIdentifierGenerator implements IdentifierGenerator, PostInsertIdentifierGenerator, Configurable { private static IdentityGenerator hibernateGeneratorDelegate = null; public void configure(Type type, Properties props, Dialect dialect) throws MappingException { hibernateGeneratorDelegate = IdentifierGeneratorFactory.create( "sequence", new LongType(), props, dialect); if (hibernateGeneratorDelegate instanceof Configurable) { ((Configurable) hibernateGeneratorDelegate).configure( new LongType(), props, dialect); } } public Serializable generate(SessionImplementor session, Object object) throws HibernateException { return hibernateGeneratorDelegate.generate(session, object); } public InsertGeneratedIdentifierDelegate getInsertGeneratedIdentifierDelegate( PostInsertIdentityPersister persister, Dialect dialect, boolean isUseGet) throws HibernateException { return hibernateGeneratorDelegate.getInsertGeneratedIdentifierDelegate(persister, dialect, isUseGet); } } Mapping snippet : <class name="sample.SimpleEntity" table="TB_SMP_SIMPLE"> <id name="entityPK" type="sample.LongEntityPK" column="SMP_ID"> <generator class="sample.CustomIdentifierGenerator" /> </id> </class> Entity class : package sample; .... public class SimpleEntity { Query code : SimpleEntity de = new SimpleEntity(); s.save(de); // Read SimpleEntity de2 = (SimpleEntity) s.load(SimpleEntity.class, de .getEntityPK()); assertNotNull(de2); assertEquals(de, de2); // Query Criteria crit = s.createCriteria(SimpleEntity.class); List results = crit.list(); // FAILING!!! IllegalArgumentException in class: it.unimaticaspa.unique.pe.spec.entity.EntityBase, setter method of property: entityPK // expected type: it.unimaticaspa.unique.pe.spec.entity.IEntityPK, actual value: java.lang.Long Logs : IllegalArgumentException in class: it.unimaticaspa.unique.pe.spec.entity.EntityBase, setter method of property: entityPK expected type: it.unimaticaspa.unique.pe.spec.entity.IEntityPK, actual value: java.lang.Long Error StackTrace: org.hibernate.PropertyAccessException: IllegalArgumentException occurred while calling setter of it.unimaticaspa.unique.pe.spec.entity.EntityBase.entityPK at org.hibernate.property.BasicPropertyAccessor$BasicSetter.set(BasicPropertyAccessor.java:104) at org.hibernate.tuple.entity.AbstractEntityTuplizer.setIdentifier(AbstractEntityTuplizer.java:211) at org.hibernate.tuple.entity.AbstractEntityTuplizer.instantiate(AbstractEntityTuplizer.java:353) at org.hibernate.persister.entity.AbstractEntityPersister.instantiate(AbstractEntityPersister.java:3600) at org.hibernate.impl.SessionImpl.instantiate(SessionImpl.java:1275) ... at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.lang.IllegalArgumentException: argument type mismatch at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.hibernate.property.BasicPropertyAccessor$BasicSetter.set(BasicPropertyAccessor.java:42) ... 35 more -- 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

18 years, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2034) Potential ClassCastException in catch block in NullableType

by Galen Palmer (JIRA)

Potential ClassCastException in catch block in NullableType ----------------------------------------------------------- Key: HHH-2034 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2034 Project: Hibernate3 Type: Improvement Components: core Versions: 3.1.3 Environment: Hibernate 3.1.3 Reporter: Galen Palmer Priority: Minor It is possible to throw an exception from within the catch block of NullableType.nullSafeSet() since the toString(value) method calls in many cases (e.g. StringType) simply result in a cast of return (String)value. This may mask the underlying problem for the users. A proposed solution would be to replace the call in the catch blog of toString(value) with a reference to value. For example: line 87: log().info( "could not bind value '" + value + "' to parameter: " + index + "; " + re.getMessage() ); and line 91: log().info( "could not bind value '" + value + "' to parameter: " + index + "; " + se.getMessage() ); This change would prevent the catch block from throwing the exception. -- 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

18 years, 6 months

3
5
0 / 0

[Hibernate-JIRA] Commented: (ANN-21) @Past validation annotation generates incorrect DDL for Oracle 8.x

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-21?page=com... ] Diego Pires Plentz commented on ANN-21: --------------------------------------- What about to use sysdate instead of current_date? > @Past validation annotation generates incorrect DDL for Oracle 8.x > ------------------------------------------------------------------ > > Key: ANN-21 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-21 > Project: Hibernate Annotations > Type: Bug > Components: validator > Versions: 3.1beta3 > Environment: Hibernate 3.0.5 > Oracle 8.1.7 (running on Win XP Pro) > Reporter: Aye Thu > Priority: Minor > > > The following validation code: > @Past > public Date getBirthDate() > { > return birthDate; > } > produces the following DDL when using the OracleDialect: > create table Person (party_id number(19,0) not null, birth_date date check (birth_date < current_date), primary key (party_id)) > The "current_date" was introduced only in Oracle 9i and is not available in earlier Oracle versions and the following SQL exception is thrown: > ORA-02438: Column check constraint cannot reference other columns > According to Gavin, the current validation framework is not aware of Dialects. (http://forum.hibernate.org/viewtopic.php?t=943378) -- 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

18 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-571) Missing referencedColumnName in @JoinColumn doesn't cause an error

by Brian Curnow (JIRA)

Missing referencedColumnName in @JoinColumn doesn't cause an error ------------------------------------------------------------------ Key: ANN-571 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-571 Project: Hibernate Annotations Type: Bug Versions: 3.2.1 Environment: Hibernate 3.3.2, Oracle 9.2 (JDBC Thin XA driver version 10.2.0.2.0) Running in WebLogic Server 9.2 MP1 on Solaris 8 and JDK 1.5.0_10 Reporter: Brian Curnow According to the JPA specification (p. 169) if there are multiple @JoinColumn annotations specified within an @JoinColumns annotation then both name and referencedColumnName attributes must be used: "If there is more than one join column, a JoinColumn annotation must be specified for each join column using the JoinColumns annotation. Both the name and the referencedColumnName elements must be specified in each such JoinColumn annotation." Right now, if I leave off the referencedColumnName everything appears to work but I get some random SQL. For instance, say I have two tables TABLE1 and TABLE2 and they are joined on the columns ID and TYPE, sometimes I get the right join condition: TABLE1.ID = TABLE2.ID AND TABLE1.TYPE = TABLE2.TYPE but sometimes I get: TABLE1.ID = TABLE2.TYPE AND TABLE1.TYPE = TABLE2.ID Adding the referencedColumnName makes that issue go away. Since the spec says that those two attributes are required there really should be a runtime check for that which, at the very least, puts a warning in the log. I'd prefer a RuntimeException so you can't accidentally violate the spec. -- 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

18 years, 6 months

2
5
0 / 0

[Hibernate-JIRA] Commented: (HHH-1682) Improve the description of differences between save() and persist()

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1682?page=c... ] Diego Pires Plentz commented on HHH-1682: ----------------------------------------- I found that a lot of people have the same doubt. To help to solve this issue I'm quoting Christian Bauer: "In case anybody finds this thread... persist() is well defined. It makes a transient instance persistent. However, it doesn't guarantee that the identifier value will be assigned to the persistent instance immediately, the assignment might happen at flush time. The spec doesn't say that, which is the problem I have with persist(). persist() also guarantees that it will not execute an INSERT statement if it is called outside of transaction boundaries. This is useful in long-running conversations with an extended Session/persistence context. A method like persist() is required. save() does not guarantee the same, it returns an identifier, and if an INSERT has to be executed to get the identifier (e.g. "identity" generator, not "sequence"), this INSERT happens immediately, no matter if you are inside or outside of a transaction. This is not good in a long-running conversation with an extended Session/persistence context." http://forum.hibernate.org/viewtopic.php?p=2325758&sid=a69cf62ab0451699a6... http://opensource.atlassian.com/projects/hibernate/browse/HHH-1273#action... > Improve the description of differences between save() and persist() > ------------------------------------------------------------------- > > Key: HHH-1682 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1682 > Project: Hibernate3 > Type: Improvement > Components: documentation > Versions: 3.1.2 > Reporter: Stephen M. Wick > Priority: Minor > > > I do not believe that the Hibernate Reference PDF differentiates between the persist() and save() methods well enough for a developer to determine which one to use and where. This information would be extremely useful in section 10.2 "Making objects persistent" where these two methods are described. -- 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

18 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-4) ValidatorMessages_pt_BR.properties

by Juliano Carniel (JIRA)

ValidatorMessages_pt_BR.properties ---------------------------------- Key: HV-4 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-4 Project: Hibernate Validator Type: Patch Environment: Hibernate Annotations (all versions) Reporter: Juliano Carniel Priority: Trivial Attachments: ValidatorMessages_pt_BR.properties here´s a bundle with messages in the locale Portuguese (Brazil). Hope that´s useful. -- 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

18 years, 7 months

2
1
0 / 0

[Hibernate-JIRA] Commented: (ANN-9) Support interface inheritance mapping

by Barney Boisvert (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-9?page=comm... ] Barney Boisvert commented on ANN-9: ----------------------------------- Yeah, you're right. Sorry. We had some issue with polymorphism and interfaces Hibernate wasn't aware of, but it clearly wasn't HQL. It's been 9 months since that project, so I can't remember too clearly. > Support interface inheritance mapping > ------------------------------------- > > Key: ANN-9 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-9 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Versions: 3.1beta3 > Reporter: Gili > Attachments: hibernate3-annotations-3.1beta5-3896-3948.diff, hibernate3-annotations-3.1beta5-3896-4138.diff > > > It should be possible to create a mapping with interfaces, as described by the documentation here: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#inheritanc... > Specifically right now it is impossible to annotate interfaces and according to HBX-231 even if you could @Entity is only meant to get used on classes so the question becomes "what do you annotate it with?" > As I pointed out here http://forum.hibernate.org/viewtopic.php?p=2238824#2238824 the additional problem seems to be that XDoclet doesn't support interface annotation either (http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1345) so I'm left without a workaround. > I can't convert the interfaces to abstract classes because I implement multiple interfaces in my application and Java does not do multiple inheritance. > If you know of a nice workaround, please let me know :) -- 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

18 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2007