[JBoss JIRA] (TEIID-3032) Database Logging: Problems with Microsoft
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3032?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3032:
-------------------------------------
May be we could simply rename the field to "QueryPlan" to avoid issues.
> Database Logging: Problems with Microsoft
> -----------------------------------------
>
> Key: TEIID-3032
> URL: https://issues.jboss.org/browse/TEIID-3032
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.7.1
> Reporter: Van Halbert
>
> Installed the teiid extension: database logging, and seeing the following errors:
> 14:46:55,588 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB Logging.1 model "LoggingData" metadata failed to load. Reason:TEIID60013 Duplicate Table check_constraints
> 14:46:55,844 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000227: Running hbm2ddl schema export
> 14:46:56,119 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: drop table auditlog
> 14:46:56,120 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Cannot drop the table 'auditlog', because it does not exist or you do not have permission.
> 14:46:56,343 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: drop table commandlog
> 14:46:56,343 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Cannot drop the table 'commandlog', because it does not exist or you do not have permission.
> 14:46:56,857 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: create table commandlog (id bigint identity not null, applicationname varchar(255), executionid varchar(50), modelname varchar(255), plan varbinary(MAX), principal varchar(50), requestid varchar(50), rowcount int, sessionid varchar(50), sourcecommand bit, sourcerequestid bigint, sqlcmd varchar(MAX), eventtype varchar(10), logtime datetime2, transactionid varchar(100), translatorname varchar(50), vdbname varchar(255), vdbversion int, primary key (id))
> 14:46:56,858 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Incorrect syntax near the keyword 'plan'.
> 14:46:56,858 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000230: Schema export complete
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3030) Update Saxon to current release (9.5.x)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3030?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3030:
---------------------------------------
You mean the saxon upgrade? That will be 8.9 at the earliest.
> Update Saxon to current release (9.5.x)
> ---------------------------------------
>
> Key: TEIID-3030
> URL: https://issues.jboss.org/browse/TEIID-3030
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 8.7
> Environment: Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T09:51:42-04:00)
> Maven home: C:\Java\apache-maven-3.2.2
> Java version: 1.7.0_60, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_60\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary Gregory
> Assignee: Steven Hawkins
>
> Our product embeds a Teiid server and provides its own set of 3rd party jar files, one of which clashes with Teiid: we provide Saxon-HE 9.4.0.6 and Teiid provides 9.2.1.5. These two versions are NOT binary compatible.
> This shows up using the web services connector as a class not found error because some classes have been repackaged between Saxon 9.2.x and 9.4.x.
> If Teiid updates to the latest version (9.5), so can we, and avoid backporting our Saxon dependencies.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3032) Database Logging: Problems with Microsoft
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3032?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3032:
---------------------------------------
The ERRORs related to the drops seem to be erroneously reported as you'd expect them to fail if the tables don't exist. The unsuccessful create is due to plan being a reserved word for SQL Server. Ideally hibernate would know this and quote it, but we should be able to do that manually as well.
> Database Logging: Problems with Microsoft
> -----------------------------------------
>
> Key: TEIID-3032
> URL: https://issues.jboss.org/browse/TEIID-3032
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.7.1
> Reporter: Van Halbert
>
> Installed the teiid extension: database logging, and seeing the following errors:
> 14:46:55,588 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB Logging.1 model "LoggingData" metadata failed to load. Reason:TEIID60013 Duplicate Table check_constraints
> 14:46:55,844 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000227: Running hbm2ddl schema export
> 14:46:56,119 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: drop table auditlog
> 14:46:56,120 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Cannot drop the table 'auditlog', because it does not exist or you do not have permission.
> 14:46:56,343 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: drop table commandlog
> 14:46:56,343 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Cannot drop the table 'commandlog', because it does not exist or you do not have permission.
> 14:46:56,857 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: create table commandlog (id bigint identity not null, applicationname varchar(255), executionid varchar(50), modelname varchar(255), plan varbinary(MAX), principal varchar(50), requestid varchar(50), rowcount int, sessionid varchar(50), sourcecommand bit, sourcerequestid bigint, sqlcmd varchar(MAX), eventtype varchar(10), logtime datetime2, transactionid varchar(100), translatorname varchar(50), vdbname varchar(255), vdbversion int, primary key (id))
> 14:46:56,858 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Incorrect syntax near the keyword 'plan'.
> 14:46:56,858 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000230: Schema export complete
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3032) Database Logging: Problems with Microsoft
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3032?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3032:
----------------------------------
Assignee: (was: Steven Hawkins)
> Database Logging: Problems with Microsoft
> -----------------------------------------
>
> Key: TEIID-3032
> URL: https://issues.jboss.org/browse/TEIID-3032
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.7.1
> Reporter: Van Halbert
>
> Installed the teiid extension: database logging, and seeing the following errors:
> 14:46:55,588 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB Logging.1 model "LoggingData" metadata failed to load. Reason:TEIID60013 Duplicate Table check_constraints
> 14:46:55,844 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000227: Running hbm2ddl schema export
> 14:46:56,119 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: drop table auditlog
> 14:46:56,120 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Cannot drop the table 'auditlog', because it does not exist or you do not have permission.
> 14:46:56,343 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: drop table commandlog
> 14:46:56,343 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Cannot drop the table 'commandlog', because it does not exist or you do not have permission.
> 14:46:56,857 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: create table commandlog (id bigint identity not null, applicationname varchar(255), executionid varchar(50), modelname varchar(255), plan varbinary(MAX), principal varchar(50), requestid varchar(50), rowcount int, sessionid varchar(50), sourcecommand bit, sourcerequestid bigint, sqlcmd varchar(MAX), eventtype varchar(10), logtime datetime2, transactionid varchar(100), translatorname varchar(50), vdbname varchar(255), vdbversion int, primary key (id))
> 14:46:56,858 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Incorrect syntax near the keyword 'plan'.
> 14:46:56,858 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000230: Schema export complete
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3031) Database Logging: Problems with Oracle
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3031?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3031:
----------------------------------
Assignee: (was: Steven Hawkins)
> Database Logging: Problems with Oracle
> --------------------------------------
>
> Key: TEIID-3031
> URL: https://issues.jboss.org/browse/TEIID-3031
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.7.1
> Reporter: Van Halbert
>
> Installed the teiid extension: database logging to use oracle, and get the following exception at startup:
> Unable to build EntityManagerFactory
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:103)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1]
> Caused by: javax.persistence.PersistenceException: [PersistenceUnit: teiid-logger] Unable to build EntityManagerFactory
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:924)
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899)
> at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:76)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:200)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$600(PersistenceUnitServiceImpl.java:57)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:99)
> ... 4 more
> Caused by: org.hibernate.MappingException: org.hibernate.dialect.Oracle10gDialect does not support identity key generation
> at org.hibernate.dialect.Dialect.getIdentityColumnString(Dialect.java:772)
> at org.hibernate.dialect.Dialect.getIdentityColumnString(Dialect.java:762)
> at org.hibernate.mapping.Table.sqlCreateString(Table.java:505)
> at org.hibernate.cfg.Configuration.generateSchemaCreationScript(Configuration.java:1038)
> at org.hibernate.tool.hbm2ddl.SchemaExport.<init>(SchemaExport.java:125)
> at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:504)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1797)
> at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:96)
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:914)
> ... 9 more
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3031) Database Logging: Problems with Oracle
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3031?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3031:
-------------------------------------
try solution mentioned here https://community.jboss.org/thread/188775 see if that fixes the issue
> Database Logging: Problems with Oracle
> --------------------------------------
>
> Key: TEIID-3031
> URL: https://issues.jboss.org/browse/TEIID-3031
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Installed the teiid extension: database logging to use oracle, and get the following exception at startup:
> Unable to build EntityManagerFactory
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:103)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1]
> Caused by: javax.persistence.PersistenceException: [PersistenceUnit: teiid-logger] Unable to build EntityManagerFactory
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:924)
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899)
> at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:76)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:200)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$600(PersistenceUnitServiceImpl.java:57)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:99)
> ... 4 more
> Caused by: org.hibernate.MappingException: org.hibernate.dialect.Oracle10gDialect does not support identity key generation
> at org.hibernate.dialect.Dialect.getIdentityColumnString(Dialect.java:772)
> at org.hibernate.dialect.Dialect.getIdentityColumnString(Dialect.java:762)
> at org.hibernate.mapping.Table.sqlCreateString(Table.java:505)
> at org.hibernate.cfg.Configuration.generateSchemaCreationScript(Configuration.java:1038)
> at org.hibernate.tool.hbm2ddl.SchemaExport.<init>(SchemaExport.java:125)
> at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:504)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1797)
> at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:96)
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:914)
> ... 9 more
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3032) Database Logging: Problems with Microsoft
by Van Halbert (JIRA)
Van Halbert created TEIID-3032:
----------------------------------
Summary: Database Logging: Problems with Microsoft
Key: TEIID-3032
URL: https://issues.jboss.org/browse/TEIID-3032
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 8.7.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Installed the teiid extension: database logging, and seeing the following errors:
14:46:55,588 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB Logging.1 model "LoggingData" metadata failed to load. Reason:TEIID60013 Duplicate Table check_constraints
14:46:55,844 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000227: Running hbm2ddl schema export
14:46:56,119 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: drop table auditlog
14:46:56,120 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Cannot drop the table 'auditlog', because it does not exist or you do not have permission.
14:46:56,343 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: drop table commandlog
14:46:56,343 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Cannot drop the table 'commandlog', because it does not exist or you do not have permission.
14:46:56,857 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: create table commandlog (id bigint identity not null, applicationname varchar(255), executionid varchar(50), modelname varchar(255), plan varbinary(MAX), principal varchar(50), requestid varchar(50), rowcount int, sessionid varchar(50), sourcecommand bit, sourcerequestid bigint, sqlcmd varchar(MAX), eventtype varchar(10), logtime datetime2, transactionid varchar(100), translatorname varchar(50), vdbname varchar(255), vdbversion int, primary key (id))
14:46:56,858 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Incorrect syntax near the keyword 'plan'.
14:46:56,858 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000230: Schema export complete
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3031) Database Logging: Problems with Oracle
by Van Halbert (JIRA)
Van Halbert created TEIID-3031:
----------------------------------
Summary: Database Logging: Problems with Oracle
Key: TEIID-3031
URL: https://issues.jboss.org/browse/TEIID-3031
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 8.7.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Installed the teiid extension: database logging to use oracle, and get the following exception at startup:
Unable to build EntityManagerFactory
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:103)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1]
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: teiid-logger] Unable to build EntityManagerFactory
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:924)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:76)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:200)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$600(PersistenceUnitServiceImpl.java:57)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:99)
... 4 more
Caused by: org.hibernate.MappingException: org.hibernate.dialect.Oracle10gDialect does not support identity key generation
at org.hibernate.dialect.Dialect.getIdentityColumnString(Dialect.java:772)
at org.hibernate.dialect.Dialect.getIdentityColumnString(Dialect.java:762)
at org.hibernate.mapping.Table.sqlCreateString(Table.java:505)
at org.hibernate.cfg.Configuration.generateSchemaCreationScript(Configuration.java:1038)
at org.hibernate.tool.hbm2ddl.SchemaExport.<init>(SchemaExport.java:125)
at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:504)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1797)
at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:96)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:914)
... 9 more
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3030) Update Saxon to current release (9.5.x)
by Gary Gregory (JIRA)
[ https://issues.jboss.org/browse/TEIID-3030?page=com.atlassian.jira.plugin... ]
Gary Gregory commented on TEIID-3030:
-------------------------------------
What about Teiid? When would this change make it on the road map? Which version?
> Update Saxon to current release (9.5.x)
> ---------------------------------------
>
> Key: TEIID-3030
> URL: https://issues.jboss.org/browse/TEIID-3030
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 8.7
> Environment: Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T09:51:42-04:00)
> Maven home: C:\Java\apache-maven-3.2.2
> Java version: 1.7.0_60, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_60\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary Gregory
> Assignee: Steven Hawkins
>
> Our product embeds a Teiid server and provides its own set of 3rd party jar files, one of which clashes with Teiid: we provide Saxon-HE 9.4.0.6 and Teiid provides 9.2.1.5. These two versions are NOT binary compatible.
> This shows up using the web services connector as a class not found error because some classes have been repackaged between Saxon 9.2.x and 9.4.x.
> If Teiid updates to the latest version (9.5), so can we, and avoid backporting our Saxon dependencies.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3030) Update Saxon to current release (9.5.x)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3030?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3030:
---------------------------------------
This is a non-trivial update as the saxon apis changed in both 9.3 and 9.4. At least there doesn't seem to be much different from there.
Is it possible that you could use isolated classloaders to prevent the saxon conflict. Moving forward you're likely to run into this again.
> Update Saxon to current release (9.5.x)
> ---------------------------------------
>
> Key: TEIID-3030
> URL: https://issues.jboss.org/browse/TEIID-3030
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 8.7
> Environment: Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T09:51:42-04:00)
> Maven home: C:\Java\apache-maven-3.2.2
> Java version: 1.7.0_60, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_60\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary Gregory
> Assignee: Steven Hawkins
>
> Our product embeds a Teiid server and provides its own set of 3rd party jar files, one of which clashes with Teiid: we provide Saxon-HE 9.4.0.6 and Teiid provides 9.2.1.5. These two versions are NOT binary compatible.
> This shows up using the web services connector as a class not found error because some classes have been repackaged between Saxon 9.2.x and 9.4.x.
> If Teiid updates to the latest version (9.5), so can we, and avoid backporting our Saxon dependencies.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months