]
Max Rydahl Andersen commented on JBDS-2852:
-------------------------------------------
[~blafond] great! i'll take you up on that. Right now I'll need to add what have
been done for JBDS 8.0 since it's GA is arriving over summer. I'll get that added
here and probably separate out the last missing part which you and I have discussed
on/off. I plan on getting through that the next week.
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
Assignee: 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.