[
https://jira.jboss.org/jira/browse/TEIID-808?page=com.atlassian.jira.plug...
]
Ted Jones resolved TEIID-808.
-----------------------------
Resolution: Done
Verified that this is no longer an issue since we are running in JBossAS, however we are
not using JMX since we are dealing with the profile service directly.
Revisit the prior issues with extending the JOPR JMX plugin and
verify if the problems have been fixed
------------------------------------------------------------------------------------------------------
Key: TEIID-808
URL:
https://jira.jboss.org/jira/browse/TEIID-808
Project: Teiid
Issue Type: Sub-task
Components: Jopr Plugin
Affects Versions: 7.0
Reporter: Van Halbert
Assignee: Ted Jones
Fix For: 7.0
In the development of the tech preview of MetaMatrix 5.5.3 version, it was determined
that the JOPR JMX plugin had issues that did not enable us to extend for our use. This
needs to be revisited because this is our first choice for discovering datasources (since
JOPR is already doing it). We need to perform a filtering process which requires us to
be able to discover and then interrogate the properties in order to determine if this is a
Teiid datasource.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira