hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Created: (ANN-378) Chinese translation (Xiaogang Cao)

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

Chinese translation (Xiaogang Cao)
----------------------------------

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

  Components: documentation  
    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

[Hibernate-issues] [Hibernate-JIRA] Created: (ANN-377) EntityBinder should use full qualified class names instead of class names

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

EntityBinder should use full qualified class names instead of class names
-------------------------------------------------------------------------

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

  Components: binder  
    Versions: 3.2.0.cr1    
 Environment: all
    Reporter: Thomas Weber


EntityBinder should use the full qualified class name to bind entities to simplify the use of entities with the same class name in larger projects. If the components of the project are from different developers the work-around with @Entity(name="someName") is not really useful, since it may not be possible to adapt the affected classes (i.e. if you do not have access to the source code)

The performance impact should be rather small since the String.equals(Object) method compares hashcodes first, so the String.length() is a minor factor for the speed of comparisons.

-- 
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-1236) Remove static reference to classloader, to avoid memory leak at webapp reload

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

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

Steve Ebersole commented on HHH-1236:
-------------------------------------

sigh...

you and i are officially done on this line of conversation

> Remove static reference to classloader, to avoid memory leak at webapp reload
> -----------------------------------------------------------------------------
>
>          Key: HHH-1236
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1236
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.0.5
>  Environment: Resin 3.0.15, CGLib 2.1_3
>     Reporter: Mattias Jiderhamn
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0.alpha1, 3.1.3
>  Attachments: OptimizeIt.jpg
>
>
> To avoid memory leaks when web applications reload, please either remove reference to classloader in org.hibernate.util.DTDEntityResolver or remove static reference to that class in org.hibernate.util.XMLHelper
> For background information, please see
> http://forum.hibernate.org/viewtopic.php?p=2275217#2275217
> http://opensource2.atlassian.com/confluence/spring/pages/viewpage.action?pageId=2669
> and attached screen shot

-- 
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-1236) Remove static reference to classloader, to avoid memory leak at webapp reload

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

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

G commented on HHH-1236:
------------------------

Because, to quote the Bug description at the top of the page:

"To avoid memory leaks when web applications reload, please either remove reference to classloader in org.hibernate.util.DTDEntityResolver or remove static reference to that class in org.hibernate.util.XMLHelper "

I however know enough about Java to know that using a static ClassLoader is a recipe for memory leaks. 

"ClassLoaders
The use of the Java ClassLoader construct is riddled with chances for memory leaks. What makes ClassLoaders so difficult from a memory-leak perspective is the complicated nature of the construct. ClassLoaders are different in that they are not just involved with "normal" object references, but are also meta-object references such as fields, methods, and classes. This means that as long as there are references to fields, methods, classes, or objects of a ClassLoader, the ClassLoader will stay in the JVM. Since the ClassLoader itself can hold on to a lot of classes as well as all their static fields, quite a bit of memory can be leaked. "


Please refer to this link for more information on the subject.
http://dev2dev.bea.com/pub/a/2005/06/memory_leaks.html

But if you have no intention of fixing this memory leak, can you, at least,  remove it from the resolved issues. I think there are a few people under the mistaken impression that this has been resolved.


> Remove static reference to classloader, to avoid memory leak at webapp reload
> -----------------------------------------------------------------------------
>
>          Key: HHH-1236
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1236
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.0.5
>  Environment: Resin 3.0.15, CGLib 2.1_3
>     Reporter: Mattias Jiderhamn
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0.alpha1, 3.1.3
>  Attachments: OptimizeIt.jpg
>
>
> To avoid memory leaks when web applications reload, please either remove reference to classloader in org.hibernate.util.DTDEntityResolver or remove static reference to that class in org.hibernate.util.XMLHelper
> For background information, please see
> http://forum.hibernate.org/viewtopic.php?p=2275217#2275217
> http://opensource2.atlassian.com/confluence/spring/pages/viewpage.action?pageId=2669
> and attached screen shot

-- 
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] Assigned: (HHH-1709) Be able to raise ENFE rather than LIE in proxies

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

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

Steve Ebersole reassigned HHH-1709:
-----------------------------------

    Assign To: Steve Ebersole

> Be able to raise ENFE rather than LIE in proxies
> ------------------------------------------------
>
>          Key: HHH-1709
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1709
>      Project: Hibernate3
>         Type: New Feature

>   Components: core
>     Reporter: Emmanuel Bernard
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0

>
>
> For HEM and EJB3

-- 
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-1709) Be able to raise ENFE rather than LIE in proxies

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

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

Steve Ebersole commented on HHH-1709:
-------------------------------------

I think we concluded in our discussions that being able to have a serialized proxy be able to route exception generation back through the configured EntityNotFoundDelegate is prohibitive; basically, we'd need to seperately track (and then ser/deser) the configured EntityNotFoundDelegate *on each proxy*.

> Be able to raise ENFE rather than LIE in proxies
> ------------------------------------------------
>
>          Key: HHH-1709
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1709
>      Project: Hibernate3
>         Type: New Feature

>   Components: core
>     Reporter: Emmanuel Bernard
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0

