hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-1586) ClassCastException in CollectionType.toLoggableString if using CustomCollectionType

[Steve E. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1586?page=all ]
     
Steve Ebersole resolved HHH-1586:
---------------------------------

    Resolution: Fixed

> ClassCastException in CollectionType.toLoggableString if using CustomCollectionType
> -----------------------------------------------------------------------------------
>
>          Key: HHH-1586
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1586
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3, 3.1.2
>  Environment: Hibernate 3.1.2, Oracle 10g
>     Reporter: Stefan Fellner
>     Assignee: Steve Ebersole
>     Priority: Minor
>      Fix For: 3.2.0.cr3

>
>
> When implementing a UserCollectionType and setting the log-Level to debug, in CollectionType.toLoggableString a ClassCastException is thrown.
> I'll put a possible bugfix here:
> 	public String toLoggableString(Object value, SessionFactoryImplementor factory)
> 			throws HibernateException {
>         if ( value == null ) return "null";
>         
>         if ( Hibernate.isInitialized( value ) ) {
>             if ( getReturnedClass().isInstance(value) ) {
>                 List list = new ArrayList();
>                 Type elemType = getElementType( factory );
>                 Iterator iter = getElementsIterator( value );
>                 while ( iter.hasNext() ) {
>                     list.add( elemType.toLoggableString( iter.next(), factory ) );
>                 }
>                 return list.toString();
>             } else {
>                 // this would be my solution
>                 if (value instanceof Element) {
>                 // for DOM4J "collections" only
>                     return ( (Element) value ).asXML(); //TODO: it would be better if this was done at the higher level by Printer
>                 } else {
>                     return value.toString();
>                 }
>             }
>         }
>         else {
>             return "<uninitialized>";
>         }
> 		
> 	}
> The main problem is that UserCollectionType Interface doesn't contain getReturnedClass() method, so getReturnedClass().isInstance(value)  will fail in case of UserCollectionTypes and in the else  value is casted to org.dom4j.Element, while value is an instance of the UserCollectionType, which causes ClassCastException.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HHH-1881) introduce LoggableUserType interface

[Steve E. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1881?page=all ]
     
Steve Ebersole closed HHH-1881:
-------------------------------

    Resolution: Fixed

> introduce LoggableUserType interface
> ------------------------------------
>
>          Key: HHH-1881
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1881
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Reporter: Steve Ebersole
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0.cr3

>
>
> Add an optional org.hibernate.usertype.LoggableUserType interface which users can implement to apply custom logging for values corresponding to their custom types.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1586) ClassCastException in CollectionType.toLoggableString if using CustomCollectionType

[Steve E. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1586?page=all ]

Steve Ebersole updated HHH-1586:
--------------------------------

    Fix Version: 3.2.0.cr3
      Assign To: Steve Ebersole

Modified version will actually look like:
	public String toLoggableString(Object value, SessionFactoryImplementor factory)
			throws HibernateException {
		if ( value == null ) {
			return "null";
		}
		else if ( !Hibernate.isInitialized( value ) ) {
			return "<uninitialized>";
		}
		else {
			return renderLoggableString( value, factory );
		}
	}

	protected String renderLoggableString(Object value, SessionFactoryImplementor factory)
			throws HibernateException {
		if ( Element.class.isInstance( value ) ) {
			// for DOM4J "collections" only
			// TODO: it would be better if this was done at the higher level by Printer
			return ( ( Element ) value ).asXML();
		}
		else {
			List list = new ArrayList();
			Type elemType = getElementType( factory );
			Iterator iter = getElementsIterator( value );
			while ( iter.hasNext() ) {
				list.add( elemType.toLoggableString( iter.next(), factory ) );
			}
			return list.toString();
		}
	}

Note that HHH-1881 also can now be used to effect this processing...

