[hibernate-issues] [Hibernate-JIRA] Closed: (HBX-95) create a hbmlint
Max Rydahl Andersen (JIRA)
noreply at atlassian.com
Thu Oct 12 13:31:24 EDT 2006
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-95?page=all ]
Max Rydahl Andersen closed HBX-95:
----------------------------------
Fix Version: 3.2beta9
(was: 3.2LATER)
Resolution: Fixed
<hibernatetool>
<...configuration/>
<hbmlint/>
</hibernatetool>
hbmlint-result.txt:
CACHE_COLLECTION_NONCACHABLE_TARGET:Entity 'org.hibernate.tool.hbmlint.Category' is referenced from the cache-enabled collection 'org.hibernate.tool.hbmlint.Category.childCategories' without the entity being cachable
LAZY_NOT_INSTRUMENTED:'org.hibernate.tool.hbmlint.BrokenNonLazy' has lazy='false', but its class 'org.hibernate.tool.hbmlint.BrokenNonLazy' has not been instrumented with cglib
LAZY_NO_DEFAULT_CONSTRUCTOR:lazy='true' set for 'org.hibernate.tool.hbmlint.BrokenLazy', but class has no default constructor.
ID_SHADOWED:org.hibernate.tool.hbmlint.IdentifierProblem has a normal property named 'id'. This can cause issues since HQL queries will always interpret 'id' as the identifier and not the concrete property
SCHEMA_TABLE_MISSING:Missing table BrokenLazy
SCHEMA_TABLE_MISSING:Missing table BrokenNonLazy
SCHEMA_TABLE_MISSING:Missing table Category
SCHEMA_TABLE_MISSING:Missing table FakeNonLazy
SCHEMA_TABLE_MISSING:Missing table IdentifierProblem
SCHEMA_TABLE_MISSING:Missing table NoTable
SCHEMA_COLUMN_TYPE_MISMATCH:BadType has a wrong column type for name, expected: CLOB but was VARCHAR in db
SCHEMA_COLUMN_MISSING:Category is missing column: name
SCHEMA_TABLE_MISSING:Missing table MissingTable
MISSING_ID_GENERATOR:Missing sequence or table: hibernate_unique_key
This is the first cut so the output is just a raw dump of the issues found - should be beefed up and with links to an explanation of the problem found instead of repeating it always etc.
> create a hbmlint
> ----------------
>
> Key: HBX-95
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-95
> Project: Hibernate Tools
> Type: New Feature
> Reporter: Max Rydahl Andersen
> Fix For: 3.2beta9
>
>
> We should create a hbmlint that checks if once hibernate configuration and mapping is correct/suited for production.
> Main function would be to check if the hibernate mappings corresponds to what is in the database (does table, column, foreignkey etc. match)
> Secondary could be to check that dialect matches database, no use of hibernate development only connectionpool, deep inheritance hiearchies etc.
--
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