>
>
> For HEM and EJB3

-- 
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-1849) Query on a one-to-one association with foreign generator does not work

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

Query on a one-to-one association with foreign generator does not work
----------------------------------------------------------------------

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

  Components: core  
    Versions: 3.2.0.cr2    
 Environment: There is no exception under hsqldb but there is one with msde or firebird.
    Reporter: Sebastien Cesbron
 Attachments: test-foreign.zip

I have 2 classes Master and Slave with Master that has a foreign generator on slave.
  <class name="Master">
    <id name="oid">
      <generator class="foreign">
      <param name="property">slave</param>
      </generator>
    </id>
    <property name="libelle" type="string" />
    <one-to-one name="slave" class="Slave" constrained="true"/>
  </class>
If I do :
query = session.createQuery("from Master master where master.slave=:slave");
query.setParameter("slave", slave);
query.list();
There is a problem because the parameter is not set. Under hsqldb, there is no exception but the query return nothing. Under msde or firebird there is an exception. Under firebird it is "org.firebirdsql.jdbc.FBMissingParameterException: Not all parameters were set.".

The same query on slave's oid works :
query = session.createQuery("from Master master where master.slave.oid=:oid");
query.setParameter("oid", 1);
query.list();

I've attached a simple project that shows the problem. I have tested this project with hibernate 3.0.5 and hibernate 3.2.0cr2. It works with the first one but not with the latter one.


-- 
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-1573) one-to-many fails on oracle if field starts with underscore

[Marco R. (JIRA) <no...@at...>]

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

Marco Reimann commented on HHH-1573:
------------------------------------

Since I also encountered this problem I created a TestCase to reproduce it =
based on the 3.2 CR2 Release and a fix that in my opinion solves the proble=
m.=20

To run the test, unpack leadingunderscore.zip into the Hibernate3/test/org/=
hibernate/test directory.

Could you please check this out and include the fix in one of the next rele=
ases?

Thanks

Marco Reimann

> one-to-many fails on oracle if field starts with underscore
> -----------------------------------------------------------
>
>          Key: HHH-1573
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/H=
HH-1573
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.2
>     Reporter: Stephen Friedrich
>  Attachments: leadingunderscore.zip, org.hibernate.util.StringHelper.patc=
h
>
>
> Hibernate generates SQL that is invalid on Oracle, because it has fields =
in the select clause that start with an underscore.
> This is my field declaration:
>     @OneToMany(cascade =3D CascadeType.ALL, fetch =3D FetchType.EAGER, ma=
ppedBy =3D "_user")
>     private Set<Permission> _permissions =3D new HashSet<Permission>();
> And this is the generated SQL:
> select
> =09_permissio0_.user_id as user4_2_,
> =09_permissio0_.id as id2_,=20
> =09_permissio0_.id as id40_1_,=20
> =09_permissio0_.version as version40_1_,=20
> =09_permissio0_.guid as guid40_1_,=20
> =09_permissio0_.user_id as user4_40_1_,=20
> =09_permissio0_2_.company_reference_id as company2_42_1_,=20
> case
> =09when _permissio0_1_.permission_id is not null then 1=20
> =09when _permissio0_2_.permission_id is not null then 2=20
> =09when _permissio0_.id is not null then 0
> end
> as
> =09clazz_1_,
> =09companyref1_.id as id43_0_,
> =09companyref1_.version as version43_0_,
> =09companyref1_.guid as guid43_0_,
> =09companyref1_.db_user_name as db4_43_0_,=20
> =09companyref1_.company_name as company5_43_0_=20
> from=20
> =09permissions _permissio0_=20
> =09left outer join admin_permissions _permissio0_1_ on _permissio0_.id=3D=
_permissio0_1_.permission_id=20
> =09left outer join company_permissions _permissio0_2_ on _permissio0_.id=
=3D_permissio0_2_.permission_id=20
> =09left outer join company_references companyref1_ on _permissio0_2_.comp=
any_reference_id=3Dcompanyref1_.id=20
> where _permissio0_.user_id=3D?
> When executed Oracle gives this error: "ORA-00911: Ung=C2=B3ltiges Zeiche=
n" ("invalid character" in german)
> If I remove the underscore in front of every occurence of "_permissio..."=
 then I can execute the SQL fine on the command line ("?" replaced by 1).
> This has been reported on the forum, but nobody answered. See last post i=
n=20
> http://forums.hibernate.org/viewtopic.php?t=3D929011&highlight=3Dora00911=
&sid=3Dc501920d028c78899884f5bfac8e827e

--=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-1573) one-to-many fails on oracle if field starts with underscore

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

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

 updated HHH-1573:
------------------

    Attachment: leadingunderscore.zip
                org.hibernate.util.StringHelper.patch

