[JBoss JIRA] (TEIID-5269) Odata4 metadata roundtrip is not in place
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5269?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5269.
-----------------------------------
Fix Version/s: 10.1.2
10.0.4
10.2
Resolution: Done
Updated the odata metadata generation to include referential constraints and changed the metadata processor to infer more fk situations.
> Odata4 metadata roundtrip is not in place
> -----------------------------------------
>
> Key: TEIID-5269
> URL: https://issues.jboss.org/browse/TEIID-5269
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors, OData
> Affects Versions: 8.12.12.6_4
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 10.1.2, 10.0.4, 10.2
>
>
> Teiid should be able to import (using odata4 translator) metadata exposed by its own odata4 interface.
> Currently there is following identified discrepancy.
> Foreign keys are not properly carried through the expose/import roundtrip. After importing metadata from odata4 endpoint for another vdb (all in single instance), the resulting metadata lacks FK definitions.
> For following data exposed in a VDB:
> {code:sql}
> CREATE VIEW A(a_id integer PRIMARY KEY, a_value string) AS SELECT 1, 'a1' UNION ALL SELECT 2, 'a2';
> CREATE VIEW B(b_id integer PRIMARY KEY, b_value string) AS SELECT 3, 'b1' UNION ALL SELECT 4, 'b2';
> CREATE VIEW C(c_id integer PRIMARY KEY, a_ref integer, b_ref integer,
> FOREIGN KEY (a_ref) REFERENCES A(a_id),
> FOREIGN KEY (b_ref) REFERENCES B(b_id))
> AS SELECT 5, 1, 3 UNION ALL SELECT 6, 2, 4;
> {code}
> the following odata4 metadata are served:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <edmx:Edmx xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx" Version="4.0">
> <edmx:Reference Uri="http://localhost:8080/odata4/static/org.apache.olingo.v1.xml">
> <edmx:Include Namespace="org.apache.olingo.v1" Alias="olingo-extensions"/>
> </edmx:Reference>
> <edmx:DataServices>
> <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="teiid5221data.1.data" Alias="data">
> <EntityType Name="A">
> <Key>
> <PropertyRef Name="a_id"/>
> </Key>
> <Property Name="a_id" Type="Edm.Int32" Nullable="false"/>
> <Property Name="a_value" Type="Edm.String" MaxLength="4000"/>
> <NavigationProperty Name="C_FK0" Type="Collection(data.C)"/>
> </EntityType>
> <EntityType Name="B">
> <Key>
> <PropertyRef Name="b_id"/>
> </Key>
> <Property Name="b_id" Type="Edm.Int32" Nullable="false"/>
> <Property Name="b_value" Type="Edm.String" MaxLength="4000"/>
> <NavigationProperty Name="C_FK1" Type="Collection(data.C)"/>
> </EntityType>
> <EntityType Name="C">
> <Key>
> <PropertyRef Name="c_id"/>
> </Key>
> <Property Name="c_id" Type="Edm.Int32" Nullable="false"/>
> <Property Name="a_ref" Type="Edm.Int32"/>
> <Property Name="b_ref" Type="Edm.Int32"/>
> <NavigationProperty Name="FK0" Type="data.A"/>
> <NavigationProperty Name="FK1" Type="data.B"/>
> </EntityType>
> <EntityContainer Name="data">
> <EntitySet Name="A" EntityType="data.A">
> <NavigationPropertyBinding Path="C_FK0" Target="C"/>
> </EntitySet>
> <EntitySet Name="B" EntityType="data.B">
> <NavigationPropertyBinding Path="C_FK1" Target="C"/>
> </EntitySet>
> <EntitySet Name="C" EntityType="data.C">
> <NavigationPropertyBinding Path="FK0" Target="A"/>
> <NavigationPropertyBinding Path="FK1" Target="B"/>
> </EntitySet>
> </EntityContainer>
> </Schema>
> </edmx:DataServices>
> </edmx:Edmx>
> {code}
> Then, when I import from the odata4 endpoint I get following:
> {code:sql}
> ===> SET NAMESPACE 'http://www.jboss.org/teiiddesigner/ext/odata/2012' AS teiid_odata;
> CREATE FOREIGN TABLE A (
> a_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> a_value string,
> PRIMARY KEY(a_id)
> ) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.A', "teiid_odata:Type" 'ENTITY_COLLECTION');
> CREATE FOREIGN TABLE B (
> b_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> b_value string,
> PRIMARY KEY(b_id)
> ) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.B', "teiid_odata:Type" 'ENTITY_COLLECTION');
> CREATE FOREIGN TABLE C (
> c_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> a_ref integer OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> b_ref integer OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> PRIMARY KEY(c_id)
> ) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.C', "teiid_odata:Type" 'ENTITY_COLLECTION');
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (TEIID-5269) Odata4 metadata roundtrip is not in place
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5269?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-5269:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1550151
Bugzilla Update: Perform
> Odata4 metadata roundtrip is not in place
> -----------------------------------------
>
> Key: TEIID-5269
> URL: https://issues.jboss.org/browse/TEIID-5269
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors, OData
> Affects Versions: 8.12.12.6_4
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> Teiid should be able to import (using odata4 translator) metadata exposed by its own odata4 interface.
> Currently there is following identified discrepancy.
> Foreign keys are not properly carried through the expose/import roundtrip. After importing metadata from odata4 endpoint for another vdb (all in single instance), the resulting metadata lacks FK definitions.
> For following data exposed in a VDB:
> {code:sql}
> CREATE VIEW A(a_id integer PRIMARY KEY, a_value string) AS SELECT 1, 'a1' UNION ALL SELECT 2, 'a2';
> CREATE VIEW B(b_id integer PRIMARY KEY, b_value string) AS SELECT 3, 'b1' UNION ALL SELECT 4, 'b2';
> CREATE VIEW C(c_id integer PRIMARY KEY, a_ref integer, b_ref integer,
> FOREIGN KEY (a_ref) REFERENCES A(a_id),
> FOREIGN KEY (b_ref) REFERENCES B(b_id))
> AS SELECT 5, 1, 3 UNION ALL SELECT 6, 2, 4;
> {code}
> the following odata4 metadata are served:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <edmx:Edmx xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx" Version="4.0">
> <edmx:Reference Uri="http://localhost:8080/odata4/static/org.apache.olingo.v1.xml">
> <edmx:Include Namespace="org.apache.olingo.v1" Alias="olingo-extensions"/>
> </edmx:Reference>
> <edmx:DataServices>
> <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="teiid5221data.1.data" Alias="data">
> <EntityType Name="A">
> <Key>
> <PropertyRef Name="a_id"/>
> </Key>
> <Property Name="a_id" Type="Edm.Int32" Nullable="false"/>
> <Property Name="a_value" Type="Edm.String" MaxLength="4000"/>
> <NavigationProperty Name="C_FK0" Type="Collection(data.C)"/>
> </EntityType>
> <EntityType Name="B">
> <Key>
> <PropertyRef Name="b_id"/>
> </Key>
> <Property Name="b_id" Type="Edm.Int32" Nullable="false"/>
> <Property Name="b_value" Type="Edm.String" MaxLength="4000"/>
> <NavigationProperty Name="C_FK1" Type="Collection(data.C)"/>
> </EntityType>
> <EntityType Name="C">
> <Key>
> <PropertyRef Name="c_id"/>
> </Key>
> <Property Name="c_id" Type="Edm.Int32" Nullable="false"/>
> <Property Name="a_ref" Type="Edm.Int32"/>
> <Property Name="b_ref" Type="Edm.Int32"/>
> <NavigationProperty Name="FK0" Type="data.A"/>
> <NavigationProperty Name="FK1" Type="data.B"/>
> </EntityType>
> <EntityContainer Name="data">
> <EntitySet Name="A" EntityType="data.A">
> <NavigationPropertyBinding Path="C_FK0" Target="C"/>
> </EntitySet>
> <EntitySet Name="B" EntityType="data.B">
> <NavigationPropertyBinding Path="C_FK1" Target="C"/>
> </EntitySet>
> <EntitySet Name="C" EntityType="data.C">
> <NavigationPropertyBinding Path="FK0" Target="A"/>
> <NavigationPropertyBinding Path="FK1" Target="B"/>
> </EntitySet>
> </EntityContainer>
> </Schema>
> </edmx:DataServices>
> </edmx:Edmx>
> {code}
> Then, when I import from the odata4 endpoint I get following:
> {code:sql}
> ===> SET NAMESPACE 'http://www.jboss.org/teiiddesigner/ext/odata/2012' AS teiid_odata;
> CREATE FOREIGN TABLE A (
> a_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> a_value string,
> PRIMARY KEY(a_id)
> ) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.A', "teiid_odata:Type" 'ENTITY_COLLECTION');
> CREATE FOREIGN TABLE B (
> b_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> b_value string,
> PRIMARY KEY(b_id)
> ) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.B', "teiid_odata:Type" 'ENTITY_COLLECTION');
> CREATE FOREIGN TABLE C (
> c_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> a_ref integer OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> b_ref integer OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> PRIMARY KEY(c_id)
> ) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.C', "teiid_odata:Type" 'ENTITY_COLLECTION');
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (TEIID-5269) Odata4 metadata roundtrip is not in place
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5269?page=com.atlassian.jira.plugin... ]
Work on TEIID-5269 started by Steven Hawkins.
---------------------------------------------
> Odata4 metadata roundtrip is not in place
> -----------------------------------------
>
> Key: TEIID-5269
> URL: https://issues.jboss.org/browse/TEIID-5269
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors, OData
> Affects Versions: 8.12.12.6_4
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> Teiid should be able to import (using odata4 translator) metadata exposed by its own odata4 interface.
> Currently there is following identified discrepancy.
> Foreign keys are not properly carried through the expose/import roundtrip. After importing metadata from odata4 endpoint for another vdb (all in single instance), the resulting metadata lacks FK definitions.
> For following data exposed in a VDB:
> {code:sql}
> CREATE VIEW A(a_id integer PRIMARY KEY, a_value string) AS SELECT 1, 'a1' UNION ALL SELECT 2, 'a2';
> CREATE VIEW B(b_id integer PRIMARY KEY, b_value string) AS SELECT 3, 'b1' UNION ALL SELECT 4, 'b2';
> CREATE VIEW C(c_id integer PRIMARY KEY, a_ref integer, b_ref integer,
> FOREIGN KEY (a_ref) REFERENCES A(a_id),
> FOREIGN KEY (b_ref) REFERENCES B(b_id))
> AS SELECT 5, 1, 3 UNION ALL SELECT 6, 2, 4;
> {code}
> the following odata4 metadata are served:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <edmx:Edmx xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx" Version="4.0">
> <edmx:Reference Uri="http://localhost:8080/odata4/static/org.apache.olingo.v1.xml">
> <edmx:Include Namespace="org.apache.olingo.v1" Alias="olingo-extensions"/>
> </edmx:Reference>
> <edmx:DataServices>
> <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="teiid5221data.1.data" Alias="data">
> <EntityType Name="A">
> <Key>
> <PropertyRef Name="a_id"/>
> </Key>
> <Property Name="a_id" Type="Edm.Int32" Nullable="false"/>
> <Property Name="a_value" Type="Edm.String" MaxLength="4000"/>
> <NavigationProperty Name="C_FK0" Type="Collection(data.C)"/>
> </EntityType>
> <EntityType Name="B">
> <Key>
> <PropertyRef Name="b_id"/>
> </Key>
> <Property Name="b_id" Type="Edm.Int32" Nullable="false"/>
> <Property Name="b_value" Type="Edm.String" MaxLength="4000"/>
> <NavigationProperty Name="C_FK1" Type="Collection(data.C)"/>
> </EntityType>
> <EntityType Name="C">
> <Key>
> <PropertyRef Name="c_id"/>
> </Key>
> <Property Name="c_id" Type="Edm.Int32" Nullable="false"/>
> <Property Name="a_ref" Type="Edm.Int32"/>
> <Property Name="b_ref" Type="Edm.Int32"/>
> <NavigationProperty Name="FK0" Type="data.A"/>
> <NavigationProperty Name="FK1" Type="data.B"/>
> </EntityType>
> <EntityContainer Name="data">
> <EntitySet Name="A" EntityType="data.A">
> <NavigationPropertyBinding Path="C_FK0" Target="C"/>
> </EntitySet>
> <EntitySet Name="B" EntityType="data.B">
> <NavigationPropertyBinding Path="C_FK1" Target="C"/>
> </EntitySet>
> <EntitySet Name="C" EntityType="data.C">
> <NavigationPropertyBinding Path="FK0" Target="A"/>
> <NavigationPropertyBinding Path="FK1" Target="B"/>
> </EntitySet>
> </EntityContainer>
> </Schema>
> </edmx:DataServices>
> </edmx:Edmx>
> {code}
> Then, when I import from the odata4 endpoint I get following:
> {code:sql}
> ===> SET NAMESPACE 'http://www.jboss.org/teiiddesigner/ext/odata/2012' AS teiid_odata;
> CREATE FOREIGN TABLE A (
> a_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> a_value string,
> PRIMARY KEY(a_id)
> ) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.A', "teiid_odata:Type" 'ENTITY_COLLECTION');
> CREATE FOREIGN TABLE B (
> b_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> b_value string,
> PRIMARY KEY(b_id)
> ) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.B', "teiid_odata:Type" 'ENTITY_COLLECTION');
> CREATE FOREIGN TABLE C (
> c_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> a_ref integer OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> b_ref integer OPTIONS (NATIVE_TYPE 'Edm.Int32'),
> PRIMARY KEY(c_id)
> ) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.C', "teiid_odata:Type" 'ENTITY_COLLECTION');
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (TEIID-5268) Anonymous bind login doesn't work for ldap connector
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5268?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5268:
---------------------------------------
The JCA layer is substituting "undefined" at runtime instead of an empty string, so the connection will not attempt an anonymous bind. I need to check if it's valid to pass an empty string in any way or if we need to change our logic.
> Anonymous bind login doesn't work for ldap connector
> ----------------------------------------------------
>
> Key: TEIID-5268
> URL: https://issues.jboss.org/browse/TEIID-5268
> Project: Teiid
> Issue Type: Bug
> Components: LDAP Connector
> Affects Versions: 8.8, 8.12.5
> Reporter: Yuming Zhu
> Assignee: Steven Hawkins
>
> I configured an anonymous to connect to LDAP server via ldaps://... according to https://docs.jboss.org/author/display/teiid812final/LDAP+Data+Sources
> like:
> {code:xml}
> <resource-adapter id="ldap">
> <module slot="main" id="org.jboss.teiid.resource-adapter.ldap"/>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory" jndi-name="java:/ldapDS" enabled="true" use-java-context="true" pool-name="ldapDS">
> <config-property name="LdapUrl">
> ldaps://ldap.corp.redhat.com:636
> </config-property>
> <config-property name="LdapAdminUserDN">
> </config-property>
> <config-property name="LdapAdminUserPassword">
> </config-property>
> <config-property name="LdapTxnTimeoutInMillis">
> -1
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
> {code}
> when I test the connection by jboss-cli, error occurs:
> command:
> {code}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=ldap/connection-definitions=ldapDS:test-connection-in-pool
> {code}
> error:
> {code}
> 13:02:17,263 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) ldapDS running as FIFO
> 13:02:17,263 DEBUG [org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover] (management-handler-thread - 3) Register pool: SemaphoreArrayListManagedConnectionPool@13f30b23[pool=ldapDS] (interval=1800000)
> 13:02:17,264 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) ldapDS: getConnection(null, null) [0/20]
> 13:02:17,802 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Initializing LDAP directory context failed. Please check LDAP connection properties, including username and password: [LDAP: error code 49 - Invalid Credentials]
> at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.initializeLDAPContext(LDAPConnectionImpl.java:151)
> at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.<init>(LDAPConnectionImpl.java:75)
> at org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory$1.getConnection(LDAPManagedConnectionFactory.java:49)
> at org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory$1.getConnection(LDAPManagedConnectionFactory.java:43)
> at org.teiid.resource.spi.BasicManagedConnectionFactory.createManagedConnection(BasicManagedConnectionFactory.java:71)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:858) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:413) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.internalTestConnection(AbstractPool.java:725) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.strategy.OnePool.testConnection(OnePool.java:89) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
> at org.jboss.as.connector.subsystems.common.pool.PoolOperations$TestConnectionInPool.invokeCommandOn(PoolOperations.java:143) [jboss-as-connector-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.connector.subsystems.common.pool.PoolOperations$1.execute(PoolOperations.java:82) [jboss-as-connector-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:702) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:537) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:338) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:314) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1144) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:331) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:201) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:135) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_112]
> at javax.security.auth.Subject.doAs(Subject.java:422) [rt.jar:1.8.0_112]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:298)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:537)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_112]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_112]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_112]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
> Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3136) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3082) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2883) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2797) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83) [rt.jar:1.8.0_112]
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:122) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.naming.InitialContext.init(InitialContext.java:107) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) [rt.jar:1.8.0_112]
> at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:98) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) [rt.jar:1.8.0_112]
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) [rt.jar:1.8.0_112]
> at javax.naming.InitialContext.init(InitialContext.java:244) [rt.jar:1.8.0_112]
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) [rt.jar:1.8.0_112]
> at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.initializeLDAPContext(LDAPConnectionImpl.java:148)
> ... 31 more
> 13:02:17,808 DEBUG [org.jboss.as.controller.management-operation] (management-handler-thread - 3) JBAS014616: Operation ("test-connection-in-pool") failed - address: ([
> ("subsystem" => "resource-adapters"),
> ("resource-adapter" => "ldap"),
> ("connection-definitions" => "ldapDS")
> ]) - failure description: "JBAS010440: failed to invoke operation: JBAS010447: Connection is not valid"
> {code}
> It looks username isn't set as expected
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (TEIID-5221) OData4 Translator generates invalid metadata
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-5221?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-5221:
------------------------------------
[~shawkins], [~jolee]
I have created following JIRA to track the issue: TEIID-5269
> OData4 Translator generates invalid metadata
> ---------------------------------------------
>
> Key: TEIID-5221
> URL: https://issues.jboss.org/browse/TEIID-5221
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors, OData
> Affects Versions: 8.12
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 10.1, 10.0.3, 9.3.7, 8.12.12.6_4
>
>
> The OData V4 translator does not generate metadata correctly in situations
> 1) When multiple navigations are defined on the EnitityType.
> 2) The PSEDEO column usage is incorrect, as this should be only used with ComplexType structures when the association to EntityType is made. But this is also used in cases where incorrect referential constraints are used. This may lead to the additional columns on Entities which are hard to resolve during the runtime.
> 3) Usage of MERGE property is also incorrect when multiple navigation properties are defined as these may be overridden for (1)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (TEIID-5269) Odata4 metadata roundtrip is not in place
by Jan Stastny (JIRA)
Jan Stastny created TEIID-5269:
----------------------------------
Summary: Odata4 metadata roundtrip is not in place
Key: TEIID-5269
URL: https://issues.jboss.org/browse/TEIID-5269
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors, OData
Affects Versions: 8.12.12.6_4
Reporter: Jan Stastny
Assignee: Steven Hawkins
Teiid should be able to import (using odata4 translator) metadata exposed by its own odata4 interface.
Currently there is following identified discrepancy.
Foreign keys are not properly carried through the expose/import roundtrip. After importing metadata from odata4 endpoint for another vdb (all in single instance), the resulting metadata lacks FK definitions.
For following data exposed in a VDB:
{code:sql}
CREATE VIEW A(a_id integer PRIMARY KEY, a_value string) AS SELECT 1, 'a1' UNION ALL SELECT 2, 'a2';
CREATE VIEW B(b_id integer PRIMARY KEY, b_value string) AS SELECT 3, 'b1' UNION ALL SELECT 4, 'b2';
CREATE VIEW C(c_id integer PRIMARY KEY, a_ref integer, b_ref integer,
FOREIGN KEY (a_ref) REFERENCES A(a_id),
FOREIGN KEY (b_ref) REFERENCES B(b_id))
AS SELECT 5, 1, 3 UNION ALL SELECT 6, 2, 4;
{code}
the following odata4 metadata are served:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<edmx:Edmx xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx" Version="4.0">
<edmx:Reference Uri="http://localhost:8080/odata4/static/org.apache.olingo.v1.xml">
<edmx:Include Namespace="org.apache.olingo.v1" Alias="olingo-extensions"/>
</edmx:Reference>
<edmx:DataServices>
<Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="teiid5221data.1.data" Alias="data">
<EntityType Name="A">
<Key>
<PropertyRef Name="a_id"/>
</Key>
<Property Name="a_id" Type="Edm.Int32" Nullable="false"/>
<Property Name="a_value" Type="Edm.String" MaxLength="4000"/>
<NavigationProperty Name="C_FK0" Type="Collection(data.C)"/>
</EntityType>
<EntityType Name="B">
<Key>
<PropertyRef Name="b_id"/>
</Key>
<Property Name="b_id" Type="Edm.Int32" Nullable="false"/>
<Property Name="b_value" Type="Edm.String" MaxLength="4000"/>
<NavigationProperty Name="C_FK1" Type="Collection(data.C)"/>
</EntityType>
<EntityType Name="C">
<Key>
<PropertyRef Name="c_id"/>
</Key>
<Property Name="c_id" Type="Edm.Int32" Nullable="false"/>
<Property Name="a_ref" Type="Edm.Int32"/>
<Property Name="b_ref" Type="Edm.Int32"/>
<NavigationProperty Name="FK0" Type="data.A"/>
<NavigationProperty Name="FK1" Type="data.B"/>
</EntityType>
<EntityContainer Name="data">
<EntitySet Name="A" EntityType="data.A">
<NavigationPropertyBinding Path="C_FK0" Target="C"/>
</EntitySet>
<EntitySet Name="B" EntityType="data.B">
<NavigationPropertyBinding Path="C_FK1" Target="C"/>
</EntitySet>
<EntitySet Name="C" EntityType="data.C">
<NavigationPropertyBinding Path="FK0" Target="A"/>
<NavigationPropertyBinding Path="FK1" Target="B"/>
</EntitySet>
</EntityContainer>
</Schema>
</edmx:DataServices>
</edmx:Edmx>
{code}
Then, when I import from the odata4 endpoint I get following:
{code:sql}
===> SET NAMESPACE 'http://www.jboss.org/teiiddesigner/ext/odata/2012' AS teiid_odata;
CREATE FOREIGN TABLE A (
a_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'),
a_value string,
PRIMARY KEY(a_id)
) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.A', "teiid_odata:Type" 'ENTITY_COLLECTION');
CREATE FOREIGN TABLE B (
b_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'),
b_value string,
PRIMARY KEY(b_id)
) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.B', "teiid_odata:Type" 'ENTITY_COLLECTION');
CREATE FOREIGN TABLE C (
c_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'),
a_ref integer OPTIONS (NATIVE_TYPE 'Edm.Int32'),
b_ref integer OPTIONS (NATIVE_TYPE 'Edm.Int32'),
PRIMARY KEY(c_id)
) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.C', "teiid_odata:Type" 'ENTITY_COLLECTION');
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (TEIID-5221) OData4 Translator generates invalid metadata
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5221?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5221:
---------------------------------------
I agree, can you log an issue about our/olingo's metadata generation? At the very least I'll use it to add the logic to cover the last case shown above.
> OData4 Translator generates invalid metadata
> ---------------------------------------------
>
> Key: TEIID-5221
> URL: https://issues.jboss.org/browse/TEIID-5221
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors, OData
> Affects Versions: 8.12
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 10.1, 10.0.3, 9.3.7, 8.12.12.6_4
>
>
> The OData V4 translator does not generate metadata correctly in situations
> 1) When multiple navigations are defined on the EnitityType.
> 2) The PSEDEO column usage is incorrect, as this should be only used with ComplexType structures when the association to EntityType is made. But this is also used in cases where incorrect referential constraints are used. This may lead to the additional columns on Entities which are hard to resolve during the runtime.
> 3) Usage of MERGE property is also incorrect when multiple navigation properties are defined as these may be overridden for (1)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (TEIID-5268) Anonymous bind login doesn't work for ldap connector
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5268?page=com.atlassian.jira.plugin... ]
Work on TEIID-5268 started by Steven Hawkins.
---------------------------------------------
> Anonymous bind login doesn't work for ldap connector
> ----------------------------------------------------
>
> Key: TEIID-5268
> URL: https://issues.jboss.org/browse/TEIID-5268
> Project: Teiid
> Issue Type: Bug
> Components: LDAP Connector
> Affects Versions: 8.8, 8.12.5
> Reporter: Yuming Zhu
> Assignee: Steven Hawkins
>
> I configured an anonymous to connect to LDAP server via ldaps://... according to https://docs.jboss.org/author/display/teiid812final/LDAP+Data+Sources
> like:
> {code:xml}
> <resource-adapter id="ldap">
> <module slot="main" id="org.jboss.teiid.resource-adapter.ldap"/>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory" jndi-name="java:/ldapDS" enabled="true" use-java-context="true" pool-name="ldapDS">
> <config-property name="LdapUrl">
> ldaps://ldap.corp.redhat.com:636
> </config-property>
> <config-property name="LdapAdminUserDN">
> </config-property>
> <config-property name="LdapAdminUserPassword">
> </config-property>
> <config-property name="LdapTxnTimeoutInMillis">
> -1
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
> {code}
> when I test the connection by jboss-cli, error occurs:
> command:
> {code}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=ldap/connection-definitions=ldapDS:test-connection-in-pool
> {code}
> error:
> {code}
> 13:02:17,263 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) ldapDS running as FIFO
> 13:02:17,263 DEBUG [org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover] (management-handler-thread - 3) Register pool: SemaphoreArrayListManagedConnectionPool@13f30b23[pool=ldapDS] (interval=1800000)
> 13:02:17,264 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) ldapDS: getConnection(null, null) [0/20]
> 13:02:17,802 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Initializing LDAP directory context failed. Please check LDAP connection properties, including username and password: [LDAP: error code 49 - Invalid Credentials]
> at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.initializeLDAPContext(LDAPConnectionImpl.java:151)
> at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.<init>(LDAPConnectionImpl.java:75)
> at org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory$1.getConnection(LDAPManagedConnectionFactory.java:49)
> at org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory$1.getConnection(LDAPManagedConnectionFactory.java:43)
> at org.teiid.resource.spi.BasicManagedConnectionFactory.createManagedConnection(BasicManagedConnectionFactory.java:71)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:858) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:413) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.internalTestConnection(AbstractPool.java:725) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.strategy.OnePool.testConnection(OnePool.java:89) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
> at org.jboss.as.connector.subsystems.common.pool.PoolOperations$TestConnectionInPool.invokeCommandOn(PoolOperations.java:143) [jboss-as-connector-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.connector.subsystems.common.pool.PoolOperations$1.execute(PoolOperations.java:82) [jboss-as-connector-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:702) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:537) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:338) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:314) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1144) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:331) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:201) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:135) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_112]
> at javax.security.auth.Subject.doAs(Subject.java:422) [rt.jar:1.8.0_112]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:298)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:537)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_112]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_112]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_112]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
> Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3136) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3082) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2883) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2797) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83) [rt.jar:1.8.0_112]
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:122) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.naming.InitialContext.init(InitialContext.java:107) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) [rt.jar:1.8.0_112]
> at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:98) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) [rt.jar:1.8.0_112]
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) [rt.jar:1.8.0_112]
> at javax.naming.InitialContext.init(InitialContext.java:244) [rt.jar:1.8.0_112]
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) [rt.jar:1.8.0_112]
> at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.initializeLDAPContext(LDAPConnectionImpl.java:148)
> ... 31 more
> 13:02:17,808 DEBUG [org.jboss.as.controller.management-operation] (management-handler-thread - 3) JBAS014616: Operation ("test-connection-in-pool") failed - address: ([
> ("subsystem" => "resource-adapters"),
> ("resource-adapter" => "ldap"),
> ("connection-definitions" => "ldapDS")
> ]) - failure description: "JBAS010440: failed to invoke operation: JBAS010447: Connection is not valid"
> {code}
> It looks username isn't set as expected
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (TEIID-5221) OData4 Translator generates invalid metadata
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-5221?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-5221:
------------------------------------
[~shawkins] well we should be able to consume, what we produce in Teiid. So either include ReferentialConstraint to the odata4 response, or be more flexible when importing from odata4.
No immediate need for that to accompany this fix, I'll use different odata source for now.
> OData4 Translator generates invalid metadata
> ---------------------------------------------
>
> Key: TEIID-5221
> URL: https://issues.jboss.org/browse/TEIID-5221
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors, OData
> Affects Versions: 8.12
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 10.1, 10.0.3, 9.3.7, 8.12.12.6_4
>
>
> The OData V4 translator does not generate metadata correctly in situations
> 1) When multiple navigations are defined on the EnitityType.
> 2) The PSEDEO column usage is incorrect, as this should be only used with ComplexType structures when the association to EntityType is made. But this is also used in cases where incorrect referential constraints are used. This may lead to the additional columns on Entities which are hard to resolve during the runtime.
> 3) Usage of MERGE property is also incorrect when multiple navigation properties are defined as these may be overridden for (1)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month