April 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-785) Jboss Har service from annotated class

by Michele Stoduto (JIRA)

Jboss Har service from annotated class --------------------------------------- Key: ANN-785 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-785 Project: Hibernate Annotations Issue Type: New Feature Reporter: Michele Stoduto Attachments: classi.zip Hi All, My problem: deploy har service from Annotated Classes. My Solution is based on org.hibernate.jmx.HibernateService and relative classes. In Attachment new classes for deploing jboss Har service from hibernate annotated classes. Please, can you add in standard release? Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5156) Add a Using JPA 2 XML mappings section in Core documentation

by Emmanuel Bernard (JIRA)

Add a Using JPA 2 XML mappings section in Core documentation ------------------------------------------------------------ Key: HHH-5156 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5156 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
10
0 / 0

[Hibernate-JIRA] Created: (HHH-4551) Query caching becomes very ineffective on conversations with extended sessions.

by Guenther Demetz (JIRA)

Query caching becomes very ineffective on conversations with extended sessions. ------------------------------------------------------------------------------- Key: HHH-4551 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4551 Project: Hibernate Core Issue Type: Improvement Components: caching (L2) Affects Versions: 3.3.2 Environment: 3.3.2 GA Reporter: Guenther Demetz Hibernate's query cache (hibernate.cache.use_query_cache) always takes the initial session timestamp for storing the result-set timestamp. --------------------------------------------- StandardQueryCache.java (put-method): ... Long ts = new Long( session.getTimestamp() ); ... cacheable.add( ts ); --------------------------------------------- When extending a session for a whole conversation (Book "Java Persistence with Hibernate" chapter. 11.2.3), the sessions initial timestamp get's soon rather deferred to the time a new query result set is produced actually. Immagine a long conversation which lasts more than 5 minutes. This leads to the effect, that often still valid result-set-cache entries are considered not up-to-date because of a flushed update action occured during the conversation. Furthermore the new obtained query-resultset (note that this query now considers the last update!) is subsequently again put in cache still with the original and outdated sessions-timestamp: That's for the birds ! Proposal: Why not take the current timestamp instead? For example calling: Long ts = new Long( cacheRegion.nextTimestamp()); best regards Guenther D. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2578) redesign SessionFactory building

by Steve Ebersole (JIRA)

redesign SessionFactory building -------------------------------- Key: HHH-2578 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2578 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Critical Fix For: cfg-rework Currently a SessionFactory is built by throwing a bunch of stuff into a Configuration object, stirring it, letting it come to a boil, and then pulling out the SessionFactory. In seriousness, there are a few problems with the way we currently operate within a Configuration and how we use it to build a SessionFactory: The general issue that there is no "lifecycle" to when various pieces of information will be available. This is an important omission in a number of ways: 1) consider schema generation. currently we cannot even know the dialect when a lot of db object names are being determined. this would be nice because it would allow us to transparently handle table/column names which are also keywords/reserved-words in the dialect, for example. 2) static-ness of types and the type-mappings. Because we currently have nothing to which to scope them. Ideally a type instance would be aware of the SessionFactory to which it is bound. Instead, what we have now is to change API methods quite a lot of the time to add in the SessionFactory as a passed parameter whenever it is discovered that it is needed. 3) also, most (all?) of the "static" configuration parameters in Hibernate are currently required to be so because of their use from within these static types; thus scoping types would allow us to also scope those config parameters (things like bytecode-provider, use of binary streams, etc). Ideally what I see happening is a scheme where users build a org.hibernate.cfg.Settings (or something similiar) instance themselves. Additionally they would apply metadata to a registry of some sort (lets call it MetadataRegistry for now). Then in order to build a SessionFactory, they would supply these two pieces of information (via ctor? via builder?). The important aspect though is that the information in MetadataRegistry would not be dealt with until that point in time, which would allow us to guarentee that resolving schema object names, types, etc would have access to the runtime Settings (and specifically the dialect) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
14
0 / 0