> ClassCastException in CollectionType.toLoggableString if using CustomCollectionType
> -----------------------------------------------------------------------------------
>
>          Key: HHH-1586
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1586
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3, 3.1.2
>  Environment: Hibernate 3.1.2, Oracle 10g
>     Reporter: Stefan Fellner
>     Assignee: Steve Ebersole
>     Priority: Minor
>      Fix For: 3.2.0.cr3

>
>
> When implementing a UserCollectionType and setting the log-Level to debug, in CollectionType.toLoggableString a ClassCastException is thrown.
> I'll put a possible bugfix here:
> 	public String toLoggableString(Object value, SessionFactoryImplementor factory)
> 			throws HibernateException {
>         if ( value == null ) return "null";
>         
>         if ( Hibernate.isInitialized( value ) ) {
>             if ( getReturnedClass().isInstance(value) ) {
>                 List list = new ArrayList();
>                 Type elemType = getElementType( factory );
>                 Iterator iter = getElementsIterator( value );
>                 while ( iter.hasNext() ) {
>                     list.add( elemType.toLoggableString( iter.next(), factory ) );
>                 }
>                 return list.toString();
>             } else {
>                 // this would be my solution
>                 if (value instanceof Element) {
>                 // for DOM4J "collections" only
>                     return ( (Element) value ).asXML(); //TODO: it would be better if this was done at the higher level by Printer
>                 } else {
>                     return value.toString();
>                 }
>             }
>         }
>         else {
>             return "<uninitialized>";
>         }
> 		
> 	}
> The main problem is that UserCollectionType Interface doesn't contain getReturnedClass() method, so getReturnedClass().isInstance(value)  will fail in case of UserCollectionTypes and in the else  value is casted to org.dom4j.Element, while value is an instance of the UserCollectionType, which causes ClassCastException.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1881) introduce LoggableUserType interface

[Steve E. (JIRA) <no...@at...>]

introduce LoggableUserType interface
------------------------------------

         Key: HHH-1881
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1881
     Project: Hibernate3
        Type: Improvement

  Components: core  
    Reporter: Steve Ebersole
 Assigned to: Steve Ebersole 
     Fix For: 3.2.0.cr3


Add an optional org.hibernate.usertype.LoggableUserType interface which users can implement to apply custom logging for values corresponding to their custom types.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1789) improve efficiency of collection initialization from L2 cache hits

[Steve E. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1789?pa=
ge=3Dcomments#action_23537 ]=20

Steve Ebersole commented on HHH-1789:
-------------------------------------

Note this requires addition of method to both CollectionType and UserCollec=
tionType in the form:
public Object instantiate(int anticipatedSize);

> improve efficiency of collection initialization from L2 cache hits
> ------------------------------------------------------------------
>
>          Key: HHH-1789
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/H=
HH-1789
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>  Environment: hibernate 3, db n/a
>     Reporter: Aapo Kyr=C3=B6l=C3=A4
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0.cr3

>
>
> We have an entity which has a <map>-type of collection attached to it, th=
at uses <many-to-many> mapping. The map has cache setting of <cache usage=
=3D"nonstrict-read-write"/>=20
> The problem is that the map is often quite large, 500-1000 elements in it=
. But when Hibernate3 instantiates it from cache (PersistentMap.initializeF=
romCache()), it will create a HashMap with default parameters and then .put=
() each item from the serialized cache data to the map.=20
> HashMap default size is 16 and it resizes it to double always when it has=
 75%*capacity elements in it. So, initializing a HashMap with 1000 entries =
will cause 7 resizes (which are expensive): 16->32->64->128->256->512->1024=
->2048. This consumes a lot of memory and cpu because HashMap.resize() is a=
 costly operation.=20
> It would be better for Hibernate to initialize the map with loadfactor 1.=
0 and size of the cached serialized data array / 2 + some extra.=20

--=20
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=
.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1789) improve efficiency of collection initialization from L2 cache hits

[Steve E. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1789?p=
age=3Dall ]

Steve Ebersole updated HHH-1789:
--------------------------------

      Component: core
        Summary: improve efficiency of collection initialization from L2 ca=
