Move the discovery of constraint types into the constructor of ConstraintTree
-----------------------------------------------------------------------------
Key: HV-338
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-338
Project: Hibernate Validator
Issue Type: Improvement
Components: engine
Affects Versions: 4.1.0.CR1
Reporter: Hardy Ferentschik
Assignee: Hardy Ferentschik
Fix For: 4.1.0.Final
Currently {{ValidatorTypeHelper.getValidatorsTypes}} is called for each call to {{ConstraintTree.findMatchingValidatorClass}}, however it can be done only once in the constructor.
--
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
Don't include the title of the example when referencing it in within a paragraph
--------------------------------------------------------------------------------
Key: STYLE-2
URL: http://opensource.atlassian.com/projects/hibernate/browse/STYLE-2
Project: Hibernate jDocBook Style
Issue Type: Task
Components: xslt
Affects Versions: 2.0.x
Reporter: Hardy Ferentschik
Assignee: Steve Ebersole
Fix For: 2.0.x
At the moment inserting a _xref_ to an _example_ creates something like this:
{quote}
Notice how in Example 6.4, "this is the full title of the example" this and such
{quote}
For readability I think it would be better to have:
{quote}
Notice how in Example 6.4 this and such
{quote}
Maybe the format type could even be controlled by a parameters, since sometimes the long format is useful as well, for example when you are referencing another chapter or section.
--
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
Code issue - NPE
----------------
Key: HHH-5327
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5327
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.3
Environment: any
Reporter: Fred Toussi
package org.hibernate.tuple.component
class AbstractComponentTuplizer
public void setPropertyValues(Object component, Object[] values) throws HibernateException {
for ( int i = 0; i < propertySpan; i++ ) {
setters[i].set( component, values[i], null );
}
}
The null "factory" argument is used via Dom4jAccessor$ElementSetter() and eventually dereferenced, causing NPE.
Issue shows up in:
[org.hibernate.test.entitymode.dom4j.component.Dom4jComponentTest#testSetAccessorsFailureExpected]
--
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
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4240?page=c... ]
Greg Burcher commented on HHH-4240:
-----------------------------------
Is there still no fix to enable using @SecondaryTable together with InheritanceType.JOINED with subclasses? The work-around of defining another first-class entity with @OneToOne association for the joined table is not desirable for me. Thanks.
> SecondaryTables not recognized when using JOINED inheritance
> ------------------------------------------------------------
>
> Key: HHH-4240
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4240
> Project: Hibernate Core
> Issue Type: Bug
> Components: annotations
> Environment: Hibernate 3.2.0CR1; db is irrelevant, as the buildSessionFactory() fails.
> Reporter: Sebastian Kirsch
> Attachments: TestSecondaries.java, TestSecondaries.java, TestSecondaries.java
>
>
> The Configuration doesn't recognize secondary tables of a super class.
> Calling AnnotationConfiguration.buildSessionFactory fails, claiming that the secondary table used in the super class cannot be found in the subclass.
> Adding the secondary table to the subclass doesn't help either.
> See attached JUnit test case.
--
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
Support not-found="ignore" for <any> mappings
---------------------------------------------
Key: HHH-3475
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3475
Project: Hibernate Core
Issue Type: Improvement
Components: core
Affects Versions: 3.3.0.SP1
Reporter: Felix Gnass
Priority: Minor
It would be useful if the <any> element would support the not-found="ignore|exception" setting. Due to the nature of any-mappings it's impossible to use on-delete cascades at the database layer, so it's very likely that ObjectNotFoundExceptions occur.
Currently the only work-around to gracefully handle such situations seems to be the implementation of a custom EntityNotFoundDelegate that doesn't throw an exception.
--
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
Stop hibernate-validator-legacy to be deployed in the maven repo
----------------------------------------------------------------
Key: HV-334
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-334
Project: Hibernate Validator
Issue Type: Task
Components: build
Affects Versions: 4.1.0.CR1
Reporter: Hardy Ferentschik
Assignee: Hardy Ferentschik
Fix For: 4.1.0.Final, 4.2.0
Currently on each deploy we also deploy hibernate-validator-legacy. Given that there is not active development we should disable deployment of this jar into the maven repo. Question is whether to do it pre or post 4.1
--
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