[Hibernate-JIRA] Created: (HHH-2931) Criteria.setMaxResults() filters children with fetch="join"

by Mattias Jiderhamn (JIRA)

Criteria.setMaxResults() filters children with fetch="join" ----------------------------------------------------------- Key: HHH-2931 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2931 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.5 Reporter: Mattias Jiderhamn Assume class Parent with a collection of children that is mapped with fetch="join", then use a Criteria to find a specific Parent using setMaxResults(1).uniqueResult(). The child collection of the returned Parent will only hold 1 element, despite how many actual matching rows the child table has in the databasen. In this case, the fetch="join" needs to be ignored, and a separate query needs to be issued to fetch the children. This issue may very well be related to HHH-2049. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3807) Adding a restriction to a many-to-one entity in Criteria query causes Join fetching

by Jonathan Gordon (JIRA)

Adding a restriction to a many-to-one entity in Criteria query causes Join fetching ----------------------------------------------------------------------------------- Key: HHH-3807 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3807 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.3.1 Environment: Hibernate 3.3.1GA Sql Server 2005 Reporter: Jonathan Gordon Priority: Minor When performing a criteria query that includes a restriction on a many-to-one entity, the associated entity is fetched eagerly, as if FetchMode were set to "JOIN". Explicitly setting the FetchMode to "SELECT" does not override this behavior. For instance, this criteria query: Criteria criteria = persistenceService.getCriteria(MailingParcel.class) .createAlias("mailingCampaign", "mc") .add(Restrictions.ge("mc.id", 1)) .setMaxResults(10); Yields the following sql: select top 10 this_.ID as ID17_1_, this_.KEYCODE as KEYCODE17_1_, this_.CAMPAIGN_ID as CAMPAIGN3_17_1_, this_.MAILING_LIST_MAILING_ID as MAILING4_17_1_, this_.COUNTRY_LE_ID as COUNTRY5_17_1_, this_.MATCH_ADDRESS as MATCH6_17_1_, this_.ADDRESS as ADDRESS17_1_, this_.MATCH_NAME as MATCH8_17_1_, this_.FIRST_NAME as FIRST9_17_1_, this_.LAST_NAME as LAST10_17_1_, this_.ZIP_CODE asZIP11_17_1_, this_.CITY as CITY17_1_, this_.STATE as STATE17_1_, this_.COMPANY as COMPANY17_1_, mc1_.ID as ID6_0_, mc1_.NOTE as NOTE6_0_, mc1_.NAME as NAME6_0_, mc1_.DATE_CREATED as DATE5_6_0_, mc1_.DATE_MODIFIED as DATE6_6_0_, mc1_.START_DATE as START7_6_0_, mc1_.SOURCE_FILE_NAME as SOURCE8_6_0_, mc1_.ORDINAL as ORDINAL6_0_, mc1_.KEYCODE_SUFFIX as KEYCODE10_6_0_, mc1_.MATCH_CATALOG_ID as MATCH11_6_0_, mc1_.ADDRESS_IMPORT_DATE as ADDRESS12_6_0_ from MATCH_MAILING_CAMPAIGN this_ inner join MATCH_CAMPAIGN_INFO mc1_ on this_.CAMPAIGN_ID=mc1_.ID where mc1_.ID>=1 However, removing the restriction yields the following sql: select top 10 this_.ID as ID17_0_, this_.KEYCODE as KEYCODE17_0_, this_.CAMPAIGN_ID as CAMPAIGN3_17_0_, this_.MAILING_LIST_MAILING_ID as MAILING4_17_0_, this_.COUNTRY_LE_ID as COUNTRY5_17_0_, this_.MATCH_ADDRESS as MATCH6_17_0_, this_.ADDRESS as ADDRESS17_0_, this_.MATCH_NAME as MATCH8_17_0_, this_.FIRST_NAME as FIRST9_17_0_, this_.LAST_NAME as LAST10_17_0_, this_.ZIP_CODE as ZIP11_17_0_, this_.CITY as CITY17_0_, this_.STATE as STATE17_0_, this_.COMPANY as COMPANY17_0_ from MATCH_MAILING_CAMPAIGN this_ Performing the original query in its HQL analog does not have this problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2544) Create the EntityPersisters in order based on Inheritance hierarchy