che hits  (was: HashMap initialization is very unefficient in cache hits)
    Fix Version: 3.2.0.cr3
      Assign To: Steve Ebersole
       Priority: Major

> improve efficiency of collection initialization from L2 cache hits
> ------------------------------------------------------------------
>
>          Key: HHH-1789
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/H=
HH-1789
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>  Environment: hibernate 3, db n/a
>     Reporter: Aapo Kyr=C3=B6l=C3=A4
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0.cr3

>
>
> We have an entity which has a <map>-type of collection attached to it, th=
at uses <many-to-many> mapping. The map has cache setting of <cache usage=
=3D"nonstrict-read-write"/>=20
> The problem is that the map is often quite large, 500-1000 elements in it=
. But when Hibernate3 instantiates it from cache (PersistentMap.initializeF=
romCache()), it will create a HashMap with default parameters and then .put=
() each item from the serialized cache data to the map.=20
> HashMap default size is 16 and it resizes it to double always when it has=
 75%*capacity elements in it. So, initializing a HashMap with 1000 entries =
will cause 7 resizes (which are expensive): 16->32->64->128->256->512->1024=
->2048. This consumes a lot of memory and cpu because HashMap.resize() is a=
 costly operation.=20
> It would be better for Hibernate to initialize the map with loadfactor 1.=
0 and size of the cached serialized data array / 2 + some extra.=20

--=20
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=
.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1880) Syntax Error in .hbm.xml file reports error but is missing replacement text

[Arnie M. (JIRA) <no...@at...>]

Syntax Error in .hbm.xml file reports error but is missing replacement text
---------------------------------------------------------------------------

         Key: HHH-1880
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1880
     Project: Hibernate3
        Type: Bug

  Components: metamodel  
    Versions: 3.0.2    
 Environment: Hibernate 3.0.2, Sybase 12.5.3, PeopleSoft 8's Job_Code table
    Reporter: Arnie Morein
    Priority: Minor


This table has 122 fields. I made a typo in the definition of a field thusly:

<property name="GvtFunctionClass" column="string" type="" update="false" insert="false"/>

should have been:
<property name="GvtFunctionClass" column="GVT_FUNC_CLASS" type="string" update="false" insert="false"/>

Obviously, Hibernate reported an error - but it wasn't every helpful:
2006-07-05 09:02:18,750 ERROR [org.jboss.hibernate.jmx.Hibernate] Starting failed jboss.jca:service=HbmEmployeeWarehouse
org.hibernate.MappingException: Could not determine type for: , for columns: [org.hibernate.mapping.Column(string)]
	at org.hibernate.mapping.SimpleValue.getType(SimpleValue.java:265)

Two Things:

1) The error is in the HbmPsJobCodeTable.hbm.xml file - NOT the HbmEmployeeWarehouse.hbm.xml file.
2) Missing substitution values for the error string "Could not determine type for: , for columns: " apparently aren't making it into the string prior to its output. Perhaps 1 is related to 2?

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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (ANN-387) lucene integration does not support Inheritance

[masrawi (JIRA) <no...@at...>]

lucene integration does not support Inheritance
-----------------------------------------------

         Key: ANN-387
         URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-387
     Project: Hibernate Annotations
        Type: Improvement

  Components: lucene  
 Environment: all
    Reporter: masrawi


the annotations of lucene does not support inherited classes, the annotaions should have @Inherited in order to be seen from the child class, otherwise we will have to override methods like getId and the such in order to get it to work

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1879) cache not only by id, but by natural-id to.

[Olexandr D. (JIRA) <no...@at...>]

cache not only by id, but by natural-id to.
-------------------------------------------

         Key: HHH-1879
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1879
     Project: Hibernate3
        Type: Improvement

  Components: core  
    Versions: 3.1.3    
    Reporter: Olexandr Demura
    Priority: Minor
 Attachments: cachetest.zip

it's will be good if Hibernate will cache object's not only by id, but by natural-id to.

i think HHH-1174 isn't a bug, but need's improvement.

