Hide Forgot
project_key: SOA On line 26 of index.jsp (see attached to SOA-2640) I'm getting: java.sql.SQLException: JZNNA: Column does not allow null values / see attached err.txt This is trying to obtain a Repository through the ServiceLoader. Perhaps DDL needs to be tuned?
Attachment: Added: err.txt
Attachment: Added: modeshape-config.xml
Link: Added: This issue Cloned to SOA-2643
This is still an issue with ER5.
There's a problem with the Sybase jdbc4 driver (jconn4.jar), in that it has issues setting "NULL" for BIT data types used to represent boolean values. A recommended solution is to go back to the jconn3 driver. However, that driver has blob / clob issues and these issues we're not fixed until the 3.5.0 release (which we use 3.3.2). Another suggestion was to use this workaround in the mapping: change: type="boolean" to use: type="org.hibernate.test.where.NumericTrueFalseType" I don't know if we want to change the product branch before the project has had this type of change applied. This needs some serious discussion.
When I referenced the fix in 3.5.0, I should have clarified that the blob/clob issue was a Hibernate issue (as indicated in MODE-1037).
As I mentioned on MODE-1037, in order to support running on EAP 5.1, we had to change ModeShape to use an older version of Hibernate. I was told that if any Hibernate issues came up (especially if they were fixed in later releases of Hibernate), that they'd be backported to the version of Hibernate that EAP, SOA-P and BRMS are using. IMO, this is what has to happen here.
It must be considered by the PM team whether we should drop jdbc4 driver support. As far as I understand though going to NumericTrueFalseType would fix the jdbc4 problem. And the backport of hibernate patches would fix the jdbc3 problem. In any case PM need to be involved.
Link: Added: This issue related BRMS-507
Assigning to Ken to get PM team answer.
Link: Added: This issue is a dependency of JBPAPP-5558
This is the jira requesting the Hibernate fix to EAP.
Further review has proven that this is not a blocker for SOA 5.1.0. It will be a candidate for SOA 5.1.0
Link: Added: This issue duplicates SOA-2706
Randall Hauch <rhauch> updated the status of jira MODE-1037 to Closed