[
https://jira.jboss.org/jira/browse/JBSEAM-4474?page=com.atlassian.jira.pl...
]
Marek Novotny commented on JBSEAM-4474:
---------------------------------------
The solution will be in eliminating of usage this class. It can be replaced by standard
Java API, because there is possibility to use java.io.Reader instead of
java.io.InputStream in cases where Seam uses org.hibernate.lob.ReaderInputStream.
Hibernate class org.hibernate.lob.ReaderInputStream is now
org.hibernate.engine.jdbc.ReaderInputStream and that breaks Seam
---------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-4474
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4474
Project: Seam
Issue Type: Bug
Components: BPM
Affects Versions: 2.1.1.GA
Reporter: Scott Marlow
Assignee: Marek Novotny
Priority: Critical
Fix For: 2.2.1.CR1
Attachments: hibernate-core-JBSEAM-4474.jar
Jira JBAS-7440 is about a JBoss app server 6.0.0.M1 unit test failure. The failure is
showing that the Seam and Hibernate integration is broken. This problem occurred when we
upgraded AS (5_x branch) to the recent Hibernate 3.5.0-Beta-2.
Hibernate 3.5.0-Beta-2 contains a fix for HHH-2412 (Support for JDBC4), which involved
repackaging org.hibernate.lob.ReaderInputStream to now be
org.hibernate.engine.jdbc.ReaderInputStream. However, Seam has a dependency on the old
package name org.hibernate.lob.ReaderInputStream. This package name change results in an
app server integration test for Seam failure (error = java.lang.NoClassDefFoundError:
org/hibernate/lob/ReaderInputStream).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira