[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5541) Change from class to interface leads to IncompatibleClassChangeError (org.hibernate.stat.EntityStatistics and co.)
Cédrik LIME (JIRA)
noreply at atlassian.com
Thu Sep 9 03:26:19 EDT 2010
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38334#action_38334 ]
Cédrik LIME commented on HHH-5541:
----------------------------------
Steve,
This is exactly what I do: distribute a binary jar that displays Hibernate Statistics, as part of my open-source monitoring utility [MessAdmin|http://messadmin.sourceforge.net] (shameless plug ;-)), and I don't want my users to have to recompile anything.
This bug report was mainly aimed at documentation; there is not much we can do in Hibernate to fix it. I will probably resort to reflection to make it work everywhere.
I guess we can close this bug now that it has been written for posterity.
> Change from class to interface leads to IncompatibleClassChangeError (org.hibernate.stat.EntityStatistics and co.)
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HHH-5541
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5541
> Project: Hibernate Core
> Issue Type: Bug
> Components: core
> Affects Versions: 3.5.0-Final, 3.6.0.Beta1
> Reporter: Cédrik LIME
>
> Hibernate 3.5.0 introduced a concurrent implementation for Statistics. Thus the classes of {{org.hibernate.stat.*}} became interfaces and lo and behold! a Java 5 concurrent implementation was born, and all rejoiced at this marvel.
> But in the land of compiled binaries, some said that a {{java.lang.IncompatibleClassChangeError}} would rear its ugly head since where a Class was expected an Interface would appear, and so the current thread would stop its processing with an Error.
> And it was said in the kingdom of Hibernate that documentation was forthcoming that everyone should re-compile their dependant 3rd-party libraries, whether one could access the 3rd-party sources or not.
> In an ironic twist, now that Hibernate 3.6 depends on Java 5, we still have the non-concurrent implementation lying around unused...
> All prose apart, this bug means I can not distribute a {{.jar}} that is compiled against Hibernate 3.1 and that works for all released Hibernate versions. I don't want impose my users the hassle to re-compile (even if I provide the source code), but I guess this 3.5.0 change leaves me no choice... This should at least be clearly documented.
--
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