Bug 778010 (SOA-537) - Extend /jboss-as/tools/schema to support Sybase (tier2 database)
Summary: Extend /jboss-as/tools/schema to support Sybase (tier2 database)
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-537
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Tooling
Version: 4.2 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: FUTURE
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-30 17:49 UTC by Len DiMaggio
Modified: 2010-10-04 17:53 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-10-04 17:53:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778004 0 high CLOSED jBPM datasource should be XA datasource 2025-02-10 03:14:37 UTC
Red Hat Bugzilla 778373 0 high CLOSED jBPM datasource should be XA datasource 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-537 0 None None None Never

Internal Links: 778004 778373

Description Len DiMaggio 2008-04-30 17:49:08 UTC
Date of First Response: 2008-07-09 19:38:45
project_key: SOA

In order to support Sybase -  a tier2 database for 4.2.0 release - we'll need to extend the /jboss-as/tools/schema tool and add other server config files.

[ldimaggi@ldimaggi jboss-soa-p-standalone.4.2.0]$ find . -name "*sybase*" -print | grep -v doc
./jbpm-jpdl/db/jbpm.jpdl.sybase.sql
./jboss-as/server/default/deploy/jbossesb.sar/juddi-sql/sybase
./jboss-as/server/default/deploy/jbpm.esb/jbpm-sql/jbpm.jpdl.sybase.sql
./jboss-as/tools/schema/common/sybase-persistence-service.xml

In comparison - we have these files for MySQL:

[ldimaggi@ldimaggi jboss-soa-p-standalone.4.2.0]$ find . -name "*mysql*" -print | grep -v doc
./jbpm-jpdl/db/jbpm.jpdl.mysql.sql
./jboss-as/server/default/deploy/jbossesb.esb/message-store-sql/mysql
./jboss-as/server/default/deploy/jbossesb.sar/juddi-sql/mysql
./jboss-as/server/default/deploy/jbpm.esb/jbpm-sql/jbpm.jpdl.mysql.sql
./jboss-as/tools/schema/common/mysql-persistence-service.xml
./jboss-as/tools/schema/mysql
./jboss-as/tools/schema/mysql/template/mysql-ds.xml
./jboss-as/tools/schema/mysql/template/mysql-persistence-service.xml
./jboss-as/tools/schema/mysql/driver/mysql-connector-java-5.0.7-bin.jar

We will have to at least have sample files for each DB:

 -> <database>-ds.xml (needed for DB2, Sybase, MS-SQL)
 -> message-store-sql/<database>/create_database.sql, drop_database.sql (needed for DB2, Sybase, MS-SQL)
 -> <database>-persistence-service.xml (needed for DB2)

Comment 1 Len DiMaggio 2008-05-07 13:14:38 UTC
Changed JIRA type from feature request to bug - Sybase is tier2 supported DB.

Comment 2 Len DiMaggio 2008-05-07 13:25:38 UTC
Link: Added: This issue is related to SOA-531


Comment 3 Mike Brock 2008-07-09 23:38:45 UTC
Duplicate of SOA-541

Comment 4 Len DiMaggio 2008-08-26 16:52:25 UTC
SOA-537 refers to adding Sybase support

SOA-541 is the same, but for MS-SQL

Comment 5 nwallace 2008-09-25 19:39:54 UTC
Link: Added: This issue is related to SOA-856


Comment 6 nwallace 2008-10-01 11:30:44 UTC
Emailed Julian for comments

Comment 7 nwallace 2009-11-25 04:07:49 UTC
Uncommented the sybase15 in the schema tool and tested against helloworld and bpm_orchestration2 quickstarts ok.

Comment 8 Len DiMaggio 2010-02-08 17:26:00 UTC
Changed fixed in version to 'FUTURE' as Sybase is not yet supported by SOA-P.

Comment 9 Len DiMaggio 2010-10-04 17:53:40 UTC
Support is there in the 5.1 ER2 schema tool - for when the DB is certified - future.


Note You need to log in before you can comment on or make changes to this bug.