for example, we have legacy DB structure, where Foo referenced to Bar by it's natural-id, see atachment.
on load Foo query Hibernate will produce unnecessary SQL to load two referenced Bars, which will be loaded in the first SQL for Foo by fetch anyway.


-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (ANN-265) Fall back to default validator message if the key is not found

[Emmanuel B. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-265?page=all ]

Emmanuel Bernard updated ANN-265:
---------------------------------

    Summary: Fall back to default validator message if the key is not found  (was: Consider changing ValidatorMEssage.properties to message.properties)

> Fall back to default validator message if the key is not found
> --------------------------------------------------------------
>
>          Key: ANN-265
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-265
>      Project: Hibernate Annotations
>         Type: Improvement

>   Components: validator
>     Reporter: Emmanuel Bernard
>     Assignee: Emmanuel Bernard
>     Priority: Minor
>      Fix For: 3.2.0

>
>


-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1870) org.hibernate.TransientObjectException: object references an unsaved transient

[Assaf B. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1870?page=comments#action_23535 ] 

Assaf Berg commented on HHH-1870:
---------------------------------

You might need to force a session flush between saving B and saving A in case the association doesn't have cascade.
The load would probably not cause a flush because B is already in the session cache.


> org.hibernate.TransientObjectException: object references an unsaved transient 
> -------------------------------------------------------------------------------
>
>          Key: HHH-1870
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1870
>      Project: Hibernate3
>         Type: Bug

>  Environment: Hibernate 3.2.0 RC 2 from SVN tunk 2006/06/30
>     Reporter: Sergey Vladimirov
>  Attachments: manytoonelazy.zip, patch.txt
>
>
> JUnit test case shows strange error on commit():
>             Session session = sessionFactory.openSession();
>             Transaction transaction = session.beginTransaction();
>             BeanB beanB = new BeanB();
>             beanB.setId(1);
>             session.save(beanB);
>             beanB = (BeanB) session.load(BeanB.class, 1);
>             BeanA beanA = new BeanA();
>             beanA.setId(2);
>             beanA.setParent((BeanB) session.load(BeanB.class, 1));
>             session.save(beanA);
>             transaction.commit();
>             session.close();
> org.hibernate.TransientObjectException: object references an unsaved transient instance - save the transient instance before flushing: ru.arptek.arpsite.data.manytoonelazy.BeanA.parent -> ru.arptek.arpsite.data.manytoonelazy.BeanB
> 	at org.hibernate.engine.CascadingAction$9.noCascade(CascadingAction.java:273)
> 	at org.hibernate.engine.Cascade.cascade(Cascade.java:257)
> 	at org.hibernate.event.def.AbstractFlushingEventListener.cascadeOnFlush(AbstractFlushingEventListener.java:131)
> 	at org.hibernate.event.def.AbstractFlushingEventListener.prepareEntityFlushes(AbstractFlushingEventListener.java:121)
> 	at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:65)
> 	at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26)
> 	at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
> 	at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338)
> 	at org.hibernate.transaction.JTATransaction.commit(JTATransaction.java:135)
> 	at ru.arptek.arpsite.data.manytoonelazy.TestWithoutCache.testFind(TestWithoutCache.java:57)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at junit.framework.TestCase.runTest(TestCase.java:154)
> 	at junit.framework.TestCase.runBare(TestCase.java:127)
> 	at junit.framework.TestResult$1.protect(TestResult.java:106)
> 	at junit.framework.TestResult.runProtected(TestResult.java:124)
> 	at junit.framework.TestResult.run(TestResult.java:109)
> 	at junit.framework.TestCase.run(TestCase.java:118)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:208)
> 	at junit.framework.TestSuite.run(TestSuite.java:203)
> 	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Temporary patch included. May be it is brokes other issue.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1878) Using custom PropertyAccessor without specifying "type" may result in unexpected exception.

[J.C. v. V. (JIRA) <no...@at...>]