> one-to-many fails on oracle if field starts with underscore
> -----------------------------------------------------------
>
>          Key: HHH-1573
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/H=
HH-1573
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.2
>     Reporter: Stephen Friedrich
>  Attachments: leadingunderscore.zip, org.hibernate.util.StringHelper.patc=
h
>
>
> Hibernate generates SQL that is invalid on Oracle, because it has fields =
in the select clause that start with an underscore.
> This is my field declaration:
>     @OneToMany(cascade =3D CascadeType.ALL, fetch =3D FetchType.EAGER, ma=
ppedBy =3D "_user")
>     private Set<Permission> _permissions =3D new HashSet<Permission>();
> And this is the generated SQL:
> select
> =09_permissio0_.user_id as user4_2_,
> =09_permissio0_.id as id2_,=20
> =09_permissio0_.id as id40_1_,=20
> =09_permissio0_.version as version40_1_,=20
> =09_permissio0_.guid as guid40_1_,=20
> =09_permissio0_.user_id as user4_40_1_,=20
> =09_permissio0_2_.company_reference_id as company2_42_1_,=20
> case
> =09when _permissio0_1_.permission_id is not null then 1=20
> =09when _permissio0_2_.permission_id is not null then 2=20
> =09when _permissio0_.id is not null then 0
> end
> as
> =09clazz_1_,
> =09companyref1_.id as id43_0_,
> =09companyref1_.version as version43_0_,
> =09companyref1_.guid as guid43_0_,
> =09companyref1_.db_user_name as db4_43_0_,=20
> =09companyref1_.company_name as company5_43_0_=20
> from=20
> =09permissions _permissio0_=20
> =09left outer join admin_permissions _permissio0_1_ on _permissio0_.id=3D=
_permissio0_1_.permission_id=20
> =09left outer join company_permissions _permissio0_2_ on _permissio0_.id=
=3D_permissio0_2_.permission_id=20
> =09left outer join company_references companyref1_ on _permissio0_2_.comp=
any_reference_id=3Dcompanyref1_.id=20
> where _permissio0_.user_id=3D?
> When executed Oracle gives this error: "ORA-00911: Ung=C2=B3ltiges Zeiche=
n" ("invalid character" in german)
> If I remove the underscore in front of every occurence of "_permissio..."=
 then I can execute the SQL fine on the command line ("?" replaced by 1).
> This has been reported on the forum, but nobody answered. See last post i=
n=20
> http://forums.hibernate.org/viewtopic.php?t=3D929011&highlight=3Dora00911=
&sid=3Dc501920d028c78899884f5bfac8e827e

--=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] Deleted: (HB-1561) java.lang.UnsupportedOperationException The user must supply a JDBC connection

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

     [ http://opensource.atlassian.com/projects/hibernate/browse/HB-1561?page=all ]
     
Christian Bauer deleted HB-1561:
--------------------------------


>  java.lang.UnsupportedOperationException  The user must supply a JDBC connection
> --------------------------------------------------------------------------------
>
>          Key: HB-1561
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1561
>      Project: Hibernate2
>         Type: Bug

>  Environment: Hibernate2.1.2,Mysql
>     Reporter: Rengesh

>
>
> Pls help in correcting the error

-- 
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: (HB-1560) java.lang.UnsupportedOperationException The user must supply a JDBC connection

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

     [ http://opensource.atlassian.com/projects/hibernate/browse/HB-1560?page=all ]
     
Christian Bauer resolved HB-1560:
---------------------------------

    Resolution: Rejected

http://forum.hibernate.org/


>  java.lang.UnsupportedOperationException  The user must supply a JDBC connection
> --------------------------------------------------------------------------------
>
>          Key: HB-1560
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1560
>      Project: Hibernate2
>         Type: Bug

>     Versions: 2.1.2
>  Environment: hibernate2.1.2,Mysql
>     Reporter: Rengesh
>     Priority: Trivial
>  Attachments: openreportserror.txt
>
>


-- 
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: (HB-1561) java.lang.UnsupportedOperationException The user must supply a JDBC connection

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

 java.lang.UnsupportedOperationException  The user must supply a JDBC connection
--------------------------------------------------------------------------------

         Key: HB-1561
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1561
     Project: Hibernate2
        Type: Bug

 Environment: Hibernate2.1.2,Mysql
    Reporter: Rengesh
 Attachments: openreportserror.txt

Pls help in correcting the error

-- 
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: (HB-1560) java.lang.UnsupportedOperationException The user must supply a JDBC connection

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

 java.lang.UnsupportedOperationException  The user must supply a JDBC connection
--------------------------------------------------------------------------------

         Key: HB-1560
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1560
     Project: Hibernate2
        Type: Bug

    Versions: 2.1.2    
 Environment: hibernate2.1.2,Mysql
    Reporter: Rengesh
    Priority: Trivial
 Attachments: openreportserror.txt



-- 
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-1236) Remove static reference to classloader, to avoid memory leak at webapp reload

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

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

Steve Ebersole commented on HHH-1236:
-------------------------------------

Why on earth do you think that defining a static field somehow causes this issue?  If that was the case, every library and every app I know of would exhibit the same behaviour...

> Remove static reference to classloader, to avoid memory leak at webapp reload
> -----------------------------------------------------------------------------
>
>          Key: HHH-1236
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1236
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.0.5
>  Environment: Resin 3.0.15, CGLib 2.1_3
>     Reporter: Mattias Jiderhamn
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0.alpha1, 3.1.3
>  Attachments: OptimizeIt.jpg
>
>
> To avoid memory leaks when web applications reload, please either remove reference to classloader in org.hibernate.util.DTDEntityResolver or remove static reference to that class in org.hibernate.util.XMLHelper
> For background information, please see
> http://forum.hibernate.org/viewtopic.php?p=2275217#2275217
> http://opensource2.atlassian.com/confluence/spring/pages/viewpage.action?pageId=2669
> and attached screen shot

-- 
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-1236) Remove static reference to classloader, to avoid memory leak at webapp reload

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

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

