July 2014 - teiid-issues - Jboss List Archives

[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: --------------------------------------- > That does not seem to be the case since the Saxon-HE jar is delivered with the embedded zip. Embedded is simply a different kitting of the server version which does pull in additional dependencies. However I was mistaken we do currently pull in our own saxon version even in the server kit, so this is something that we can take on more easily. > 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

1
0
0 / 0

[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 updated TEIID-3030: -------------------------------- Summary: Update Saxon to current release (9.5.x) (was: Update Saxon to current release (9.5)) > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-3030) Update Saxon to current release (9.5)

by Gary Gregory (JIRA)

[ https://issues.jboss.org/browse/TEIID-3030?page=com.atlassian.jira.plugin... ] Gary Gregory commented on TEIID-3030: ------------------------------------- In Teiid, replacing 9.2.1.5 with 9.5.1-6 is does not just require reorganizing the imports. The Saxon Axis contants are now in an enum. Replacing replacing 9.2.1.5 with 9.4.0.7, cause other, different compilation problems. Replacing replacing 9.2.1.5 with 9.4, cause other, different compilation problems. 9.4 is the oldest version of "Saxon-HE" in Maven Central. > Update Saxon to current release (9.5) > ------------------------------------- > > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-3030) Update Saxon to current release (9.5)

by Gary Gregory (JIRA)

[ https://issues.jboss.org/browse/TEIID-3030?page=com.atlassian.jira.plugin... ] Gary Gregory edited comment on TEIID-3030 at 7/11/14 1:36 PM: -------------------------------------------------------------- In Teiid, replacing 9.2.1.5 with 9.5.1-6 is does not just require reorganizing the imports. The Saxon Axis contants are now in an enum. Replacing replacing 9.2.1.5 with 9.4.0.7, cause other, different compilation problems. Replacing replacing 9.2.1.5 with 9.4, cause other, different compilation problems. 9.4 is the oldest version of "Saxon-HE" in Maven Central. What is the next step? was (Author: gary.gregory): In Teiid, replacing 9.2.1.5 with 9.5.1-6 is does not just require reorganizing the imports. The Saxon Axis contants are now in an enum. Replacing replacing 9.2.1.5 with 9.4.0.7, cause other, different compilation problems. Replacing replacing 9.2.1.5 with 9.4, cause other, different compilation problems. 9.4 is the oldest version of "Saxon-HE" in Maven Central. > Update Saxon to current release (9.5) > ------------------------------------- > > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2854) bounded-queue-thread-pool silently drops tasks after the queue length is exceeded

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2854?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-2854. -------------------------------- Resolution: Done > bounded-queue-thread-pool silently drops tasks after the queue length is exceeded > --------------------------------------------------------------------------------- > > Key: TEIID-2854 > URL: https://issues.jboss.org/browse/TEIID-2854 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.5 > Environment: JBoss EAP 6.1.0 Alpha and Teiid 8.5 > Reporter: Rakesh Balguri > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.3, 8.7 > > > The bounded-queue-thread-pool apparently needs a handoff executor configured otherwise it silently drops tasks after the queue length is exceeded. > See the discussion for more information. > https://community.jboss.org/thread/236744 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2854) bounded-queue-thread-pool silently drops tasks after the queue length is exceeded

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2854?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2854: --------------------------------- Fix Version/s: 8.4.3 > bounded-queue-thread-pool silently drops tasks after the queue length is exceeded > --------------------------------------------------------------------------------- > > Key: TEIID-2854 > URL: https://issues.jboss.org/browse/TEIID-2854 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.5 > Environment: JBoss EAP 6.1.0 Alpha and Teiid 8.5 > Reporter: Rakesh Balguri > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7, 8.4.3 > > > The bounded-queue-thread-pool apparently needs a handoff executor configured otherwise it silently drops tasks after the queue length is exceeded. > See the discussion for more information. > https://community.jboss.org/thread/236744 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2854) bounded-queue-thread-pool silently drops tasks after the queue length is exceeded

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2854?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-2854: ---------------------------------- re-open for fix version > bounded-queue-thread-pool silently drops tasks after the queue length is exceeded > --------------------------------------------------------------------------------- > > Key: TEIID-2854 > URL: https://issues.jboss.org/browse/TEIID-2854 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.5 > Environment: JBoss EAP 6.1.0 Alpha and Teiid 8.5 > Reporter: Rakesh Balguri > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7 > > > The bounded-queue-thread-pool apparently needs a handoff executor configured otherwise it silently drops tasks after the queue length is exceeded. > See the discussion for more information. > https://community.jboss.org/thread/236744 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3030) Update Saxon to current release (9.5)

by Gary Gregory (JIRA)

[ https://issues.jboss.org/browse/TEIID-3030?page=com.atlassian.jira.plugin... ] Gary Gregory commented on TEIID-3030: ------------------------------------- {quote} Are you using Teiid embedded? {quote} Yes, version 8.7.0, which is delivered with Saxon-HE in {{teiid-8.7.0.Final-embedded-dist.zip/lib/saxonhe-9.2.1.5.jar}} {quote} Have you tried just using the later saxon version ...? {quote} Yes, which is why I created this issue. If I use 9.4.0.6 instead of 9.2.1.5, I get: {noformat} java.lang.NoClassDefFoundError: net/sf/saxon/expr/PathMap$PathMapNode at org.teiid.query.sql.lang.XMLTable.compileXqueryExpression(XMLTable.java:114) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:325) at org.teiid.query.sql.lang.XMLTable.acceptVisitor(XMLTable.java:159) at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:63) at org.teiid.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:76) at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:186) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:568) at org.teiid.query.sql.lang.From.acceptVisitor(From.java:146) at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:63) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:209) at org.teiid.query.resolver.command.SimpleQueryResolver.resolveCommand(SimpleQueryResolver.java:67) at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:271) at org.teiid.query.resolver.QueryResolver.resolveView(QueryResolver.java:436) at org.teiid.query.metadata.MetadataValidator.validate(MetadataValidator.java:318) at org.teiid.query.metadata.MetadataValidator.access$100(MetadataValidator.java:66) at org.teiid.query.metadata.MetadataValidator$ResolveQueryPlans.execute(MetadataValidator.java:219) at org.teiid.query.metadata.MetadataValidator.validate(MetadataValidator.java:90) at org.teiid.deployers.VDBRepository.finishDeployment(VDBRepository.java:294) at org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:195) at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:694) at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:161) at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:635) at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:576) at com.seagullsw.appinterface.server.comm.virtualdb.TeiidCommunicationManager.doStart(TeiidCommunicationManager.java:177) ... com.seagullsw.appinterface.server.comm.virtualdb.TeiidTcpCommunicationManagerRoundtripTestCase.setUpOnce(TeiidTcpCommunicationManagerRoundtripTestCase.java:27) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) Caused by: java.lang.ClassNotFoundException: net.sf.saxon.expr.PathMap$PathMapNode at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 54 more {noformat} {quote} ... or are there api changes affecting Teiid? {quote} Yes, in Saxon 9.4.0.6, net/sf/saxon/expr/PathMap is now in net/sf/saxon/expr/parser/PathMap {quote} Unfortunately we don't have complete flexibility here as the saxon dependency is normally coming from the AS/EAP platform. {quote} That does not seem to be the case since the Saxon-HE jar is delivered with the embedded zip. If I try to recompile Teiid with Saxon-HE 9.5.1-6, I get all sorts of errors, presumably due to the package changes. What is the next step? > Update Saxon to current release (9.5) > ------------------------------------- > > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-3010) odata webapp missing joda time dependency

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3010?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-3010. -------------------------------- Resolution: Done > odata webapp missing joda time dependency > ----------------------------------------- > > Key: TEIID-3010 > URL: https://issues.jboss.org/browse/TEIID-3010 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.4.3, 8.8 > > > Usage of a datetime literal (datetime'2000-01-01T00:00:00) in a query, results in a no class def error: > Caused by: java.lang.NoClassDefFoundError: org/joda/time/LocalDateTime > at org.teiid.odata.ODataSQLBuilder.visit(ODataSQLBuilder.java:454) [classes:] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3010) odata webapp missing joda time dependency

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3010?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3010: ---------------------------------- re-open for fix version > odata webapp missing joda time dependency > ----------------------------------------- > > Key: TEIID-3010 > URL: https://issues.jboss.org/browse/TEIID-3010 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > Usage of a datetime literal (datetime'2000-01-01T00:00:00) in a query, results in a no class def error: > Caused by: java.lang.NoClassDefFoundError: org/joda/time/LocalDateTime > at org.teiid.odata.ODataSQLBuilder.visit(ODataSQLBuilder.java:454) [classes:] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2014