[JBoss JIRA] (TEIID-5672) When using DateTime datatype with millisecond fractions, i.e DateTime(3) the resulting urls for the records are invalid
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5672?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5672:
-------------------------------------
In my test, I see the microseconds passed through the OData URL is making all the way to the translator layer correctly. So, unless query yields no rows you should not get 404. In your case that is not true.
can you turn on the logging on the "org.teiid.COMMAND_LOG" to "TRACE" and see what the query that Teiid is sending to your MySQL? You should see a log statement with "source-specific" pretext. Then once you have that, take that and execute directly with a SQL client against your MySQL and see if you are getting any results?
> When using DateTime datatype with millisecond fractions, i.e DateTime(3) the resulting urls for the records are invalid
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-5672
> URL: https://issues.jboss.org/browse/TEIID-5672
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 11.2.1
> Environment: Docker Container
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Major
> Attachments: Bildschirmfoto 2019-03-04 um 20.47.19.png
>
>
> I am using a composite key based on a BIGINT and a DATETIME(3) value. The URLs which Teiid generates are invalid in this case. When using DATETIME(0) the links or ok. Example of generated record structure
> {code:java}
> <a:feed xmlns:a="http://www.w3.org/2005/Atom" xmlns:m="http://docs.oasis-open.org/odata/ns/metadata" xmlns:d="http://docs.oasis-open.org/odata/ns/data" m:context="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/$metadata#Diary">
> <a:id>
> https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary
> </a:id>
> <a:entry>
> <a:id>
> https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad...
> </a:id>
> <a:title/>
> <a:summary/>
> <a:updated>2019-03-03T17:53:52Z</a:updated>
> <a:author>
> <a:name/>
> </a:author>
> <a:link rel="edit" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:link rel="http://docs.oasis-open.org/odata/ns/related/fkDiaryToAccount" title="fkDiaryToAccount" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:link rel="http://docs.oasis-open.org/odata/ns/related/fkDiaryToFDBProducts" title="fkDiaryToFDBProducts" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:link rel="http://docs.oasis-open.org/odata/ns/relatedlinks/fkDiaryToAccount" title="fkDiaryToAccount" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:link rel="http://docs.oasis-open.org/odata/ns/relatedlinks/fkDiaryToFDBProducts" title="fkDiaryToFDBProducts" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:category scheme="http://docs.oasis-open.org/odata/ns/scheme" term="#svc.1.my_nutri_diary.Diary"/>
> <a:content type="application/xml">
> <m:properties>
> <d:fkProfile m:type="Int64">2</d:fkProfile>
> <d:AddedDateTime m:type="DateTimeOffset">2019-03-03T17:53:12.676Z</d:AddedDateTime>
> <d:fkIdCode m:type="Int64">1772</d:fkIdCode>
> <d:product_name>Mélange fruits secs</d:product_name>
> <d:brands>Agrosourcing</d:brands>
> <d:DatabaseID m:type="Int16">0</d:DatabaseID>
> <d:MealNumber>5</d:MealNumber>
> <d:AmountInG m:type="Double">100.0</d:AmountInG>
> <d:Calories m:type="Double">0.0</d:Calories>
> <d:ProteinsInG m:type="Double">-1.0</d:ProteinsInG>
> <d:CarbohydratesInG m:type="Double">-1.0</d:CarbohydratesInG>
> <d:SugarsInG m:type="Double">-1.0</d:SugarsInG>
> <d:FatsInG m:type="Double">-1.0</d:FatsInG>
> <d:SaturatedFatsInG m:type="Double">-1.0</d:SaturatedFatsInG>
> <d:SaltsInG m:type="Double">-1.0</d:SaltsInG>
> <d:Diarycol m:null="true"/>
> </m:properties>
> </a:content>
> </a:entry>
> {code}
> When I navigate to
> https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad...
> I get HTTP ERROR 404 page not found. Note: I replaced ":"with "%3A" (urlencode) in the url which was required to work with the DateTime(0) primary keys. But this did not help either.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIIDSB-46) Support override translators
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-46?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIIDSB-46.
---------------------------------
Resolution: Done
> Support override translators
> ----------------------------
>
> Key: TEIIDSB-46
> URL: https://issues.jboss.org/browse/TEIIDSB-46
> Project: Teiid Spring Boot
> Issue Type: Enhancement
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.0.3
>
>
> Override translators will need supported especially for migration scenarios. By default the current logic will map ddl overrides to the corresponding vdb xml equivalents, which will then trigger a failure to deploy. So things will need to be overriden to map the override to actually installing the translator (there is already an EmbeddedServer method for that given a translator type and properties).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIIDSB-49) OData does not select the virtual model as the default one to expose
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-49?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIIDSB-49.
---------------------------------
Fix Version/s: 1.0.3
Resolution: Done
> OData does not select the virtual model as the default one to expose
> --------------------------------------------------------------------
>
> Key: TEIIDSB-49
> URL: https://issues.jboss.org/browse/TEIIDSB-49
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: OData
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.0.3
>
>
> When OData interface is created the default schema that exposed at root "/" is not any virtual model defined but the very first source model.
> In implicit based VDBs the implicit virtual model "teiid" is exposed at root and it is the only single virtual model. Also going forward in Syndesis there is only going to be a single virtual model in a VDB. In the case of legacy VDB there can be multiple virtual models.
> To match with the implicit vdb, any VDB with a single virtual model, the virtual model should be exposed at the root. If there are more than single virtual model, then user is advised to use the OData interface using the "/schema-name/entiry" in the URL path. In case of multiple virtual vdbs, the behavior is unknown.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5673) OData does not select the virtual model as the default one to expose
by Ramesh Reddy (Jira)
Ramesh Reddy created TEIID-5673:
-----------------------------------
Summary: OData does not select the virtual model as the default one to expose
Key: TEIID-5673
URL: https://issues.jboss.org/browse/TEIID-5673
Project: Teiid
Issue Type: Bug
Components: OData
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
When OData interface is created the default schema that exposed at root "/" is not any virtual model defined but the very first source model.
In implicit based VDBs the implicit virtual model "teiid" is exposed at root and it is the only single virtual model. Also going forward in Syndesis there is only going to be a single virtual model in a VDB. In the case of legacy VDB there can be multiple virtual models.
To match with the implicit vdb, any VDB with a single virtual model, the virtual model should be exposed at the root. If there are more than single virtual model, then user is advised to use the OData interface using the "/schema-name/entiry" in the URL path. In case of multiple virtual vdbs, the behavior is unknown.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIIDSB-49) OData does not select the virtual model as the default one to expose
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-49?page=com.atlassian.jira.plugin... ]
Ramesh Reddy moved TEIID-5673 to TEIIDSB-49:
--------------------------------------------
Project: Teiid Spring Boot (was: Teiid)
Key: TEIIDSB-49 (was: TEIID-5673)
Component/s: OData
(was: OData)
> OData does not select the virtual model as the default one to expose
> --------------------------------------------------------------------
>
> Key: TEIIDSB-49
> URL: https://issues.jboss.org/browse/TEIIDSB-49
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: OData
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Major
>
> When OData interface is created the default schema that exposed at root "/" is not any virtual model defined but the very first source model.
> In implicit based VDBs the implicit virtual model "teiid" is exposed at root and it is the only single virtual model. Also going forward in Syndesis there is only going to be a single virtual model in a VDB. In the case of legacy VDB there can be multiple virtual models.
> To match with the implicit vdb, any VDB with a single virtual model, the virtual model should be exposed at the root. If there are more than single virtual model, then user is advised to use the OData interface using the "/schema-name/entiry" in the URL path. In case of multiple virtual vdbs, the behavior is unknown.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5672) When using DateTime datatype with millisecond fractions, i.e DateTime(3) the resulting urls for the records are invalid
by Christoph John (Jira)
[ https://issues.jboss.org/browse/TEIID-5672?page=com.atlassian.jira.plugin... ]
Christoph John commented on TEIID-5672:
---------------------------------------
Well, I believe that the second one is the more likely case. For DateTime(3) the objects are at least correctly written into the database. With SAPUI5 I can also bind to the collection with DATATIME(3) entities in it. The binding pathes hold the millisecon fractions as well. So my hope is that topic one is not the issue. Let me know when I can help with testing.
> When using DateTime datatype with millisecond fractions, i.e DateTime(3) the resulting urls for the records are invalid
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-5672
> URL: https://issues.jboss.org/browse/TEIID-5672
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 11.2.1
> Environment: Docker Container
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Major
> Attachments: Bildschirmfoto 2019-03-04 um 20.47.19.png
>
>
> I am using a composite key based on a BIGINT and a DATETIME(3) value. The URLs which Teiid generates are invalid in this case. When using DATETIME(0) the links or ok. Example of generated record structure
> {code:java}
> <a:feed xmlns:a="http://www.w3.org/2005/Atom" xmlns:m="http://docs.oasis-open.org/odata/ns/metadata" xmlns:d="http://docs.oasis-open.org/odata/ns/data" m:context="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/$metadata#Diary">
> <a:id>
> https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary
> </a:id>
> <a:entry>
> <a:id>
> https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad...
> </a:id>
> <a:title/>
> <a:summary/>
> <a:updated>2019-03-03T17:53:52Z</a:updated>
> <a:author>
> <a:name/>
> </a:author>
> <a:link rel="edit" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:link rel="http://docs.oasis-open.org/odata/ns/related/fkDiaryToAccount" title="fkDiaryToAccount" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:link rel="http://docs.oasis-open.org/odata/ns/related/fkDiaryToFDBProducts" title="fkDiaryToFDBProducts" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:link rel="http://docs.oasis-open.org/odata/ns/relatedlinks/fkDiaryToAccount" title="fkDiaryToAccount" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:link rel="http://docs.oasis-open.org/odata/ns/relatedlinks/fkDiaryToFDBProducts" title="fkDiaryToFDBProducts" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:category scheme="http://docs.oasis-open.org/odata/ns/scheme" term="#svc.1.my_nutri_diary.Diary"/>
> <a:content type="application/xml">
> <m:properties>
> <d:fkProfile m:type="Int64">2</d:fkProfile>
> <d:AddedDateTime m:type="DateTimeOffset">2019-03-03T17:53:12.676Z</d:AddedDateTime>
> <d:fkIdCode m:type="Int64">1772</d:fkIdCode>
> <d:product_name>Mélange fruits secs</d:product_name>
> <d:brands>Agrosourcing</d:brands>
> <d:DatabaseID m:type="Int16">0</d:DatabaseID>
> <d:MealNumber>5</d:MealNumber>
> <d:AmountInG m:type="Double">100.0</d:AmountInG>
> <d:Calories m:type="Double">0.0</d:Calories>
> <d:ProteinsInG m:type="Double">-1.0</d:ProteinsInG>
> <d:CarbohydratesInG m:type="Double">-1.0</d:CarbohydratesInG>
> <d:SugarsInG m:type="Double">-1.0</d:SugarsInG>
> <d:FatsInG m:type="Double">-1.0</d:FatsInG>
> <d:SaturatedFatsInG m:type="Double">-1.0</d:SaturatedFatsInG>
> <d:SaltsInG m:type="Double">-1.0</d:SaltsInG>
> <d:Diarycol m:null="true"/>
> </m:properties>
> </a:content>
> </a:entry>
> {code}
> When I navigate to
> https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad...
> I get HTTP ERROR 404 page not found. Note: I replaced ":"with "%3A" (urlencode) in the url which was required to work with the DateTime(0) primary keys. But this did not help either.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5618) clientHostName always reported as localhost via JDBC connection
by Johnathon Lee (Jira)
[ https://issues.jboss.org/browse/TEIID-5618?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-5618:
---------------------------------
Fix Version/s: 8.12.17.6_4
> clientHostName always reported as localhost via JDBC connection
> ---------------------------------------------------------------
>
> Key: TEIID-5618
> URL: https://issues.jboss.org/browse/TEIID-5618
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.12.16.6_4
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 8.12.17.6_4, 12.1
>
>
> VDB session information in the Management Console and logs shows localhost for Client Host Name with a JDBC connection.
> Client Host Name: localhost
> Client Hardware Address: 4CBB58502284
> IP Address:
> Security Domain: teiid-security
> In the server.log with org.teiid set to TRACE it displays below for session:
> DEBUG [org.teiid.SECURITY] (New I/O worker #2) Logon successful, created session: sessionid=DW9hzUw5P1ob; userName=teiidUser@teiid-security; vdbName=deb_pg; vdbVersion=2; createdTime=Thu Jan 17 08:15:44 CST 2019; applicationName=JDBC; clientHostName=localhost; clientHardwareAddress=4CBB58502284; IPAddress=192.168.x.x; securityDomain=teiid-security; lastPingTime=Thu Jan 17 08:15:44 CST 2019
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5618) clientHostName always reported as localhost via JDBC connection
by RH Bugzilla Integration (Jira)
[ https://issues.jboss.org/browse/TEIID-5618?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-5618:
------------------------------------------------
jolee(a)redhat.com changed the Status of [bug 1668367|https://bugzilla.redhat.com/show_bug.cgi?id=1668367] from NEW to MODIFIED
> clientHostName always reported as localhost via JDBC connection
> ---------------------------------------------------------------
>
> Key: TEIID-5618
> URL: https://issues.jboss.org/browse/TEIID-5618
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.12.16.6_4
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> VDB session information in the Management Console and logs shows localhost for Client Host Name with a JDBC connection.
> Client Host Name: localhost
> Client Hardware Address: 4CBB58502284
> IP Address:
> Security Domain: teiid-security
> In the server.log with org.teiid set to TRACE it displays below for session:
> DEBUG [org.teiid.SECURITY] (New I/O worker #2) Logon successful, created session: sessionid=DW9hzUw5P1ob; userName=teiidUser@teiid-security; vdbName=deb_pg; vdbVersion=2; createdTime=Thu Jan 17 08:15:44 CST 2019; applicationName=JDBC; clientHostName=localhost; clientHardwareAddress=4CBB58502284; IPAddress=192.168.x.x; securityDomain=teiid-security; lastPingTime=Thu Jan 17 08:15:44 CST 2019
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIID-5672) When using DateTime datatype with millisecond fractions, i.e DateTime(3) the resulting urls for the records are invalid
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5672?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5672:
-------------------------------------
So, there may be a couple of issues then
* one, handling higher precision timestamps not supported in translators to support micro/nano second level
* second, in OData layer not able correctly resolve the time with milli-second precision.
Will write an example to duplicate at least for the second issue, I guess first once simply truncates perhaps.
> When using DateTime datatype with millisecond fractions, i.e DateTime(3) the resulting urls for the records are invalid
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-5672
> URL: https://issues.jboss.org/browse/TEIID-5672
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 11.2.1
> Environment: Docker Container
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Major
> Attachments: Bildschirmfoto 2019-03-04 um 20.47.19.png
>
>
> I am using a composite key based on a BIGINT and a DATETIME(3) value. The URLs which Teiid generates are invalid in this case. When using DATETIME(0) the links or ok. Example of generated record structure
> {code:java}
> <a:feed xmlns:a="http://www.w3.org/2005/Atom" xmlns:m="http://docs.oasis-open.org/odata/ns/metadata" xmlns:d="http://docs.oasis-open.org/odata/ns/data" m:context="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/$metadata#Diary">
> <a:id>
> https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary
> </a:id>
> <a:entry>
> <a:id>
> https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad...
> </a:id>
> <a:title/>
> <a:summary/>
> <a:updated>2019-03-03T17:53:52Z</a:updated>
> <a:author>
> <a:name/>
> </a:author>
> <a:link rel="edit" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:link rel="http://docs.oasis-open.org/odata/ns/related/fkDiaryToAccount" title="fkDiaryToAccount" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:link rel="http://docs.oasis-open.org/odata/ns/related/fkDiaryToFDBProducts" title="fkDiaryToFDBProducts" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:link rel="http://docs.oasis-open.org/odata/ns/relatedlinks/fkDiaryToAccount" title="fkDiaryToAccount" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:link rel="http://docs.oasis-open.org/odata/ns/relatedlinks/fkDiaryToFDBProducts" title="fkDiaryToFDBProducts" href="https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad..."/>
> <a:category scheme="http://docs.oasis-open.org/odata/ns/scheme" term="#svc.1.my_nutri_diary.Diary"/>
> <a:content type="application/xml">
> <m:properties>
> <d:fkProfile m:type="Int64">2</d:fkProfile>
> <d:AddedDateTime m:type="DateTimeOffset">2019-03-03T17:53:12.676Z</d:AddedDateTime>
> <d:fkIdCode m:type="Int64">1772</d:fkIdCode>
> <d:product_name>Mélange fruits secs</d:product_name>
> <d:brands>Agrosourcing</d:brands>
> <d:DatabaseID m:type="Int16">0</d:DatabaseID>
> <d:MealNumber>5</d:MealNumber>
> <d:AmountInG m:type="Double">100.0</d:AmountInG>
> <d:Calories m:type="Double">0.0</d:Calories>
> <d:ProteinsInG m:type="Double">-1.0</d:ProteinsInG>
> <d:CarbohydratesInG m:type="Double">-1.0</d:CarbohydratesInG>
> <d:SugarsInG m:type="Double">-1.0</d:SugarsInG>
> <d:FatsInG m:type="Double">-1.0</d:FatsInG>
> <d:SaturatedFatsInG m:type="Double">-1.0</d:SaturatedFatsInG>
> <d:SaltsInG m:type="Double">-1.0</d:SaltsInG>
> <d:Diarycol m:null="true"/>
> </m:properties>
> </a:content>
> </a:entry>
> {code}
> When I navigate to
> https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary(fkProfile=2,Ad...
> I get HTTP ERROR 404 page not found. Note: I replaced ":"with "%3A" (urlencode) in the url which was required to work with the DateTime(0) primary keys. But this did not help either.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (TEIIDSB-19) Create Portfolio Example
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-19?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIIDSB-19.
---------------------------------
Resolution: Done
> Create Portfolio Example
> ------------------------
>
> Key: TEIIDSB-19
> URL: https://issues.jboss.org/browse/TEIIDSB-19
> Project: Teiid Spring Boot
> Issue Type: Task
> Components: OpenShift
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.0.3
>
>
> - Portfolio example project that includes a representative sample of all resources a user might interact with (application.properties, VDB DDL, data source definitions, beans, etc.)
> - Portfolio example project delivered via GitHub
> - README documentation instructing a user on how to build and deploy Portfolio example
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month