G commented on HHH-1236:
------------------------

Has this issue really been resolved. A quick look at the source code - reveals that the static refernce has not been removed.
At least for the source cod ein 3.1.3 and 3.2.alpha
I have downloaded the source for both, and in org.hibernate.utils.XMLHelper the static reference to DTDEntityResolver

i.e. This is the current source code in both versions.
public final class XMLHelper {

	private static final Log log = LogFactory.getLog(XMLHelper.class);
	public static final EntityResolver DEFAULT_DTD_RESOLVER = new DTDEntityResolver();

> Remove static reference to classloader, to avoid memory leak at webapp reload
> -----------------------------------------------------------------------------
>
>          Key: HHH-1236
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1236
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.0.5
>  Environment: Resin 3.0.15, CGLib 2.1_3
>     Reporter: Mattias Jiderhamn
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0.alpha1, 3.1.3
>  Attachments: OptimizeIt.jpg
>
>
> To avoid memory leaks when web applications reload, please either remove reference to classloader in org.hibernate.util.DTDEntityResolver or remove static reference to that class in org.hibernate.util.XMLHelper
> For background information, please see
> http://forum.hibernate.org/viewtopic.php?p=2275217#2275217
> http://opensource2.atlassian.com/confluence/spring/pages/viewpage.action?pageId=2669
> and attached screen shot

-- 
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-1848) A session.lock generates a query with a version column in a joined subclass which does not exist

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

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

Eduard Mossinkoff updated HHH-1848:
-----------------------------------

    Attachment: screenshot-1.jpg

Hibernate console showing subclass with version property

> A session.lock generates a query with a version column in a joined subclass which does not exist
> ------------------------------------------------------------------------------------------------
>
>          Key: HHH-1848
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1848
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.2.0.cr2
>  Environment: Windows XP Pro SP2 (full update)
> Java 1.5.0_06
> Postgres 8.1
> postgresql-8.1-404.jdbc3.jar
> Annotations 3.2.0 cr1
> hibernatetools-3.1.0.beta5
>     Reporter: Eduard Mossinkoff
>     Priority: Minor
>  Attachments: screenshot-1.jpg, screenshot-1.jpg
>
>
> A joined class hierarchy using annotations has a version property named "optlock" like in the annotation reference.
> The session factory in the Eclipse Hibernate console shows the joined subclass and it contains the "id" and "version" properties inherited from its superclass. The generated schema only has the version property in the table representing the root entity. The subclass has no "optlock" column. Now when a session.lock() is called with an instance of the subclass as its parameter and lockmode "UPGRADE", a query is generated including the "optlock" column on the subclass table which doesn't exist in the schema.
> The root entity, only showing the relevant properties
> @Entity
> @Inheritance(strategy = InheritanceType.JOINED)
> @AccessType("field")
> public class ModelObject implements Serializable, AccessControl {
> 	private static final long serialVersionUID = 2354579396538279696L;
> 	transient public static final int STORAGE_COSTS = 10;
> 	@Id
> 	@GeneratedValue(generator = "system-uuid")
> 	@GenericGenerator(name = "system-uuid", strategy = "uuid")
> 	private String id;
> 	@Version
> 	@Column(name="optlock")
> 	private Integer version;
> }
> A sub class 
> @Entity
> @AccessType("field")
> public class Item extends ModelObject implements Cloneable, Serializable {
> }
> @Entity
> @AccessType("field")
> public class Domain extends Item {
>       protected String domainId = null;
> }
> @Entity
> @AccessType("field")
> public class UserDomain extends Domain {
>         private long lastLoginDate;
> }
> The Hibernate console shows:
> org.across.model.UserDomain
> +id:java.lang.String
> +version:java.lang.Integer
> The database table of ModelObject
> CREATE TABLE dev.modelobject
> (
>   id varchar(255) NOT NULL,
>   optlock int4,
>   acl_id varchar(255),
>   CONSTRAINT modelobject_pkey PRIMARY KEY (id),
>   CONSTRAINT fk78ba6fa841f3e430 FOREIGN KEY (acl_id)
>       REFERENCES dev.acl (id) MATCH SIMPLE
>       ON UPDATE NO ACTION ON DELETE NO ACTION
> ) 
> WITHOUT OIDS;
> ALTER TABLE dev.modelobject OWNER TO across;
> The UserDomain table
> CREATE TABLE dev.userdomain
> (
>   id varchar(255) NOT NULL,
>   lastlogindate int8 NOT NULL,
>   CONSTRAINT userdomain_pkey PRIMARY KEY (id),
>   CONSTRAINT fkbbd6448faf7c2769 FOREIGN KEY (id)
>       REFERENCES dev."domain" (id) MATCH SIMPLE
>       ON UPDATE NO ACTION ON DELETE NO ACTION
> ) 
> WITHOUT OIDS;
> ALTER TABLE dev.userdomain OWNER TO across;
> The query generated when calling session.lock(userDomain, LockMode.UPGRADE); where userDomain is an instance created in a different session that was closed. 
> Hibernate: select id from dev.UserDomain where id =? and optlock =? for update
> 7625 [main] WARN  org.hibernate.util.JDBCExceptionReporter  - SQL Error: 0, SQLState: 42703
> 7625 [main] ERROR org.hibernate.util.JDBCExceptionReporter  - ERROR: column "optlock" does not exist
> The "optlock" column is not present in the UserDomain table only in the ModelObject table. 
> The question is, is the generated query wrong or is the Hibernate Eclipse tool generating a wrong schema.

