[jbosstools-issues] [JBoss JIRA] (JBDS-2852) Database/source/connection Usability
[
https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin....
]
Barry LaFond edited comment on JBDS-2852 at 5/16/14 2:38 PM:
-------------------------------------------------------------
Though we currently utilize Teiid's API to createDataSource(), my understanding is
Teiid uses server api's to actually deploy the DS and update the standalone.xml.
Theoretically Teiid Designer tooling could convert to use the server api vs the Teiid
api.
Note Designer is investigating what it would take to abstract DS management up a level
that could incorporate CPs and just know how to extract properties and deploy DS's.
Not an easy task considering the varying structures of our numerous data source types.
This work would play into a new integrated Data Source Wizard. We're more than willing
to collaborate :)
The server > Subsystems > datasources node seems like the logic place to provide
generic "Add/Remove/Edit Data Source" actions via a wizard dialog or editor.
Our Teiid Instance Configuration contributed tree node (actually a submodule) manages Data
Sources, Translators and VDBs.... though ultimately, Data Sources are actually just
what's defined/deployed in the standalone.xml as resource adapters and/or data
sources. Teiid only supports creating and removing Data Sources through their API. Edit
data source is currently not supported.
was (Author: blafond):
Though we currently utilize Teiid's API to createDataSource(), my understanding is
Teiid uses server api's to actually deploy the DS and update the standalone.xml.
Theoretically Teiid Designer tooling could convert to use the server api vs the Teiid
api.
Note Designer is investigating what it would take to abstract DS management up a level
that could incorporate CPs and just know how to extract properties and deploy DS's.
Not an easy task considering the varying structures of our numerous data source types.
This work would play into a new integrated Data Source Wizard. We're more than willing
to collaborate :)
Database/source/connection Usability
------------------------------------
Key: JBDS-2852
URL: https://issues.jboss.org/browse/JBDS-2852
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Epic
Security Level: Public(Everyone can see)
Components: integration, requirements
Reporter: Burr Sutter
Labels: QE_JBDS80_needinfo
Connecting to a database from within JBDS/Eclipse is a multi-step, multi-screen,
potentially error-prone challenge.
Forge is involved as it can generate entities from schema
Datasources are needed in/on AS/Wildfly/EAP in order for the project deploy
Persistence.xml may needed to be tweaked for the datasource
End-user would like to navigate the schema in the DTP/Hibernate Tools, interactively
review the data and there was once a feature for viewing an ORM diagram that I seem to
have forgotten how it is displayed.
What happens when a project that needs a database connection is imported into the IDE?
This was partially addressed with
https://issues.jboss.org/browse/JBIDE-15263
Let's see if we can continue to improve the workflow by reducing steps, making it
more obvious what steps are required (e.g. hey developer, get the mysql driver .jar), auto
generating the -ds.xml, with a decent explanation for the end-user to follow.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)