Bug 780117 (SOA-2486) - Data Source Explorer in JBDS does not show content of JDBC accessed ModeShape
Summary: Data Source Explorer in JBDS does not show content of JDBC accessed ModeShape
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-2486
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Tooling
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-27 13:49 UTC by Jiri Pechanec
Modified: 2013-05-07 19:20 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 780118 (view as bug list)
Environment:
Last Closed: 2011-12-06 22:01:37 UTC
Type: Bug


Attachments (Terms of Use)
Screenshot-1.png (160.24 KB, image/png)
2010-10-27 13:50 UTC, Jiri Pechanec
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2486 0 Major Closed Data Source Explorer in JBDS does not show content of JDBC accessed ModeShape 2014-07-29 09:50:03 UTC

Description Jiri Pechanec 2010-10-27 13:49:43 UTC
project_key: SOA

Data Explorer does not show the contents of ModeShape. Data Explorer seems to be using path -> Catalog -> Schema -> View -> ModeShape elements.

It seems that ModeShape JDBC driver does not support call of getSchema.

See attached screenshot for differences between ModeShape exploring and PostgreSQL exploring

Comment 1 Jiri Pechanec 2010-10-27 13:50:25 UTC
Attachment: Added: Screenshot-1.png


Comment 2 Van Halbert 2010-10-27 14:25:18 UTC
We have a usability issue regarding its usage in the first release.   The driver, in JBDS, is only usable when importing metadata to build a Teiid Model that will be deployed to EDS.    Outside of that, it's not usable.      

There are similar limitations of other connection profiles (i.e.,  webservices, salesforce).   

With that said, the driver could be fixed to at least support the methods to show the metadata in the data explorer, but it will still not support querying the data from a remote client.




Comment 3 Ken Johnson 2010-10-27 20:02:58 UTC
 Right. Users are not expected to be able to query ModeShape directly through the modeshape connection profile. To query ModeShape from Data Tools or any out-of-process client, you need to go through Teiid. MS supports remote metadata calls but data calls must be in-process. Therefore Teiid running in the same VM as ModeShape can act as a proxy and provide a remote JDBC/ODBC interface to MS via a VDB. 

In the future MS will support direct remote JDBC connections. In the meantime this behavior is expected and should be documented. 

Comment 4 Van Halbert 2010-10-28 02:48:14 UTC
Changed status to Future as this will part of a scheduled enhancement

Comment 5 Van Halbert 2011-09-12 18:05:02 UTC
Link: Added: This issue depends MODE-872



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