[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ] 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.... -- 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