[jbosstools-issues] [JBoss JIRA] (JBDS-2852) Database/source/connection Usability

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969301#comment-12969301 ] 

Max Rydahl Andersen commented on JBDS-2852:
-------------------------------------------

Just to make it clear - anything the requires Teiid management api is not applicable to this. we just can't use it nor rely on it since Teiid are not available.

Whatever we do need be done via the server management api. afaics all the data is available from it - username, password, connection properties, driverclassname and classpath info.

[~blafond] what is CP's a reference to ? classpath ? yeah - afaics that is all available in form of a module name which one can look up in management api too.

About having the UI on at /server/subsystems/datasources that would be a start but  I think this deserves higher visibility and I would make it available from the "New" sub menu for selected servers too and then use a wizard which initial selection is simply initalized to be the server currently selected. 

Another subject is to actually get that tree more useful and not require to navigate that tree so much - it could use the property view somewhat smarter to reduce the need for that. (should create separate jira for that)


> 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)