-- 
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-1848) A session.lock generates a query with a version column in a joined subclass which does not exist

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

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

Eduard Mossinkoff updated HHH-1848:
-----------------------------------

    Attachment: screenshot-1.jpg

Hibernate console showing root class

> A session.lock generates a query with a version column in a joined subclass which does not exist
> ------------------------------------------------------------------------------------------------
>
>          Key: HHH-1848
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1848
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.2.0.cr2
>  Environment: Windows XP Pro SP2 (full update)
> Java 1.5.0_06
> Postgres 8.1
> postgresql-8.1-404.jdbc3.jar
> Annotations 3.2.0 cr1
> hibernatetools-3.1.0.beta5
>     Reporter: Eduard Mossinkoff
>     Priority: Minor
>  Attachments: screenshot-1.jpg, screenshot-1.jpg
>
>
> A joined class hierarchy using annotations has a version property named "optlock" like in the annotation reference.
> The session factory in the Eclipse Hibernate console shows the joined subclass and it contains the "id" and "version" properties inherited from its superclass. The generated schema only has the version property in the table representing the root entity. The subclass has no "optlock" column. Now when a session.lock() is called with an instance of the subclass as its parameter and lockmode "UPGRADE", a query is generated including the "optlock" column on the subclass table which doesn't exist in the schema.
> The root entity, only showing the relevant properties
> @Entity
> @Inheritance(strategy = InheritanceType.JOINED)
> @AccessType("field")
> public class ModelObject implements Serializable, AccessControl {
> 	private static final long serialVersionUID = 2354579396538279696L;
> 	transient public static final int STORAGE_COSTS = 10;
> 	@Id
> 	@GeneratedValue(generator = "system-uuid")
> 	@GenericGenerator(name = "system-uuid", strategy = "uuid")
> 	private String id;
> 	@Version
> 	@Column(name="optlock")
> 	private Integer version;
> }
> A sub class 
> @Entity
> @AccessType("field")
> public class Item extends ModelObject implements Cloneable, Serializable {
> }
> @Entity
> @AccessType("field")
> public class Domain extends Item {
>       protected String domainId = null;
> }
> @Entity
> @AccessType("field")
> public class UserDomain extends Domain {
>         private long lastLoginDate;
> }
> The Hibernate console shows:
> org.across.model.UserDomain
> +id:java.lang.String
> +version:java.lang.Integer
> The database table of ModelObject
> CREATE TABLE dev.modelobject
> (
>   id varchar(255) NOT NULL,
>   optlock int4,
>   acl_id varchar(255),
>   CONSTRAINT modelobject_pkey PRIMARY KEY (id),
>   CONSTRAINT fk78ba6fa841f3e430 FOREIGN KEY (acl_id)
>       REFERENCES dev.acl (id) MATCH SIMPLE
>       ON UPDATE NO ACTION ON DELETE NO ACTION
> ) 
> WITHOUT OIDS;
> ALTER TABLE dev.modelobject OWNER TO across;
> The UserDomain table
> CREATE TABLE dev.userdomain
> (
>   id varchar(255) NOT NULL,
>   lastlogindate int8 NOT NULL,
>   CONSTRAINT userdomain_pkey PRIMARY KEY (id),
>   CONSTRAINT fkbbd6448faf7c2769 FOREIGN KEY (id)
>       REFERENCES dev."domain" (id) MATCH SIMPLE
>       ON UPDATE NO ACTION ON DELETE NO ACTION
> ) 
> WITHOUT OIDS;
> ALTER TABLE dev.userdomain OWNER TO across;
> The query generated when calling session.lock(userDomain, LockMode.UPGRADE); where userDomain is an instance created in a different session that was closed. 
> Hibernate: select id from dev.UserDomain where id =? and optlock =? for update
> 7625 [main] WARN  org.hibernate.util.JDBCExceptionReporter  - SQL Error: 0, SQLState: 42703
> 7625 [main] ERROR org.hibernate.util.JDBCExceptionReporter  - ERROR: column "optlock" does not exist
> The "optlock" column is not present in the UserDomain table only in the ModelObject table. 
> The question is, is the generated query wrong or is the Hibernate Eclipse tool generating a wrong schema.

