[JBoss JIRA] (TEIID-3036) Update CXF to current version (3.0.0)
by Gary Gregory (JIRA)
[ https://issues.jboss.org/browse/TEIID-3036?page=com.atlassian.jira.plugin... ]
Gary Gregory commented on TEIID-3036:
-------------------------------------
I am upgrading our server to CXF 2.7.11 from 2.7.10 and I do not see any conflicts yet. I does not mean there are no conflicts, just that our tests have not found them if they exist.
> Update CXF to current version (3.0.0)
> -------------------------------------
>
> Key: TEIID-3036
> URL: https://issues.jboss.org/browse/TEIID-3036
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Embedded
> Affects Versions: 8.8
> Reporter: Gary Gregory
> Assignee: Steven Hawkins
>
> In the same vein as TEIID-3030, we embed CXF and Teiid in our server. We use CXF 2.7.10 and are about to update to 3.0.0. At worse, we'll go to 2.7.11 as an interim step to 3.0.0.
> Teiid embedded delivers CXF 2.6.6 for web services support.
> It would be great if we could get Teiid to the latest and greatest from CXF so we can all live in the same space without being forced to deal with any incompatibilities or class loader hacks.
> Thank you,
> Gary
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3036) Update CXF to current version (3.0.0)
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3036?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3036:
-------------------------------------
I have been just copying the version from platform, to keep us informed of the version we are using, otherwise they should always match
> Update CXF to current version (3.0.0)
> -------------------------------------
>
> Key: TEIID-3036
> URL: https://issues.jboss.org/browse/TEIID-3036
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Embedded
> Affects Versions: 8.8
> Reporter: Gary Gregory
> Assignee: Steven Hawkins
>
> In the same vein as TEIID-3030, we embed CXF and Teiid in our server. We use CXF 2.7.10 and are about to update to 3.0.0. At worse, we'll go to 2.7.11 as an interim step to 3.0.0.
> Teiid embedded delivers CXF 2.6.6 for web services support.
> It would be great if we could get Teiid to the latest and greatest from CXF so we can all live in the same space without being forced to deal with any incompatibilities or class loader hacks.
> Thank you,
> Gary
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3036) Update CXF to current version (3.0.0)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3036?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3036:
---------------------------------------
> Is that version mix comming from JBoss? That can't be good...
Not exactly. We are contributing the frontend-jaxrs jars based upon the upstream EAP version (a carry forward from an 8.7.x change). Our root pom is attempting to override the managed version with the property version.org.apache.cxf set to 2.6.8, but the kitting is still picking up 2.6.6 for the other cxf jars. I'm not sure why this is, but since the jars are compatible we haven't spent too much effort tracking that down.
On a related note, compatibility with EAP 6.3 will bring CXF up to 2.7.11, but until there is a corresponding community release we are somewhat stuck on master targeting the EAP 6.0 Alpha1 version.
Have you tried embedded with 2.7.11 or 3.0.0?
Ramesh - should we just remove our version overrides from 8.7.x to pick up the appropriate platform version?
> Can that be fixed?
You should use the version specific to the connectivity, which is why they are packaged that way. There is only a potential issue if you attempt to use conflicting version, such as cassandra and google spreadsheet connectivity together in embedded. But based upon our AS/EAP testing it appears that either is fine using the lesser guava version (actually the platform version is down at 13.0.1), but it's always best to use the latest when possible. Guava is doing a much better job with api compatibility than saxon.
> Update CXF to current version (3.0.0)
> -------------------------------------
>
> Key: TEIID-3036
> URL: https://issues.jboss.org/browse/TEIID-3036
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Embedded
> Affects Versions: 8.8
> Reporter: Gary Gregory
> Assignee: Steven Hawkins
>
> In the same vein as TEIID-3030, we embed CXF and Teiid in our server. We use CXF 2.7.10 and are about to update to 3.0.0. At worse, we'll go to 2.7.11 as an interim step to 3.0.0.
> Teiid embedded delivers CXF 2.6.6 for web services support.
> It would be great if we could get Teiid to the latest and greatest from CXF so we can all live in the same space without being forced to deal with any incompatibilities or class loader hacks.
> Thank you,
> Gary
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3036) Update CXF to current version (3.0.0)
by Gary Gregory (JIRA)
[ https://issues.jboss.org/browse/TEIID-3036?page=com.atlassian.jira.plugin... ]
Gary Gregory commented on TEIID-3036:
-------------------------------------
Hm... I see.
The following is a bit messy though: there seems to be a mix for CXF 2.6.6 and 2.6.8:
- optional\webservice\cxf-api-2.6.6.jar
- optional\webservice\cxf-bundle-2.6.8.jar
- optional\webservice\cxf-rt-bindings-xml-2.6.6.jar
- optional\webservice\cxf-rt-core-2.6.6.jar
- optional\webservice\cxf-rt-frontend-jaxrs-2.6.8.jar
Is that version mix comming from JBoss? That can't be good...
Other jars are duplicated:
- optional\cassandra\guava-16.0.1.jar
- optional\google\guava-14.0.1.jar
Can that be fixed?
> Update CXF to current version (3.0.0)
> -------------------------------------
>
> Key: TEIID-3036
> URL: https://issues.jboss.org/browse/TEIID-3036
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Embedded
> Affects Versions: 8.8
> Reporter: Gary Gregory
> Assignee: Steven Hawkins
>
> In the same vein as TEIID-3030, we embed CXF and Teiid in our server. We use CXF 2.7.10 and are about to update to 3.0.0. At worse, we'll go to 2.7.11 as an interim step to 3.0.0.
> Teiid embedded delivers CXF 2.6.6 for web services support.
> It would be great if we could get Teiid to the latest and greatest from CXF so we can all live in the same space without being forced to deal with any incompatibilities or class loader hacks.
> Thank you,
> Gary
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3036) Update CXF to current version (3.0.0)
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3036?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3036:
-------------------------------------
The dependencies we setup for all the Teiid projects are based on JBoss EAP version we support for mainline distribution. Obviously we package the same dependency versions for embedded. We recommend using the versions that are provided. If you have the need to move up in dependency versions you have to make sure, if they are API compatible and works with Teiid without any issues. Since we are tied with JBoss EAP as our platform we do not always have flexibility to move the versions ad-hoc.
> Update CXF to current version (3.0.0)
> -------------------------------------
>
> Key: TEIID-3036
> URL: https://issues.jboss.org/browse/TEIID-3036
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Embedded
> Affects Versions: 8.8
> Reporter: Gary Gregory
> Assignee: Steven Hawkins
>
> In the same vein as TEIID-3030, we embed CXF and Teiid in our server. We use CXF 2.7.10 and are about to update to 3.0.0. At worse, we'll go to 2.7.11 as an interim step to 3.0.0.
> Teiid embedded delivers CXF 2.6.6 for web services support.
> It would be great if we could get Teiid to the latest and greatest from CXF so we can all live in the same space without being forced to deal with any incompatibilities or class loader hacks.
> Thank you,
> Gary
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3036) Update CXF to current version (3.0.0)
by Gary Gregory (JIRA)
[ https://issues.jboss.org/browse/TEIID-3036?page=com.atlassian.jira.plugin... ]
Gary Gregory commented on TEIID-3036:
-------------------------------------
The CXF jars are delivered in the Teiid embedded ws folder so how can it be in the platform? I provide the platform, it's not part of the embedded zip.
> Update CXF to current version (3.0.0)
> -------------------------------------
>
> Key: TEIID-3036
> URL: https://issues.jboss.org/browse/TEIID-3036
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Embedded
> Affects Versions: 8.8
> Reporter: Gary Gregory
> Assignee: Steven Hawkins
>
> In the same vein as TEIID-3030, we embed CXF and Teiid in our server. We use CXF 2.7.10 and are about to update to 3.0.0. At worse, we'll go to 2.7.11 as an interim step to 3.0.0.
> Teiid embedded delivers CXF 2.6.6 for web services support.
> It would be great if we could get Teiid to the latest and greatest from CXF so we can all live in the same space without being forced to deal with any incompatibilities or class loader hacks.
> Thank you,
> Gary
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3036) Update CXF to current version (3.0.0)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3036?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3036:
---------------------------------------
The same comments from TEIID-3030 are applicable here. The version we use is coming from the platform. If you try to use embedded with an updated cxf what happens? And for future proofing you'll want to look at isolating your application from teiid embedded.
> Update CXF to current version (3.0.0)
> -------------------------------------
>
> Key: TEIID-3036
> URL: https://issues.jboss.org/browse/TEIID-3036
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Embedded
> Affects Versions: 8.8
> Reporter: Gary Gregory
> Assignee: Steven Hawkins
>
> In the same vein as TEIID-3030, we embed CXF and Teiid in our server. We use CXF 2.7.10 and are about to update to 3.0.0. At worse, we'll go to 2.7.11 as an interim step to 3.0.0.
> Teiid embedded delivers CXF 2.6.6 for web services support.
> It would be great if we could get Teiid to the latest and greatest from CXF so we can all live in the same space without being forced to deal with any incompatibilities or class loader hacks.
> Thank you,
> Gary
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIID-3036) Update CXF to current version (3.0.0)
by Gary Gregory (JIRA)
Gary Gregory created TEIID-3036:
-----------------------------------
Summary: Update CXF to current version (3.0.0)
Key: TEIID-3036
URL: https://issues.jboss.org/browse/TEIID-3036
Project: Teiid
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Embedded
Affects Versions: 8.8
Reporter: Gary Gregory
Assignee: Steven Hawkins
In the same vein as TEIID-3030, we embed CXF and Teiid in our server. We use CXF 2.7.10 and are about to update to 3.0.0. At worse, we'll go to 2.7.11 as an interim step to 3.0.0.
Teiid embedded delivers CXF 2.6.6 for web services support.
It would be great if we could get Teiid to the latest and greatest from CXF so we can all live in the same space without being forced to deal with any incompatibilities or class loader hacks.
Thank you,
Gary
--
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... ]
Work on TEIID-3030 started by Steven Hawkins.
> 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-3023) records lost when query by hiernate
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3023?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3023:
---------------------------------------
Do you have any more details here? The query plan(s)? Or even a vdb? Otherwise I'll need to resolve as incomplete description.
> records lost when query by hiernate
> -----------------------------------
>
> Key: TEIID-3023
> URL: https://issues.jboss.org/browse/TEIID-3023
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 7.3
> Environment: window7,eclipse Helios Service Release 2, Teiid v7.3.0
> Reporter: Lai Chao
> Priority: Minor
>
> Recently, I get an issue when retrieve data from vdb that some records lost in the list. Fox example, from source table we can get 12100 records, but from vdb query(projects with hibernate) can only get 10800+ records.
> Meanwhile, there's a set on maxSetSize = 1000, is there any affects?
> Please advise.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months