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

[Burr Sutter (JIRA)]

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

Burr Sutter commented on JBDS-2852:
-----------------------------------

[~mmurray]One of our challenges is...I am not sure if we even know how it is supposed to work in its current form.  I have found the best way to achieve better usability is to first document the N step "ugly" process/workflow that is experienced by the end-user, then tweak, normally with just a few hours of effort you can get from N steps to N / 2 pretty easily - half the steps normally makes things a little more usable.  :-)

In this particular case, here is an example of a possible user story:
a) As a Java EE JAX-RS+JPA developer, I need to be able to:
1) connect to my Oracle, MySQL, MS SQL Server, DB/2 or Postgres databases (local machine or remotely across the network, in openshift) with my provided credentials
2) view its schema/tables/fields
3) view the relationships amongst the tables/views
4) run some sql queries (insert, update, delete, select)
5) generate initial JPA entity classes (via Forge)
6) generate a persistence.xml, being able to tweak it
7) generate a datasource.xml, being able to tweak it
9) generate initial JAX-RS endpoints
10) run an interactive test of a JAX-RS endpoint (CRUD ops)
11) go back to the database to see if the CRUD op has occurred in the database itself
12) add bean validations to my entities....
                
> Database/source/connection Usability
> ------------------------------------
>
>                 Key: JBDS-2852
>                 URL: https://issues.jboss.org/browse/JBDS-2852
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: integration, requirements
>            Reporter: Burr Sutter
>
> 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