[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 see that CXF 3 has made it in Wildfly through https://issues.jboss.org/browse/WFLY-3790. Any ideas on when this will trickle down to Teiid's web service component?
> 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
> Components: Embedded
> Affects Versions: 8.8
> Reporter: Gary Gregory
>
> 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.3.11#6341)
10 years, 2 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 edited comment on TEIID-3036 at 12/26/14 12:19 PM:
----------------------------------------------------------------
(Sorry for the double comment, I can only edit, not delete)
was (Author: gary.gregory):
I see that CXF 3 has made it in Wildfly through https://issues.jboss.org/browse/WFLY-3790. Any ideas on when this will trickle down to Teiid's web service component?
> 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
> Components: Embedded
> Affects Versions: 8.8
> Reporter: Gary Gregory
>
> 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.3.11#6341)
10 years, 2 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:
-------------------------------------
I see that CXF 3 has made it in Wildfly through https://issues.jboss.org/browse/WFLY-3790. Any ideas on when this will trickle down to Teiid's web service component?
> 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
> Components: Embedded
> Affects Versions: 8.8
> Reporter: Gary Gregory
>
> 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.3.11#6341)
10 years, 2 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:
-------------------------------------
FWIW, Saxon is now on to its 9.6.x line.
> 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
> 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
> Fix For: 8.9
>
>
> 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.3.11#6341)
10 years, 2 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:
-------------------------------------
FWIW, Saxon is now on to its 9.6.x line.
> 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
> 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
> Fix For: 8.9
>
>
> 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.3.11#6341)
10 years, 2 months
[JBoss JIRA] (TEIID-3269) Oracle pushdown time formatting incorrect
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3269:
-------------------------------------
Summary: Oracle pushdown time formatting incorrect
Key: TEIID-3269
URL: https://issues.jboss.org/browse/TEIID-3269
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 8.7.1, 8.10, 8.9.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.10, 8.9.1
Oracle formatting cannot control the number of digits displayed in the same way as Java formatting, needs to AM instead of PM, and needs better handling for ERA.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 2 months
[JBoss JIRA] (TEIID-2818) Use Oauth SAML Grant Type
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2818?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2818:
-------------------------------------
This is most cryptic requirement I have seen. The [OAuth|http://oauth.net/documentation/] specification is extended to allow different types of GRANT types. They are
* JSON Web Token
* OAuth Assertions Framework
* SAML2 Bearer Assertion - for integrating with existing identity systems - TEIID-2819
* JWT Bearer Assertion - for integrating with existing identity systems
The first two Teiid does not need to support as they are *not* involving the "delegation", the last two are the delegation models. I suspect this JIRA need to be support of "JWT Bearer Assertion". If we are just want to deal with OAuth and SAML TEIID-2819 is suffice.
> Use Oauth SAML Grant Type
> -------------------------
>
> Key: TEIID-2818
> URL: https://issues.jboss.org/browse/TEIID-2818
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
>
> How to connect to underlying data sources on behalf of Oauth when user comes into webservice with Oauth?
> Use cases:
> 1 – client u/p sources: oauth/saml
> 2- client : oauth/saml sorces u/p, other
> 3 – client: Oauth/saml sources Oauth/saml (data sources are also secured by Oauth) –
> 3a) propogate sources and 3b – resolve new tokens for sources
> Link: http://www.layer7tech.com/tutorials/oauth-20-with-layer-7-gateways-tutori...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 2 months