[JBoss JIRA] (TEIIDSB-100) move static handling to the root context
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-100?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIIDSB-100.
------------------------------------
Resolution: Done
Moved static handling to the root and simplified the logic dealing with the baseurl. Also removed the authenticationinterceptor and the alt paths logic as they are no longer needed.
> move static handling to the root context
> ----------------------------------------
>
> Key: TEIIDSB-100
> URL: https://issues.jboss.org/browse/TEIIDSB-100
> Project: Teiid Spring Boot
> Issue Type: Quality Risk
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.2.0
>
>
> To prevent conflicts with entity and schema names, static handling should be moved to the root level:
> /odata/...
> /static/...
> rather than
> /odata/static
> It's also a good idea to fully restrict the resources that can be read as all xml files in the unified classpath are currently accessible.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (TEIID-5741) Upgrade to Thorntail 2.4
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5741?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5741:
---------------------------------------
Switched to Teiid 12.2 with thorntail 2.4 on my shawkins/teiid-thorntail with no problems. Tested starting with Java 11, and that worked just fine. Will hold off for Teiid 12.2.1 and then cut this release.
> Upgrade to Thorntail 2.4
> ------------------------
>
> Key: TEIID-5741
> URL: https://issues.jboss.org/browse/TEIID-5741
> Project: Teiid
> Issue Type: Feature Request
> Components: thorntail
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: tt-2.1.0
>
>
> As a likely terminal release, we should provide Java 11 support via Thorntail 2.4.
> Since 2.4 is based upon WildFly 15.0.1, this will likely be off of 12.2.x, rather than 12.3.x.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (TEIIDSB-101) OData issues with multiple visible schema
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-101?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIIDSB-101:
----------------------------------------
Yes, I know that syndesis won't use it. But we've left it as a grey are for just engine usage. Assumptions around what constitutes a default model also seem problematic.
> OData issues with multiple visible schema
> -----------------------------------------
>
> Key: TEIIDSB-101
> URL: https://issues.jboss.org/browse/TEIIDSB-101
> Project: Teiid Spring Boot
> Issue Type: Quality Risk
> Components: OData
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 1.2.0
>
>
> The odata logic accommodates a subcontext specifying the schema to access. Other logic however doesn't allow for this:
> * if multiple visible schema are exposed and have a cross reference, then the metadata links will be invalid as they are created based upon the Teiid Wildfly conventions.
> * The keycloak logic exposes /$metadata as unsecured, but any of the schema/$metadata links would require authentication.
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (TEIIDSB-101) OData issues with multiple visible schema
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-101?page=com.atlassian.jira.plugi... ]
Ramesh Reddy commented on TEIIDSB-101:
--------------------------------------
schema/$metadata model will not be used syndesis. But is there way pattern match to $metadata as endpoint would be good.
> OData issues with multiple visible schema
> -----------------------------------------
>
> Key: TEIIDSB-101
> URL: https://issues.jboss.org/browse/TEIIDSB-101
> Project: Teiid Spring Boot
> Issue Type: Quality Risk
> Components: OData
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 1.2.0
>
>
> The odata logic accommodates a subcontext specifying the schema to access. Other logic however doesn't allow for this:
> * if multiple visible schema are exposed and have a cross reference, then the metadata links will be invalid as they are created based upon the Teiid Wildfly conventions.
> * The keycloak logic exposes /$metadata as unsecured, but any of the schema/$metadata links would require authentication.
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (TEIID-5710) Create remaining spring docs
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5710?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5710.
-----------------------------------
Resolution: Done
Marking the initial effort as resolved. The security guide is the only doc that has nothing of value to add to teiid-spring-boot as all configuration options and functionality has changed.
> Create remaining spring docs
> ----------------------------
>
> Key: TEIID-5710
> URL: https://issues.jboss.org/browse/TEIID-5710
> Project: Teiid
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> Presuming that the embedded, dev, and security docs will all be available as part of their respective code (javadocs and examples), that leaves admin, caching, and client-dev as the remaining books that need a spring specific spin.
> Most of the admin guide is not applicable - but we do need to capture somewhere all of the information related to system/env properties
> Most of the caching guide is TBD - but the sections on result set and other caching are still applicable.
> Most of the client guide is applicable to spring.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (TEIIDSB-101) OData issues with multiple visible schema
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-101:
--------------------------------------
Summary: OData issues with multiple visible schema
Key: TEIIDSB-101
URL: https://issues.jboss.org/browse/TEIIDSB-101
Project: Teiid Spring Boot
Issue Type: Quality Risk
Components: OData
Reporter: Steven Hawkins
Fix For: 1.2.0
The odata logic accommodates a subcontext specifying the schema to access. Other logic however doesn't allow for this:
* if multiple visible schema are exposed and have a cross reference, then the metadata links will be invalid as they are created based upon the Teiid Wildfly conventions.
* The keycloak logic exposes /$metadata as unsecured, but any of the schema/$metadata links would require authentication.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (TEIID-5757) Remove the need for the odata role
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5757:
-------------------------------------
Summary: Remove the need for the odata role
Key: TEIID-5757
URL: https://issues.jboss.org/browse/TEIID-5757
Project: Teiid
Issue Type: Quality Risk
Components: OData
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 12.3
Similar to TEIIDSB-85 the rationale for having an odata role no longer seems valid. It will simplify usage if that is no longer required.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (TEIID-5756) null session query output from PDI
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5756?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5756.
-----------------------------------
Resolution: Out of Date
Advised about disabling the server ping check.
> null session query output from PDI
> ----------------------------------
>
> Key: TEIID-5756
> URL: https://issues.jboss.org/browse/TEIID-5756
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Environment: Prod
> Reporter: CHANDAN BISHT
> Priority: Major
> Attachments: jdvapp1.tar.gz, jdvapp3.tar.gz, server.log.1
>
>
> User getting null session query executed from PDI tool.
> the session id tvgWrPf4oPvD
> 2019-02-04 09:21:42,987 [New I/O worker #39] WARN [org.teiid.PROCESSOR] TEIID40011 Processing exception 'TEIID40042 Invalid Session tvgWrPf4oPvD. Session may have already been terminated.' for session null. Exception type org.teiid.client.security.InvalidSessionException thrown from org.teiid.jboss.TransportService$2.invoke(TransportService.java:239).: org.teiid.client.security.InvalidSessionException: TEIID40042 Invalid Session tvgWrPf4oPvD. Session may have already been terminated.
> at org.teiid.jboss.TransportService$2.invoke(TransportService.java:239)
> at com.sun.proxy.$Proxy20.processCursorRequest(Unknown Source)
> at sun.reflect.GeneratedMethodAccessor152.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:87)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284)
> at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:231)
> at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:217)
> at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:216)
> at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88)
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
> at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
> at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:142)
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
> at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years