[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-140) @IndexedEmbedded default depth is effectively 1 due to integer overflow
Franz Amador (JIRA)
noreply at atlassian.com
Mon Dec 10 12:46:59 EST 2007
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_29122 ]
Franz Amador commented on HSEARCH-140:
--------------------------------------
Glad to be able to help. Actually, I'm in no rush for a fix - there's a trivial workaround: just use @IndexedEmbedded(depth=100) or some large-enough number.
> @IndexedEmbedded default depth is effectively 1 due to integer overflow
> -----------------------------------------------------------------------
>
> Key: HSEARCH-140
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-140
> Project: Hibernate Search
> Issue Type: Bug
> Components: mapping
> Affects Versions: 3.0.0.GA
> Environment: Hibernate 3.2.5.ga
> Reporter: Franz Amador
> Assignee: Emmanuel Bernard
> Fix For: 3.0.1
>
>
> DocumentBuilder.java line 236 uses the expression "embeddedAnn.depth() + level", which overflows to a large negative number if "embeddedAnn.depth()" has its default value of Integer.MAX_VALUE and "level" is greater than zero. It then sets maxLevel to be that large negative number, which halts processing of any @IndexedEmbedded above level 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
More information about the hibernate-issues
mailing list