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

Max Rydahl Andersen (JIRA) issues at jboss.org
Thu Feb 20 05:37:47 EST 2014


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

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

btw. forge now supports using DTP connections so that means all parts of our stack now can use DTP connections which simplifies things greatly.


                
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list