[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 Christoph John (Jira)
[ https://issues.jboss.org/browse/TEIID-5599?page=com.atlassian.jira.plugin... ]
Christoph John commented on TEIID-5599:
---------------------------------------
Hello Steven,
thanks for the info.
> 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
>
>
> 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-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 commented on TEIID-5599:
---------------------------------------
This is coming from the Account condition. I should be able to produce a better error message for that though.
If you don't need it enforced for the insert, set the constraint flag to false - see http://teiid.github.io/teiid-documents/master/content/reference/Permissio... Role Based Security and the example on http://teiid.github.io/teiid-documents/master/content/reference/XML_Defin... - if you do that, you should be able to confirm that your scenario works.
However this is generally a bug - we should evaluate the condition even without the idProfile.
> 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
>
>
> 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.xml.ws</groupId>
<artifactId>jboss-jaxws-api_2.3_spec</artifactId>
<version>1.0.0.Final</version>
{code}
replacing with bom:
{code}
<groupId>javax.xml.ws</groupId>
<artifactId>jaxws-api</artifactId>
<version>2.3.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-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 edited comment on TEIID-5594 at 1/16/19 9:27 AM:
-------------------------------------------------------------
regarding:
{code}
<groupId>org.jboss.spec.javax.transaction</groupId>
<artifactId>jboss-transaction-api_1.2_spec</artifactId>
<version>1.1.1.Final</version>
{code}
replacing with:
{code}
<groupId>javax.transaction</groupId>
<artifactId>javax.transaction-api</artifactId>
<version>1.3</version>
{code}
was (Author: van.halbert):
regarding:
{code}
<groupId>org.jboss.spec.javax.transaction</groupId>
<artifactId>jboss-transaction-api_1.2_spec</artifactId>
<version>1.1.1.Final</version>
{code}
replacing with bom:
{code}
<groupId>javax.transaction</groupId>
<artifactId>javax.transaction-api</artifactId>
<version>1.3</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-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... ]
Work on TEIID-5599 started by Steven Hawkins.
---------------------------------------------
> 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
>
>
> 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-5593) Add a Java 11 travis build
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5593?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5593.
-----------------------------------
Fix Version/s: 12.0.1
Resolution: Done
Merged Van's commit and updated the arquillian tests to not run at all for java 11+. We'll revisit that in Teiid 13.
> Add a Java 11 travis build
> --------------------------
>
> Key: TEIID-5593
> URL: https://issues.jboss.org/browse/TEIID-5593
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Van Halbert
> Priority: Major
> Fix For: 12.1, 12.0.1
>
>
> We should also build/test with java 11 on travis. This is expected to work for everything but the arquillian tests.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (TEIID-5593) Add a Java 11 travis build
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5593?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5593:
---------------------------------------
>From the build and the docs confirm that matrix is in addition to any combination of jobs created by the runtime/environment. So I've made a couple of changes to remove the matrix, and to update the pom to not run the arquillian tests when running java 11 - that makes the travis file a little simpler.
> Add a Java 11 travis build
> --------------------------
>
> Key: TEIID-5593
> URL: https://issues.jboss.org/browse/TEIID-5593
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Van Halbert
> Priority: Major
> Fix For: 12.1
>
>
> We should also build/test with java 11 on travis. This is expected to work for everything but the arquillian tests.
--
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 updated TEIID-5595:
----------------------------------
Fix Version/s: 12.1
> 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-5541) Incorrect parsing of xml with XmlTable
by Johnathon Lee (Jira)
[ https://issues.jboss.org/browse/TEIID-5541?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-5541:
---------------------------------
Fix Version/s: 8.12.17.6_4
> Incorrect parsing of xml with XmlTable
> --------------------------------------
>
> Key: TEIID-5541
> URL: https://issues.jboss.org/browse/TEIID-5541
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 11.1
> Environment: teiid-11.1.0 (from 01.09.2018) on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 11.0.3, 11.1.2, 12.0, 11.2.1, 8.12.17.6_4
>
>
> Running the query:
> {code:sql}
> Begin
> Declare xml xcontent = '<root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <report>
> <data>
> <year xsi:type="decimal">2018</year>
> </data>
> </report>
> <waitSeconds xsi:type="decimal">13</waitSeconds>
> </root>' ;
> Select *
> From
> XmlTable(
> XmlNamespaces ('http://www.w3.org/2001/XMLSchema-instance' as xsi),
> '/root/report/data'
> PASSING xcontent
> Columns
> "year" integer,
> waitSeconds xml Path 'root()/root/waitSeconds',
> waitSecondsStr string Path 'root()/root/waitSeconds'
> )a ;
> End ;;
> {code}
> and having a look at the structure we can see that the value 13 should be returned, while the value is not picked from xml for result.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months