[Hibernate-JIRA] Created: (HHH-7145) There is a typo/syntax error in the first example under 2.2.2.3. Embedded objects (aka components)
by Tracy Logan (JIRA)
There is a typo/syntax error in the first example under 2.2.2.3. Embedded objects (aka components)
--------------------------------------------------------------------------------------------------
Key: HHH-7145
URL: https://hibernate.onjira.com/browse/HHH-7145
Project: Hibernate ORM
Issue Type: Improvement
Components: documentation
Environment: 3.1 beta 9
Reporter: Tracy Logan
Priority: Trivial
The example given under section 2.2.2.3. Embedded objects (aka components) contains the following:
{code:java}
@AttributeOverrides( {
@AttributeOverride(name="iso2", column = @Column(name="bornIso2") ),
@AttributeOverride(name="name", column = @Column(name="bornCountryName") )
} )
{code}
However, @AttributeOverrides actually takes an array, so the correct syntax changes the curly braces to square brackets:
{code:java}
@AttributeOverrides( [
@AttributeOverride(name="iso2", column = @Column(name="bornIso2") ),
@AttributeOverride(name="name", column = @Column(name="bornCountryName") )
] )
{code}
This is of course a trivial (though helpful!) fix; I plan to use it to gain experience contributing, and will edit this ticket to add a patch (or pull request?) shortly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[Hibernate-JIRA] Created: (HHH-7194) NullPointerExeption with nested subqueries using Criteria API
by Shawn Clowater (JIRA)
NullPointerExeption with nested subqueries using Criteria API
-------------------------------------------------------------
Key: HHH-7194
URL: https://hibernate.onjira.com/browse/HHH-7194
Project: Hibernate ORM
Issue Type: Bug
Components: query-criteria
Affects Versions: 4.1.1
Environment: N/A
Reporter: Shawn Clowater
It appears a regression was introduced under HHH-3646
Under that change the CriteriaQueryTranslator was changed to track the root entity names in CriteriaInfoProvider objects vs plain Strings. The old functionality would allow for returning a null out of the map and then handling an entity not found exception that was thrown further down the stack and then it would try to find the root entity name from the outer criteria. Now, it blows the NPE on the getName() call and prevents the query from executing.
I've got a working fix for it but I still need to put together a test for the change, I'll create a pull request in the next day or so with the fix.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[Hibernate-JIRA] Created: (HSEARCH-1075) FSSlaveDirectoryProvider JMS configuration documentation is incomplete
by Eli Colner (JIRA)
FSSlaveDirectoryProvider JMS configuration documentation is incomplete
----------------------------------------------------------------------
Key: HSEARCH-1075
URL: https://hibernate.onjira.com/browse/HSEARCH-1075
Project: Hibernate Search
Issue Type: Improvement
Components: documentation
Affects Versions: 4.0.0.Final
Environment: all
Reporter: Eli Colner
Priority: Minor
The documentation for 'hibernate.search.default.refresh' property states that "The refresh period should be higher that the expected copy time." which is misleading imo. It should read "The refresh period represents the least amount of time that slaves will be out of sync with the master. It is recommended that the refresh period be higher than the expected copy time, however if the value becomes insufficient then the default implementation of FSSlaveDirectoryProvider will prevent multiple copies from occurring simultaneously using a mutex lock. It's safe to set this value low anticipating that as your index grows the lock will be used appropriately."
Based on the code, I believe the default value to be very high... but that's a separate issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years