Using custom PropertyAccessor without specifying "type" may result in unexpected exception.
-------------------------------------------------------------------------------------------

         Key: HHH-1878
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1878
     Project: Hibernate3
        Type: Bug

    Versions: 3.1.2    
    Reporter: J.C. van Vorst
    Priority: Minor


For a java class using member variable prefixes:

This will work:
    <id name="_id" access="field">

This will not:
    <id name="id" access="my.UnderscoreFieldAccessor">

... and results in a misleading "org.hibernate.PropertyNotFoundException: field not found: id".   This is due to the configuration binding process assuming the property type should be accessible via reflection (i.e., tries to reflect on field "id" which does not exist).

After tracing the cause, it's reasonable that "type" must to be specified absent other means of determining the property class, but the documentation doesn't mention it, and the condition checking to determine the appropriate exception is insufficient.


-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1877) ClassNotFoundException on my entity-name in a join tag

[Christian M. (JIRA) <no...@at...>]

ClassNotFoundException on my entity-name in a join tag
------------------------------------------------------

         Key: HHH-1877
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1877
     Project: Hibernate3
        Type: Bug

    Versions: 3.1.3    
 Environment: Hibernate 3.1.3, Spring 1.2.8, Oracle 9I, Windows XP (localhost)
    Reporter: Christian Mineau


I use the attribute "entity-name" in my class mapping, this is for mapping the same object many times on table(s), and all seem to work normally. I found a problem when I tried to join a table on another class mapping, like: 

     <class entity-name="categoryDefault" name="ca.cie.pak.CategoryVO" table="CATEGORY">
		    <id name="id" column="CATEGORY_ID" type="java.lang.Integer">
                <generator class="native"/>
            </id>
            <property name="name" column="NAME"/>
            
		 <bag name="contents" where="priority = 0"> 
		     <key column="CATEGORY_ID" />
		     <one-to-many entity-name="ContentSummary"/>
		 </bag>
		    
		 <join table="LAYOUT_CATEGORY">
		      <key foreign-key="CATEGORY_ID" column="CATEGORY_ID" />
	            <property  name="layoutId" column="LAYOUT_ID"/>
            </join>  		    
		</class> 

I found a ClassNotFoundException: categoryDefault. This exception is thrown when the HbmBinder.bindJoin method is called. I see the code and it tries to instantiate a class from the getEntityName and not by the className. 

Someone can answer me if this is a XML mapping error or a real bug and what I need to do.


-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1876) xsd mapping / session factory conformance

[Emmanuel B. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1876?page=comments#action_23534 ] 

Emmanuel Bernard commented on HHH-1876:
---------------------------------------

Unless from a external contribution I don't see that as a priority. Esp because portable xsd validation is inexistent and xsd chasspath lookup is a dirty hack.

> xsd mapping / session factory conformance
> -----------------------------------------
>
>          Key: HHH-1876
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1876
>      Project: Hibernate3
>         Type: New Feature

>   Components: core
>  Environment: any env, any Hib version
>     Reporter: erwan le goulven

>
> Original Estimate: 1 week
>         Remaining: 1 week
>
> As xsd is becoming more popular than DTD's, and as Xsd-to-java tools are more reliable thant dtd-to-java ones,  I'm filling this FR in order to see hibconfig as well as hib mapping files conform to xsd schema and not a dtd.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-545) Hibernate doesn't seem to allow nested properties in an Order object.

