[
https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin...
]
Paul Richardson commented on TEIID-2650:
----------------------------------------
I think that the upgrading of teiid on a domain member server to a different version of
teiid to that on the domain master would be detrimental, would it not? For example, a new
version of teiid might add a new translator or change its name and since this would be
different from the master this would introduce a conflict.
Therefore, is it best to declare that teiid installations should remain uniform across a
domain?
Ramesh, what do you think?
A jboss server in domain mode does not advertise its teiid
runtime-version
--------------------------------------------------------------------------
Key: TEIID-2650
URL:
https://issues.jboss.org/browse/TEIID-2650
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.4
Reporter: Paul Richardson
Assignee: Ramesh Reddy
Priority: Blocker
Fix For: 8.4.1, 8.5
A standalone jboss server installed with teiid advertises its teiid runtime version at
the path /subsystem=teiid/runtime-version.
Likewise, a domain jboss server installed with teiid in the 'ha' profile should
advertise its runtime version at the path /profile=ha/subsystem=teiid/runtime-version.
However, whereas the standalone returns the correct value for this attribute, the domain
mode server fails, only returning 'undefined'.
This attribute is essential to designer in determining what version is the teiid
instance. This in turns determines the functionality of the modelling that is available
and which teiid client should be used for connection.
--
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