| Summary: | ModeShape needs to support Sybase as a repository | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Aleksandar Kostadinov <akostadinov> | ||||||
| Component: | EAP, EDS | Assignee: | Van Halbert <vhalbert> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 5.1.0.ER4, 5.1.0.ER5 | CC: | akostadinov, rhauch, vhalbert | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | FUTURE | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-2642 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: |
linux, sybase 15.x, jdbc4 driver, repository database schema created through the supplied modeshape DDL script
|
|||||||
| Last Closed: | 2011-12-06 22:01:38 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 899318 | ||||||||
| Attachments: |
|
||||||||
|
Description
Aleksandar Kostadinov
2010-12-03 17:39:28 UTC
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 |