[Eric C. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-545?page=comments#action_23533 ] 

Eric Coupal commented on HHH-545:
---------------------------------

Actually, i also need a workaround fort that, i tried to get the sql query string to pipe the orderby but getQueryString doesnt exist in hibernate3. 

> Hibernate doesn't seem to allow nested properties in an Order object.
> ---------------------------------------------------------------------
>
>          Key: HHH-545
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-545
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.0.5
>  Environment: Hibernate 3.0.5
> JBoss 4.0.2
> MySql 5.0.4 BETA
>     Reporter: Stephen Earl
>  Attachments: orderIssue.zip
>
>
> When passing "nested" properties in an Order expression a QueryException is thrown stating: could not resolve property: artist.name of: ami.server.dto.AlbumDTO.
> My mapping files are below:
> <album.hbm.xml> 
> <hibernate-mapping package="ami.server.dto"> 
> <class name="AlbumDTO" table="calliope.albums"> 
> <id name="id" column="id"> 
> <generator class="native"/> 
> </id> 
> <property name="title" column="title" not-null="true"/> 
> <property name="upc" column="upc" not-null="true"/> 
> <many-to-one name="artist" column="artist_id" class="ArtistDTO" fetch="join"/> 
> </class> 
> </hibernate-mapping> 
> <artist.hbm.xml> 
> <hibernate-mapping package="ami.server.dto"> 
> <class name="ArtistDTO" table="calliope.artists"> 
> <id name="id" column="id"> 
> <generator class="native"/> 
> </id> 
> <property name="name" column="name" not-null="true"/> 
> <property name="searchName" column="search_name" not-null="false"/> 
> </class> 
> </hibernate-mapping> 
> The full source code of the method being called is below:
> public List<AlbumDTO> findOrderBy (AlbumDTO obj, Order[] orderBy) throws Exception {
>     Criteria criteria = HibernateUtil.getSession().createCriteria(AlbumDTO.class);
>     criteria.add(Example.create(obj));
>     for (int i=0; i<orderBy.length; i++) {
>       criteria.addOrder(orderBy[i]);
>     }
>     return criteria.list();
>   }
> Should this functionality work in Hibernate 3.0.5?  Is it a bug?

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1876) xsd mapping / session factory conformance

[erwan le g. (JIRA) <no...@at...>]

xsd mapping / session factory conformance
-----------------------------------------

         Key: HHH-1876
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1876
     Project: Hibernate3
        Type: New Feature

  Components: core  
 Environment: any env, any Hib version
    Reporter: erwan le goulven


As xsd is becoming more popular than DTD's, and as Xsd-to-java tools are more reliable thant dtd-to-java ones,  I'm filling this FR in order to see hibconfig as well as hib mapping files conform to xsd schema and not a dtd.


-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1525) multiple cascades to the same transient instance within a single object graph

