[
https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on TEIID-2650:
-----------------------------------------
Note that the Teiid subsystem should not be registering this attribute on host
controllers, since those processes cannot provide the information.
When the Teiid Extension is initialized by the Host Controller, an ExtensionContext is
passed in. ExtensionContenxt.getProcessType() allows the extension to know what type of
process it is running in (DOMAIN_SERVER, EMBEDDED_SERVER, STANDALONE_SERVER,
HOST_CONTROLLER, APPLICATION_CLIENT) so it can use that information to control what
resources/attributes/operations it registers. Items that don't make sense for the
given process type shouldn't be registered.
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