-- 
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-1848) A session.lock generates a query with a version column in a joined subclass which does not exist

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

A session.lock generates a query with a version column in a joined subclass which does not exist
------------------------------------------------------------------------------------------------

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

    Versions: 3.2.0.cr2    
 Environment: Windows XP Pro SP2 (full update)
Java 1.5.0_06
Postgres 8.1
postgresql-8.1-404.jdbc3.jar
Annotations 3.2.0 cr1
hibernatetools-3.1.0.beta5
    Reporter: Eduard Mossinkoff
    Priority: Minor


A joined class hierarchy using annotations has a version property named "optlock" like in the annotation reference.
The session factory in the Eclipse Hibernate console shows the joined subclass and it contains the "id" and "version" properties inherited from its superclass. The generated schema only has the version property in the table representing the root entity. The subclass has no "optlock" column. Now when a session.lock() is called with an instance of the subclass as its parameter and lockmode "UPGRADE", a query is generated including the "optlock" column on the subclass table which doesn't exist in the schema.

The root entity, only showing the relevant properties

@Entity
@Inheritance(strategy = InheritanceType.JOINED)
@AccessType("field")
public class ModelObject implements Serializable, AccessControl {

	private static final long serialVersionUID = 2354579396538279696L;

	transient public static final int STORAGE_COSTS = 10;

	@Id
	@GeneratedValue(generator = "system-uuid")
	@GenericGenerator(name = "system-uuid", strategy = "uuid")
	private String id;

	@Version
	@Column(name="optlock")
	private Integer version;
}

A sub class 
@Entity
@AccessType("field")
public class Item extends ModelObject implements Cloneable, Serializable {
}

@Entity
@AccessType("field")
public class Domain extends Item {
      protected String domainId = null;
}

@Entity
@AccessType("field")
public class UserDomain extends Domain {
        private long lastLoginDate;
}

The Hibernate console shows:
org.across.model.UserDomain
+id:java.lang.String
+version:java.lang.Integer

The database table of ModelObject
CREATE TABLE dev.modelobject
(
  id varchar(255) NOT NULL,
  optlock int4,
  acl_id varchar(255),
  CONSTRAINT modelobject_pkey PRIMARY KEY (id),
  CONSTRAINT fk78ba6fa841f3e430 FOREIGN KEY (acl_id)
      REFERENCES dev.acl (id) MATCH SIMPLE
      ON UPDATE NO ACTION ON DELETE NO ACTION
) 
WITHOUT OIDS;
ALTER TABLE dev.modelobject OWNER TO across;

The UserDomain table
CREATE TABLE dev.userdomain
(
  id varchar(255) NOT NULL,
  lastlogindate int8 NOT NULL,
  CONSTRAINT userdomain_pkey PRIMARY KEY (id),
  CONSTRAINT fkbbd6448faf7c2769 FOREIGN KEY (id)
      REFERENCES dev."domain" (id) MATCH SIMPLE
      ON UPDATE NO ACTION ON DELETE NO ACTION
) 
WITHOUT OIDS;
ALTER TABLE dev.userdomain OWNER TO across;

The query generated when calling session.lock(userDomain, LockMode.UPGRADE); where userDomain is an instance created in a different session that was closed. 

Hibernate: select id from dev.UserDomain where id =? and optlock =? for update
7625 [main] WARN  org.hibernate.util.JDBCExceptionReporter  - SQL Error: 0, SQLState: 42703
7625 [main] ERROR org.hibernate.util.JDBCExceptionReporter  - ERROR: column "optlock" does not exist

The "optlock" column is not present in the UserDomain table only in the ModelObject table. 

The question is, is the generated query wrong or is the Hibernate Eclipse tool generating a wrong schema.

-- 
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: (HHH-1792) Callable update/insert/delete statements should not force rowcount out parameter

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

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

    Resolution: Fixed

Introduced a new "check" attribute on the pertinent DTD elements:
<!ATTLIST sql-insert check (none|rowcount|param) #IMPLIED>

none = perform no update-count checking
rowcount = perform update-count checking based on the value returned by executeUpdate()/executeBatch()
param = perform update-count checking based on an output parameter (legacy callable checking)

Should we make none the default for callable statements moving forward?

> Callable update/insert/delete statements should not force rowcount out parameter
> --------------------------------------------------------------------------------
>
>          Key: HHH-1792
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1792
>      Project: Hibernate3
>         Type: Deprecation

>   Components: core
>     Versions: 3.1.3, 3.2.0.cr2
>     Reporter: Max Rydahl Andersen
>     Priority: Blocker
>      Fix For: 3.2.0

>
>
> the current handling of <sql-insert>, <sql-update>, <sql-delete> when callable="true" is broken.
> It "forcefully" requires users to have an out parameter at the first position that returns the rowcount and then simply ignores it!
> This only became obvious when trying to use the sql-update on DB2 where executeUpdate returns -1 opposed to what is done
> on Oracle and MS SQL Server.
> We need to fix this by either:
> a) actually start using this value (which requires the SP to return an expected value which in most cases just will be 1 or 0)
> b) remove the need for this parameter and simply let the SP handle the error handling 
> I vote for B even though it will break backwards compability, since if they were using the old way they would either have failed on every operation (if running on DB2) or having the code silently ignore any possible update/delete rowcount mismatches.

