[JBoss JIRA] (TEIID-5561) Prevent alias collisions with built-in odata schema
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5561?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-5561 at 1/16/19 4:25 PM:
----------------------------------------------------------------
URL reserved characters are a problem also. The odata filter uses non decoded string to determine the vdb, version, and schema. I can't really find a reference in the odata spec as to the expectation or limitation on schema names.
was (Author: shawkins):
URL reserved characters are a problem also. The odata filter uses httpRequest.getContextPath() to determine the vdb, version, and schema - but that url is not decoded. I can't really find a reference in the odata spec as to the expectation or limitation on schema names.
> Prevent alias collisions with built-in odata schema
> ---------------------------------------------------
>
> Key: TEIID-5561
> URL: https://issues.jboss.org/browse/TEIID-5561
> Project: Teiid
> Issue Type: Quality Risk
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> It is problematic to have a Teiid model/schema with the name:
> olingo-extensions
> teiid
> edm
> as that will use an alias that conflicts with built-in handling. We should provide an error/warning as appropriate or come up with the logic to introduce a non-conflicting alias.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (TEIID-5594) Use generic rather than jboss javax dependencies for teiid core
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5594?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-5594:
-------------------------------
Git Pull Request: https://github.com/teiid/teiid/pull/1126
> Use generic rather than jboss javax dependencies for teiid core
> ---------------------------------------------------------------
>
> Key: TEIID-5594
> URL: https://issues.jboss.org/browse/TEIID-5594
> Project: Teiid
> Issue Type: Sub-task
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 12.1
>
>
> The following dependencies are aligned to Wildfly, but that is unnecessary for embedded/springboot. They should be replaced with more generic versions.
> {code}
> <dependency>
> <groupId>org.jboss.spec.javax.ws.rs</groupId>
> <artifactId>jboss-jaxrs-api_2.1_spec</artifactId>
> <version>1.0.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.xml.ws</groupId>
> <artifactId>jboss-jaxws-api_2.3_spec</artifactId>
> <version>1.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.servlet</groupId>
> <artifactId>jboss-servlet-api_3.1_spec</artifactId>
> <version>1.0.2.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.transaction</groupId>
> <artifactId>jboss-transaction-api_1.2_spec</artifactId>
> <version>1.1.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.xml.bind</groupId>
> <artifactId>jboss-jaxb-api_2.3_spec</artifactId>
> <version>1.0.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.slf4j</groupId>
> <artifactId>slf4j-api</artifactId>
> <version>1.7.22.jbossorg-1</version>
> </dependency>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (TEIID-5594) Use generic rather than jboss javax dependencies for teiid core
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5594?page=com.atlassian.jira.plugin... ]
Work on TEIID-5594 stopped by Van Halbert.
------------------------------------------
> Use generic rather than jboss javax dependencies for teiid core
> ---------------------------------------------------------------
>
> Key: TEIID-5594
> URL: https://issues.jboss.org/browse/TEIID-5594
> Project: Teiid
> Issue Type: Sub-task
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 12.1
>
>
> The following dependencies are aligned to Wildfly, but that is unnecessary for embedded/springboot. They should be replaced with more generic versions.
> {code}
> <dependency>
> <groupId>org.jboss.spec.javax.ws.rs</groupId>
> <artifactId>jboss-jaxrs-api_2.1_spec</artifactId>
> <version>1.0.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.xml.ws</groupId>
> <artifactId>jboss-jaxws-api_2.3_spec</artifactId>
> <version>1.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.servlet</groupId>
> <artifactId>jboss-servlet-api_3.1_spec</artifactId>
> <version>1.0.2.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.transaction</groupId>
> <artifactId>jboss-transaction-api_1.2_spec</artifactId>
> <version>1.1.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.xml.bind</groupId>
> <artifactId>jboss-jaxb-api_2.3_spec</artifactId>
> <version>1.0.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.slf4j</groupId>
> <artifactId>slf4j-api</artifactId>
> <version>1.7.22.jbossorg-1</version>
> </dependency>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (TEIID-5594) Use generic rather than jboss javax dependencies for teiid core
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5594?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-5594:
------------------------------------
regarding:
{code}
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.7.22.jbossorg-1</version>
{code}
replacing with bom:
{code}
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-api</artifactId>
<version>2.11.1</version>
{code}
> Use generic rather than jboss javax dependencies for teiid core
> ---------------------------------------------------------------
>
> Key: TEIID-5594
> URL: https://issues.jboss.org/browse/TEIID-5594
> Project: Teiid
> Issue Type: Sub-task
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 12.1
>
>
> The following dependencies are aligned to Wildfly, but that is unnecessary for embedded/springboot. They should be replaced with more generic versions.
> {code}
> <dependency>
> <groupId>org.jboss.spec.javax.ws.rs</groupId>
> <artifactId>jboss-jaxrs-api_2.1_spec</artifactId>
> <version>1.0.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.xml.ws</groupId>
> <artifactId>jboss-jaxws-api_2.3_spec</artifactId>
> <version>1.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.servlet</groupId>
> <artifactId>jboss-servlet-api_3.1_spec</artifactId>
> <version>1.0.2.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.transaction</groupId>
> <artifactId>jboss-transaction-api_1.2_spec</artifactId>
> <version>1.1.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.xml.bind</groupId>
> <artifactId>jboss-jaxb-api_2.3_spec</artifactId>
> <version>1.0.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.slf4j</groupId>
> <artifactId>slf4j-api</artifactId>
> <version>1.7.22.jbossorg-1</version>
> </dependency>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (TEIID-5561) Prevent alias collisions with built-in odata schema
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5561?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5561:
---------------------------------------
Core should also be reserved.
To reproduce the problem, use a schema named teiid, then exceptions will arise when fetching the metadata as the annotation terms will no longer be known.
> Prevent alias collisions with built-in odata schema
> ---------------------------------------------------
>
> Key: TEIID-5561
> URL: https://issues.jboss.org/browse/TEIID-5561
> Project: Teiid
> Issue Type: Quality Risk
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> It is problematic to have a Teiid model/schema with the name:
> olingo-extensions
> teiid
> edm
> as that will use an alias that conflicts with built-in handling. We should provide an error/warning as appropriate or come up with the logic to introduce a non-conflicting alias.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (TEIID-5595) Solve the maven duplicate PartSupplier.vdb issue
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5595?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5595.
-----------------------------------
Resolution: Done
Merged Van's PR, which just renamed the one of them. We may want to consider differentiating between stuff that gets into the classpath and stuff that's used from the file system - currently even if we only use file references to get at stuff in test resources, they will end up in the test-jar.
> Solve the maven duplicate PartSupplier.vdb issue
> ------------------------------------------------
>
> Key: TEIID-5595
> URL: https://issues.jboss.org/browse/TEIID-5595
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 12.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Trivial
> Fix For: 12.1
>
>
> When changing to use the basebom, it triggered a duplicate artifiact issue with PartsSupplier.vdb between the metadata project and the connector projects. If its the exact same vdb, then the connector vdb could be removed. Otherwise, I would suggest the connectors rename their vdb and fix the related dependent tests.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (TEIID-5599) When creating an entity via POST message, it is expected, that the returned message includes the primary key of the newly created instance. This is not the case currently
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5599?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5599.
-----------------------------------
Fix Version/s: 11.2.2
12.0.1
Resolution: Done
Updated the logic to check whether a missing value is used in the checked condition or not and provide a more informative error if it is.
> When creating an entity via POST message, it is expected, that the returned message includes the primary key of the newly created instance. This is not the case currently
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-5599
> URL: https://issues.jboss.org/browse/TEIID-5599
> Project: Teiid
> Issue Type: Bug
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 12.1, 11.2.2, 12.0.1
>
>
> The following communication shows the issue. What I am doing here is to create a new Account entity via post request. My underlaying mysql database requires the primary key in the table to be set to NN (not null), hence, a value must be provided. Moreover the primary key is set to autoincrement and is generated by the database. The only execepted value here seems to be, to provide the key with value=0. The object is created in the database as expected. However, Teiid answers with the created object, but again with the primary key (idProfile) set as zero, instead to provide the newly created primary key.
> POST Account HTTP/1.1
> Accept:application/json;odata.metadata=minimal;IEEE754Compatible=true
> Accept-Language:de-DE
> Content-Type:application/json;charset=UTF-8;IEEE754Compatible=true
> {"uuidUser":"65820574-7525-463b-9d20-5ee133a06b94","idProfile":"0"}
> --batch_id-1547485733072-21
> Content-Type:application/http
> Content-Transfer-Encoding:binary
> The response:
> HTTP/1.1 201 Created
> Location: http://localhost/odata4/svc/my_nutri_diary/Account(0)
> Content-Type: application/json;ieee754compatible=true;odata.metadata=minimal
> Content-Length: 147
> {"@odata.context":"http://localhost/odata4/svc/my_nutri_diary/$metadata#Account","idProfile":"0","uuidUser":"65820574-7525-463b-9d20-5ee133a06b94"}
> --batch_e834eb7c-df0d-4e22-a423-78cd3638955f
> Content-Type: application/http
> Content-Transfer-Encoding: binary
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (TEIID-5594) Use generic rather than jboss javax dependencies for teiid core
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5594?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-5594:
------------------------------------
regarding:
{code}
<groupId>org.jboss.spec.javax.servlet</groupId>
<artifactId>jboss-servlet-api_3.1_spec</artifactId>
<version>1.0.2.Final</version>
{code}
replacing with bom:
{code}
<groupId>javax.servlet</groupId>
<artifactId>javax.servlet-api</artifactId>
<version>4.0.1</version>
{code}
> Use generic rather than jboss javax dependencies for teiid core
> ---------------------------------------------------------------
>
> Key: TEIID-5594
> URL: https://issues.jboss.org/browse/TEIID-5594
> Project: Teiid
> Issue Type: Sub-task
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 12.1
>
>
> The following dependencies are aligned to Wildfly, but that is unnecessary for embedded/springboot. They should be replaced with more generic versions.
> {code}
> <dependency>
> <groupId>org.jboss.spec.javax.ws.rs</groupId>
> <artifactId>jboss-jaxrs-api_2.1_spec</artifactId>
> <version>1.0.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.xml.ws</groupId>
> <artifactId>jboss-jaxws-api_2.3_spec</artifactId>
> <version>1.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.servlet</groupId>
> <artifactId>jboss-servlet-api_3.1_spec</artifactId>
> <version>1.0.2.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.transaction</groupId>
> <artifactId>jboss-transaction-api_1.2_spec</artifactId>
> <version>1.1.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.xml.bind</groupId>
> <artifactId>jboss-jaxb-api_2.3_spec</artifactId>
> <version>1.0.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.slf4j</groupId>
> <artifactId>slf4j-api</artifactId>
> <version>1.7.22.jbossorg-1</version>
> </dependency>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (TEIID-5606) Deprecate project-integration-bom repo
by Van Halbert (Jira)
Van Halbert created TEIID-5606:
----------------------------------
Summary: Deprecate project-integration-bom repo
Key: TEIID-5606
URL: https://issues.jboss.org/browse/TEIID-5606
Project: Teiid
Issue Type: Task
Reporter: Van Halbert
Assignee: Steven Hawkins
Deprecate the project-integration-bom repo. Now that its no longer referenced in 12.x or 11.2, this repo should be flagged as no longer being used.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months