[Assaf B. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1525?page=comments#action_23532 ] 

Assaf Berg commented on HHH-1525:
---------------------------------

I think there's another scenario that arises from this problem.
Say you have a common class C which is refrenced both from A and B.
A is considered the owner of C so it has a cascade="save-update" to C, while B has cascade="none" and not-null="true". 

Now if I'm saving an instance of A with a new C instance, and want to create a reference to that same instance of C from B, i'll have to force a session flush first before saving B or I get an exception.

I would like the checks done when saving B to wait until A is actually saved (i.e. flushed). Or if it is not done in the same order I called save, at least check all associations with cascades before associations without...


> multiple cascades to the same transient instance within a single object graph
> -----------------------------------------------------------------------------
>
>          Key: HHH-1525
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1525
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Reporter: Steve Ebersole
>     Assignee: Steve Ebersole

>
>
> Consider an object graph being saved that contains the same transient instance multiple times (at diffierent levels in the graph) where some of the associations define cascading and some do not and that the associations without cascading are further defined as not-null.  Based on the order in which the associations are cascaded there is a potential for that transient instance to cause an "unsaved transient instance" exception if the non-cascaded and not-null association is cascaded to first, even though a subsequent cascaced would in fact cause the instance to become managed.
> Typically this is easy enough to work around by simply reordering the associations in the mapping so that the cascaded association is before the non-cascaded one.  However, this is not always possible (the case of inheritence hierarchies comes to mind, where the superclass associations are always cascaded to 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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1875) Fetch EAGER_SELECT for one-to-many associations

[Joris W. (JIRA) <no...@at...>]

Fetch EAGER_SELECT for one-to-many associations
-----------------------------------------------

         Key: HHH-1875
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1875
     Project: Hibernate3
        Type: New Feature

  Components: core  
    Versions: 3.1.3    
    Reporter: Joris Wijlens
    Priority: Minor


I create a criteria query for a object that has a one-to-many relation to another object. 

Now I can't use the FetchMode join to eagerly fetch the associated objects because i get an cartesian product. But FetchMode select does not select my associated object eagerly. I would like to have a FetchMode that does an eager select.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1750) Exception ORA-01000 too many open cursors by generated="insert"

[Benoit Goudreault-E. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1750?page=comments#action_23531 ] 

Benoit Goudreault-Emond commented on HHH-1750:
----------------------------------------------

I've inspected the code in 3.2, and the bug is still there (unclosed PreparedStatement & ResultSet).

Would it be possible to apply the patch prior to the 3.2 release?  It's a very simple patch, and I believe it's obvious that the ResultSet and PreparedStatement ought to be closed.  Especially since it's done in every other method in AbstractEntityPersister.  Leaving PreparedStatements unclosed is extremely bad when using Oracle--it will exhaust cursors very quickly.

I'd hate to have to recompile a custom hibernate version every time a new release comes out...

> Exception ORA-01000 too many open cursors by generated="insert"
> ---------------------------------------------------------------
>
>          Key: HHH-1750
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1750
>      Project: Hibernate3
>         Type: Bug

>  Environment: Hibernate3, Oracle10g
>     Reporter: Andreas Dornhof
>  Attachments: HHH-1750.patch
>
>
> When creating  more as 300 Object in Oracle with insert="false" and generated="insert" by property - Tag in Mapping-File
> causes an ORA-01000  "too many open cursors"...
> It is executed using the following Java code:
> SessionFactory sessionFactory;
>     	
>     	try {
>             // Create the SessionFactory from hibernate.cfg.xml
>             sessionFactory = new Configuration().
>             						configure().
>             						buildSessionFactory();
>         } catch (Throwable ex) {
>             // Make sure you log the exception, as it might be swallowed
>             System.err.println("Initial SessionFactory creation failed." + ex);
>             throw new ExceptionInInitializerError(ex);
>         }
>     
>         try{
>     
>         	for (int i = 0; i <= 301; i++) {
>         		
>         	Session session = sessionFactory.getCurrentSession();
>         	Transaction tx = session.beginTransaction();
> 							
> 	        Test test = new Test();
> 	        session.save(test);
> 	        
> 	        tx.commit();
> 	        
>         	}
>     
> 		    } catch (Exception e) {
> 				System.out.println(e.getMessage()+e.getClass().toString());
> 			}
>     
> And Mapping - File:
> <?xml version="1.0"?>
> <!DOCTYPE hibernate-mapping PUBLIC
> 	"-//Hibernate/Hibernate Mapping DTD//EN"
> 	"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd" >
> <hibernate-mapping>
> 	<class
> 		name="src.persistence.Test"
> 		table="TEST"
> 		
> 	>
> 		<id name="id" type="java.lang.Long" column="ID"
> 		>
> 			<generator class="sequence">
> 				<param name="sequence">TEST_SEQ</param>
> 			</generator>
> 		</id>
> 		<property
> 			name="created"
> 			column="CREATED"
> 			type="java.util.Date"
> 			not-null="true"
> 			insert="false"
> 			update="false"
> 			generated="insert"
> 		>
> 		</property>
> 	</class>	
> </hibernate-mapping>

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1874) Problem mapping properties names which consists of several words

[Luis P. (JIRA) <no...@at...>]

Problem mapping properties names which consists of several words
----------------------------------------------------------------

         Key: HHH-1874
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1874
     Project: Hibernate3
        Type: Bug

    Versions: 3.0.5    
 Environment: Hibernate 3.0.5
hsqldb 1.8
    Reporter: Luis Parravicini


I'm having problems trying to map certain properties.
Having a class with a property named nChilds and public getter/setter:

public class Test {
    private int nChilds;
    ....
    public int getNChilds() { return nChilds; }
    public void setNChilds(int nChilds) { this.nChilds = nChilds; }
    ....
}


The property is mapped as:
    <property name="nChilds" not-null="true"/>


And I get the exception:
org.hibernate.PropertyNotFoundException: Could not find a getter for nChilds in class ar.com.itboss.Test


When I replace all occurrences of nChilds to other name, like numberChilds it works. It seems the problem is when the property name is composed of several words and the first one is only a letter long.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HHH-1873) Query the hibernate version through the API

[Steve E. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1873?page=all ]
     
Steve Ebersole closed HHH-1873:
-------------------------------

    Resolution: Rejected

org.hibernate.cfg.Environment.VERSION

> Query the hibernate version through the API
> -------------------------------------------
>
>          Key: HHH-1873
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1873
>      Project: Hibernate3
>         Type: New Feature

>   Components: core
>     Reporter: Mark Grand
>     Priority: Minor

>
> Original Estimate: 2 hours
>         Remaining: 2 hours
>
> I am building a tool that will work with hibernate. Though this tool will be used with hibernate, I want it to work with whatever version of hibernate my users select. Making this work with future versions of hibernate will be eaiser if there is something in the API that says what the version of hibernate is.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1873) Query the hibernate version through the API

[Mark G. (JIRA) <no...@at...>]

Query the hibernate version through the API
-------------------------------------------

         Key: HHH-1873
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1873
     Project: Hibernate3
        Type: New Feature

  Components: core  
    Reporter: Mark Grand
    Priority: Minor


I am building a tool that will work with hibernate. Though this tool will be used with hibernate, I want it to work with whatever version of hibernate my users select. Making this work with future versions of hibernate will be eaiser if there is something in the API that says what the version of hibernate is.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1854) Shoulb be able to specify cache enties to evict in generated SQL query

[Sergey V. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1854?page=all ]

Sergey Vladimirov updated HHH-1854:
-----------------------------------

    Attachment: patch-1.txt
                patch-2.txt

add getAffectedTables and setAffectedTables methods

> Shoulb be able to specify cache enties to evict in generated SQL query
> ----------------------------------------------------------------------
>
>          Key: HHH-1854
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1854
>      Project: Hibernate3
>         Type: New Feature

>   Components: core
>     Versions: 3.2.0.cr2
>  Environment: Hibernate cr2
>     Reporter: Sergey Vladimirov
>  Attachments: patch-1.txt, patch-2.txt
>
>
> For example:
>             Query updateQuery = entityManager.createNativeQuery("INSERT INTO "
>                     + table + "(" + field + ") VALUES(?)");
>             if (updateQuery instanceof HibernateQuery) {
>                 org.hibernate.Query hibUpdateQuery = ((HibernateQuery) updateQuery)
>                         .getHibernateQuery();
>                 if (hibUpdateQuery instanceof SQLQuery)  {
>                     SQLQuery query = (SQLQuery) hibUpdateQuery;
>                     //specify tables to clear after update
>                 }
>             }
> I want to specify, that only table with name from variable "table" should be cleared. Or that some entires should be evicted. But I need to prevent FULL second-level cache eviction.

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Resolved: (ANN-386) Add support for RAMDirectory

[Emmanuel B. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-386?page=all ]
     
Emmanuel Bernard resolved ANN-386:
----------------------------------

    Resolution: Fixed

contributed by Sylvain

> Add support for RAMDirectory
> ----------------------------
>
>          Key: ANN-386
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-386
>      Project: Hibernate Annotations
>         Type: New Feature

>   Components: lucene
>     Reporter: Emmanuel Bernard
>     Assignee: Emmanuel Bernard
>      Fix For: 3.2.0

>
>


-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (ANN-386) Add support for RAMDirectory

[Emmanuel B. (JIRA) <no...@at...>]

Add support for RAMDirectory
----------------------------

         Key: ANN-386
         URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-386
     Project: Hibernate Annotations
        Type: New Feature

  Components: lucene  
    Reporter: Emmanuel Bernard
 Assigned to: Emmanuel Bernard 
     Fix For: 3.2.0




-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira