[JBoss JIRA] (TEIIDDES-2059) Preview VDB should contain only models needed for the preview
by Debbie Steigner (JIRA)
Debbie Steigner created TEIIDDES-2059:
-----------------------------------------
Summary: Preview VDB should contain only models needed for the preview
Key: TEIIDDES-2059
URL: https://issues.jboss.org/browse/TEIIDDES-2059
Project: Teiid Designer
Issue Type: Feature Request
Components: Data Preview
Affects Versions: 8.3
Reporter: Debbie Steigner
When doing a view data on a table, designer unnecessarily deploys a vdb for ALL models in the project instead of evaluating what is necessary for a particular table in a view model (where I've chosen to preview data)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIIDDES-2058) Allow an OpenShift instance as the default server
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2058?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-2058:
-----------------------------------------
We are close to being able to deploy DV to OpenShift from within Designer. "File > New > Other... > OpenShift > OpenShift application". This wizard connects to a users OpenShift account and allows cartridges to be deployed - resulting in an OpenShift 'server' being created in the ServersView. Currently it does not support 'downloadable' cartridges like us, but it is on the radar - https://issues.jboss.org/browse/JBDS-2865
Once the above JIRA is resolved, this would allow us to use the created OpenShift 'server' as a default instance. The other approach 'externally managed' would still work, but this seems equally valid.
> Allow an OpenShift instance as the default server
> -------------------------------------------------
>
> Key: TEIIDDES-2058
> URL: https://issues.jboss.org/browse/TEIIDDES-2058
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: VDB & Execution
> Affects Versions: 8.3.1
> Reporter: Mark Drilling
> Attachments: OpenShiftServerView.png
>
>
> The latest Dev Studio release has support for creating an OpenShift 'server', connection to an application deployed to OpenShift.
> We need to allow an OpenShift instance (with Teiid deployed) to be used as a default server in Designer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIIDDES-2058) Allow an OpenShift instance as the default server
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2058?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2058:
----------------------------------------
Can a user do this without installing Teiid up in the OpenShift first? If they have to install first, then how is this different from server view available from Dev Studio.
> Allow an OpenShift instance as the default server
> -------------------------------------------------
>
> Key: TEIIDDES-2058
> URL: https://issues.jboss.org/browse/TEIIDDES-2058
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: VDB & Execution
> Affects Versions: 8.3.1
> Reporter: Mark Drilling
> Attachments: OpenShiftServerView.png
>
>
> The latest Dev Studio release has support for creating an OpenShift 'server', connection to an application deployed to OpenShift.
> We need to allow an OpenShift instance (with Teiid deployed) to be used as a default server in Designer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIIDDES-2058) Allow an OpenShift instance as the default server
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-2058:
---------------------------------------
Summary: Allow an OpenShift instance as the default server
Key: TEIIDDES-2058
URL: https://issues.jboss.org/browse/TEIIDDES-2058
Project: Teiid Designer
Issue Type: Enhancement
Components: VDB & Execution
Affects Versions: 8.3.1
Reporter: Mark Drilling
The latest Dev Studio release has support for creating an OpenShift 'server', connection to an application deployed to OpenShift.
We need to allow an OpenShift instance (with Teiid deployed) to be used as a default server in Designer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIIDDES-2055) HTTP 406 Importing Generated REST Service as Source
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2055?page=com.atlassian.jira.plu... ]
Ted Jones edited comment on TEIIDDES-2055 at 2/18/14 11:31 AM:
---------------------------------------------------------------
This is due to TeiidXmlImportSourcePage hard-coding the Content-Type on the HttpConnection to application/xml. The generated REST service sets the charset and so the 406 is thrown. Changing TeiidXmlImportSourcePage to use Content-Type=application/xml;charset=MacRoman (in my case) fixes this. This will be an issue for any REST service that specifies anything other than application/xml. We should allow the user to override the HTTP Headers in the importer.
The REST Connection Profile should be modified to allow for name-value pairs of HTTP Headers. The user could then enter for example:
Header Name Header Value
Content-Type application/xml;charset=somecharset
This should overwrite our default value in TeiidXmlImportSourcePage which is "application/xml". If that value is entered by the user, the default should be used. The same would apply for the "Accept" header value.
was (Author: tejones):
This is due to TeiidXmlImportSourcePage hard-coding the Content-Type on the HttpConnection to application/xml. The generated REST service sets the charset and so the 406 is thrown. Changing TeiidXmlImportSourcePage to use Content-Type=application/xml;charset=MacRoman (in my case) fixes this. This will be an issue for any REST service that specifies anything other than application/xml. We should allow the user to override the HTTP Headers in the importer.
> HTTP 406 Importing Generated REST Service as Source
> ---------------------------------------------------
>
> Key: TEIIDDES-2055
> URL: https://issues.jboss.org/browse/TEIIDDES-2055
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.3.1
> Reporter: Ted Jones
> Assignee: Ted Jones
> Fix For: 8.4, 8.3.2
>
>
> I generated a REST service from Designer and then tried to use as a source. I received a 406 (Not acceptable) error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month