Bug 1036601 - JON Plugin doesn't publish any configuration information about Teiid VDBs nor Teiid
Summary: JON Plugin doesn't publish any configuration information about Teiid VDBs nor...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: JON
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: GA
: 6.0
Assignee: Van Halbert
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-02 10:42 UTC by Filip Nguyen
Modified: 2014-07-09 05:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When users are attempting to view VDB configuration using the JBoss Ooperations Network plugin for JBoss Data Virtualization, they are presented with the following message: "No configuration was retrieved. This means that either the plugin failed to load the configuration or that configuration collection is merely switched off in the connection settings."
Clone Of:
Environment:
Last Closed: 2014-03-10 19:50:17 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIIDRHQ-21 0 Major Resolved JON Plugin doesn't publish any configuration information about Teiid VDBs nor Teiid 2014-03-10 19:50:00 UTC

Description Filip Nguyen 2013-12-02 10:42:32 UTC
When trying to view VDB configuration it shows:

"No configuration was retrieved. This means that either the plugin failed to load the configuration or that configuration collection is merely switched off in the connection settings."

Comment 1 JBoss JIRA Server 2013-12-04 21:01:12 UTC
Ted Jones <tejones> updated the status of jira TEIIDRHQ-21 to Resolved

Comment 2 JBoss JIRA Server 2013-12-04 21:01:12 UTC
Ted Jones <tejones> made a comment on jira TEIIDRHQ-21

A property name change in Teiid (dynamic->xml-deployment) caused an NPE in the plugin while loading the configuration. Changed the name in the plugin to match the new name in Teiid.


Note You need to log in before you can comment on or make changes to this bug.