-- 
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: (HHH-1507) one-to-one can have formula or meta but not both of them.

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

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

    Fix Version: 3.2.0
     Resolution: Fixed
      Assign To: Steve Ebersole

> one-to-one can have formula or meta but not both of them.
> ---------------------------------------------------------
>
>          Key: HHH-1507
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1507
>      Project: Hibernate3
>         Type: Bug

>   Components: metamodel
>     Versions: 3.1.2
>     Reporter: Ivan Latysh
>     Assignee: Steve Ebersole
>     Priority: Minor
>      Fix For: 3.2.0
>  Attachments: patch.txt
>
>
> one-to-one defined as:
> <!ELEMENT one-to-one (meta*|formula*)>
> when should be:
> <!ELEMENT one-to-one (meta*,formula*)>

-- 
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-1847) QBE 'like' clause with backslashes don't work with MySQL

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

QBE 'like' clause with backslashes don't work with MySQL
--------------------------------------------------------

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

  Components: query-criteria  
    Versions: 3.2.0.cr2    
 Environment: 3.2.0.cr2, JBoss AS 4.0.4, MySQL 4.x or 5.x
    Reporter: Scott Marlow
 Attachments: Example-patch.txt, LikeExpression-patch.txt, QueryCacheTest-patch.txt

MySQL supports backslashes in the 'like' clause as a special escape character for expressing newline characters.  Many applications will want to disable this functionality in MySQL which can be done by specifying the escape character value as empty string or some other value.

MySQL support recommends that customers either double up their backslashes or use the escape clause to specify a different escape character value than backslash.

This patch adds a new method SetEscapeCharacter to org.hibernate.criterion.Example.  This is only used if the  'like' clause option is enabled.  Also added is org.hibernate.criterion.LikeExpression.  A new test case is added (for MySQL only) to org.hibernate.test.querycache.QueryCacheTest.

Example.setEscapeCharacter allows a value to be specfied that will be used as the new escape character for the like clause.

-- 
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-1564) Possible bug with deleting versioned object (patch included)

[Dave S. (JIRA) <no...@at...>]

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

Dave Syer commented on HHH-1564:
--------------------------------

I find that there is another spurious update of the parent object when it is first inserted (also causes the same potential constraint violation in the kind of trigger-driven situation originally outlined in this issue).  Thus:

Bar bar = new Bar(); // Bar is versioned
Foo foo = new Foo();
bar.getFoos().add(foo); // bar.foos are cascaded
session.save(bar);
session.flush();

results in:

INSERT INTO BAR ...
INSERT INTO FOO ...
UPDATE BAR ...

The UPDATE operation increments the version number of bar, but nothing else changes.

Hibernate only thinks that the Bar is dirty because its foos changed from a HashSet before the INSERT into a PersistentBag afterwards.  The java docs for PesistentBag is quite explicit that it doesn't follow the Collection API convention of making an item by item comparison in equals().  If it did, then the UPDATE wouldn't happen because the Bar would not be dirty.

Ironically, while the UPDATE is an issue for me because business users simply cannot see the logic in it, if it went away, an even bigger issue would be the fact the the INSERT statements come in the wrong order to make the audit trail show the Bar with the correct collection of Foos at the time it was created.  The Foos are only properly present in version 1 of bar.  But even worse, if the INSERTs happened the other way round, I might have a null constraint violation on inserting the Foo (it's parent Bar would not be persisted yet).  Maybe that is wrong, or could be addressed in another way?

> Possible bug with deleting versioned object (patch included)
> ------------------------------------------------------------
>
>          Key: HHH-1564
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1564
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.2
>  Environment: 3.1rc2
>     Reporter: N Clayton
>  Attachments: onetomanydelete_test.tar.gz
>
>
> We're seeing an odd problem when trying to delete a row. The code that does this simply creates a new object, commits it, starts a new session, finds the object, deletes it. It dies with a constraint violation on an audit table, because hibernate is issuing an unnecessary update operation (and not incrementing the version either). Further debugging shows that Hibernate thinks that three properties on the object are 'modified'. These three are collections. One is the points collection, one owners and the other is systems. Hibernate seems to think that they are 'different' because null != an empty collection. So, it thinks it needs to update the object.  However; later on - it doesn't increment the version number - because it knows the object is to be deleted. Thus - a problem. 
> A complete description is here:
> http://forum.hibernate.org/viewtopic.php?t=950225&highlight=collectiontype+isdirty
> This appears to be fixed if we change CollectionType.isDirty() to be:
>    public boolean isDirty(Object old, Object current, boolean[] checkable, SessionImplementor session)
>          throws HibernateException {
>         if(checkable.length == 0) {
>             // Assume not checkable
>             return false;
>         }
>       return isDirty(old, current, session);
>    } 

-- 
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: (HBX-672) hbm.xml HQL validation

[Max R. A. (JIRA) <no...@at...>]

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

Max Rydahl Andersen updated HBX-672:
------------------------------------

    Fix Version: 3.2beta6
                     (was: 3.1beta5a)

> hbm.xml HQL validation
> ----------------------
>
>          Key: HBX-672
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-672
>      Project: Hibernate Tools
>         Type: New Feature

>   Components: eclipse
>     Reporter: Max Rydahl Andersen
>      Fix For: 3.2beta6

>
>


-- 
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-1777) org.hibernate.QueryException: ClassNotFoundException: org.hibernate.hql.ast.HqlToken

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

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

