[
https://jira.jboss.org/jira/browse/JBIDE-4985?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4985:
--------------------------------------------
Conclusions from irc chat:
The location of the .launch is only different
when JPA facet is selected and hibernate platform enabled.
We need to look at that for CR2. For CR1 not important.
Issue is to get uniform projects so locations of file should be
stable as possible.
hibernate.properties file still need to get
generated. the provider class and datasource and manager lookup class is needed
to override what is stated in persistence.xml.
Without them hibernate query console and critiera editor not work.
Suggestion for cR1, continue to create hibernate.properties
so things are still overridden and usable from ant.
In CR2 possibly introduce an option about hat behavior we want.
New seam projects should configure hibernate tools with the DTP
connection
--------------------------------------------------------------------------
Key: JBIDE-4985
URL:
https://jira.jboss.org/jira/browse/JBIDE-4985
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate, Seam
Affects Versions: 3.1.0.M3
Reporter: Max Rydahl Andersen
Assignee: Dmitry Geraskov
Fix For: 3.1.0.CR1
Attachments: connection_profile_connection.zip, seam+jpa.PNG, seam_only.PNG
Now that hibernate console supports DTP connection profiles shouldn't we start using
that for our Seam projects ?
Removing the need to have connection info in the hibernate-console.properties ? (the
other fields related to tx and others still need to there though)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira