[
https://issues.jboss.org/browse/TEIIDDES-2064?page=com.atlassian.jira.plu...
]
Paul Richardson resolved TEIIDDES-2064.
---------------------------------------
Resolution: Done
Changes made:
* Upon connection the teiid instance model in Designer updates the version number from the
teiid instance itself
* The teiid instance editor allows editing of the version number when the instance is
stopped but not only is it updated upon connection but the field becomes read-only since
the instance has told the client what it is rather than a manual guess by the user.
Issues with 8.4 Designers handling of Teiid 8.6 Runtime version
---------------------------------------------------------------
Key: TEIIDDES-2064
URL:
https://issues.jboss.org/browse/TEIIDDES-2064
Project: Teiid Designer
Issue Type: Bug
Components: Teiid Integration
Affects Versions: 8.4
Reporter: Barry LaFond
Assignee: Paul Richardson
Priority: Blocker
Fix For: 8.4
* Teiid Designer code-base reflects Teiid 8.6 runtime codebase.
* Creating a New Server based on EAP 6.1 Alpha 1 with Teiid 8.6 installed results in a
TeiidServer who's version is 8.4.0 because
TeiidJboss7ServerUtil.getTeiidRuntimeVersion() is returning the DEFAULT_TEIID_8_SERVER
which is currently set to 8.4.0 because the server isn't started.
* Once I start the server I would expect that the server version would be discovered from
the actual server connection and re-set to it's real 8.6.0 version, but it's not,
it remains at 8.4.0
* Note we haven't addressed the this use-case fully.
* VDB's are tagged with a Teiid runtime validation version
* If no server is running, should the default Teiid version be set to an actual Default
version rather than the last selected TeiidServer version value?
--
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