Emmanuel Bernard commented on HHH-1777:
---------------------------------------

Prabhagar, your comment is the worst solution. Please guys check the migration guide

> org.hibernate.QueryException: ClassNotFoundException: org.hibernate.hql.ast.HqlToken 
> -------------------------------------------------------------------------------------
>
>          Key: HHH-1777
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1777
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.1.3
>  Environment: Hibernate 3.1.3,mysql-5.0.21-win32,mysql-connector-java-3.0.17-ga,jdk1.4.1_05,Struts 1.1,weblogic 8.1,MyEclipse 4.1.1GA
>     Reporter: Ranjit Patil
>  Attachments: AbstractBook.java, Book.hbm.xml, Book.java, BookListAction.java, BookListForm.class, HibernateSessionFactory.java, LibraryManager.java, hibernate.cfg.xml
>
>
> I have two tables book and customer. My index page has two links show book list and Show customer List.Currently I am working on only Book List. It calls BookListAction.java which in turn calls LibraryManager.java in which getAllBooks() has code something like this:
> public Book[] getAllBooks() {
> 		/* will hold the books we are going to return later */
> 		List books = new ArrayList();
> 		/* a Hibernate session */
> 		Session session = null;
> 		/* we always need a transaction */
> 		Transaction tx = null;
> 		/* get session of the current thread */
> 		session = HibernateSessionFactory.currentSession();
> 		tx = session.beginTransaction();
>                                          ----------Exception is thrown when the below line of code is executed---------------------
> 		List tmpBooks = session.createQuery(
> 				"select b from Book as b order by b.author, b.title").list();
>                                          -----------------------------------------------------------------------------------------------------------------
> 		for (Iterator iter = tmpBooks.iterator(); iter.hasNext();) {
> 			books.add((Book) iter.next());
> 		}
> 		tx.commit();
> 		return (Book[]) books.toArray(new Book[0]);
> 	}
> In eclipse it runs fine but when i deployed on weblogic i got following error when i clicked the show book list link:
> org.hibernate.QueryException: ClassNotFoundException: org.hibernate.hql.ast.HqlToken [select b from de.laliluna.library.Book as b order by b.author, b.title]
> 	at org.hibernate.hql.ast.HqlLexer.panic(HqlLexer.java:57)
> 	at antlr.CharScanner.setTokenObjectClass(CharScanner.java:287)
> 	at org.hibernate.hql.ast.HqlLexer.setTokenObjectClass(HqlLexer.java:31)
> 	at antlr.CharScanner.(CharScanner.java:42)
> 	at antlr.CharScanner.(CharScanner.java:51)
> 	at org.hibernate.hql.antlr.HqlBaseLexer.(HqlBaseLexer.java:56)
> 	at org.hibernate.hql.antlr.HqlBaseLexer.(HqlBaseLexer.java:53)
> 	at org.hibernate.hql.antlr.HqlBaseLexer.(HqlBaseLexer.java:50)
> 	at org.hibernate.hql.ast.HqlLexer.(HqlLexer.java:26)
> 	at org.hibernate.hql.ast.HqlParser.getInstance(HqlParser.java:44)
> 	at org.hibernate.hql.ast.QueryTranslatorImpl.parse(QueryTranslatorImpl.java:232)
> 	at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:155)
> 	at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:109)
> 	at org.hibernate.engine.query.HQLQueryPlan.(HQLQueryPlan.java:75)
> 	at org.hibernate.engine.query.HQLQueryPlan.(HQLQueryPlan.java:54)
> 	at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:71)
> 	at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133)
> 	at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112)
> 	at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1583)
> 	at de.laliluna.library.bl.LibraryManager.getAllBooks(LibraryManager.java:35)

-- 
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-1775) collection batch fetching

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

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

Christian Bauer updated HHH-1775:
---------------------------------

    Comment: was deleted

> collection batch fetching
> -------------------------
>
>          Key: HHH-1775
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1775
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Reporter: Steve Ebersole
>     Assignee: Steve Ebersole
>     Priority: Minor
>      Fix For: 3.2.0

>
>
> I have code local on my box to support "peeking" into the second level cache when determining whether to add a particular entity/collection key to a batch load request.  If the given key is contained in the second level cache, then do not batch fetch the entity/collection as it will be initialized from second level cache on access.
> However, there are still large inefficiencies when performing this for collections; the biggest of which currently is the fact that we retreive a IdentityMap.entrySet for each and ever call to determine a collectiomn fetch batch.  For performance reasons, we should align this with how entity batches are handled where the entity keys considered to be "batch loadable" are tracked seperately on the BatchFetchQueue.

-- 
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