by Shawn Clowater (JIRA)

Create the EntityPersisters in order based on Inheritance hierarchy ------------------------------------------------------------------- Key: HHH-2544 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2544 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.3 Reporter: Shawn Clowater Priority: Minor I have a bit of what might seem to be an odd request. I had run into a scenario where filters on my mappings that were part of a Single Table hierarchy were not getting into the configuration and it turned out it was based on the order that the EntityPersisters were being created as we've doing some minor magic with Custom EntityPersisters for filters. In our case we have a filter template where the filter is pretty much the same for each class that implements it except for the table and key name used in the filter. So, rather than define this annotation everywhere (we had previously been using xdoclet to generate it for the hbm mappings) we pushed the logic into a Custom Persister. So, essentially as it is building the EntityPersister we intercept the PersistentClass before it calls the super() constructor and add our required filters on the PersistantClass (in its FilterMap) before it gets passed up. This is done like this because by the time it gets to the AbstractEntityPersister's constructor it uses the filterMap to construct the FilterHelper and then you're done as you have no access to change that after it is built. So, in the Inheritance case any subclasses that are built before the main root class will not have the filters that we inject during the construction of our Custom Entity Persisters. I have temporarily worked around it by changing the Subclasses getFilterMap() method to not only return the filters from the Parent class but also from the class itself. Now, normally you can't define the filter on the subclass but I can through the persister. What I'd like to do is: Make the persister class for the subclasses a 'standard' persister that doesn't add any filters to the subclass. Still have my root class' entity persister adding the filters. But have the Entity Persisters built in hierarchal order in the SessionFactoryImpl. Since they are being built in any given order right now, I can't see an issue with providing some order to them, something like the AnnotationBinder does. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4787) AuditProperty.isNull() doesn't generate "tab.col is null" SQL clause as expected

by Eric Citaire (JIRA)

AuditProperty.isNull() doesn't generate "tab.col is null" SQL clause as expected -------------------------------------------------------------------------------- Key: HHH-4787 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4787 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.0.GA Environment: Hibernate 3.3.0.GA, Envers 1.2.2, HSQLDB Database Reporter: Eric Citaire Priority: Critical AuditProperty.isNull() generate a SQL condition like this : "tab.col=?" where the bind variable is mapped to a null value. This doesn't work : most database engines will return false in every case. It should use the "is null" test instead : "tab.col is null" http://en.wikipedia.org/wiki/SQL#Null_and_Three-Valued_Logic_.283VL.29 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2579) scope bytecode provider selection to session factory

by Steve Ebersole (JIRA)

scope bytecode provider selection to session factory ---------------------------------------------------- Key: HHH-2579 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2579 Project: Hibernate3 Issue Type: Improvement Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: cfg-rework currently this is one of those "static" config params (classloader wide). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3574) ANY mapping ignores lazy="false"

by Manuel Dominguez Sarmiento (JIRA)

ANY mapping ignores lazy="false" -------------------------------- Key: HHH-3574 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3574 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Reporter: Manuel Dominguez Sarmiento We have a use case for eager fetching of an <any> association. The DTD accepts lazy="false|true", however at runtime it doesn't make any difference. Digging deeper, we see that org.hibernate.mapping.Any does not have a lazy property, furthermore, it does not extend Fetchable. This explains why it will not work as expected. There are two possible resolutions: 1) Implement eager fetching for <any> associations, unless there is some technical difficulty in doing so. Of course lazy fetching won't be possible using joins because of the nature of this type of associations, however it should be simple enough with a second select. This means that the XML config should handle lazy="false|true" but not fetch="join|select|subselect|etc" 2) Fix the DTD in case this can't be done to avoid confusion (less desirable). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2010