[ https://issues.jboss.org/browse/JBIDE-11394?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11394: --------------------------------------------- its a chicken and egg problem here - if your project has a hibernate JPA configuration it must already have a persistence.xml.... Not sure what flow it would fit into. is it not more a "based on DTP connection info" generate -ds.xml + persistence.xml with proper ds name in it ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11394?page=com.atlassian.jira.plugi... ] Dmitry Geraskov updated JBIDE-11394: ------------------------------------ Fix Version/s: 3.3.0.CR1 (was: 3.3.0.Beta3) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11394?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11394: --------------------------------------------- Alexey - would it make sense to add optional persistence.xml generation/update based on the dtp connection ? If project has no persistence.xml, offer to put in META-INF/persistence.xml, otherwise update it to use the geenrated datasource? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11394?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11394: ---------------------------------------- Fix Version/s: 3.3.1 putting on 3.3.1 to consider as option. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11394?page=com.atlassian.jira.plugi... ] Pete Muir commented on JBIDE-11394: ----------------------------------- JPA/Hibernate will correctly default a lot of that for you. Remember also, that we follow convention over configuration, so we want to suggest a minimal good config, not present all options. We should also include comments for them. Here is the template I would suggest: {code} <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd"> <persistence-unit name="primary"> <!-- If you are running in a production environment, add a managed data source, this example data source is just for development and testing! --> <!-- The datasource is deployed as ${ds-deployment-location}, you can find it in the source at ${ds-source-location} --> <jta-data-source>${ds-name}</jta-data-source> <properties> <!-- Properties for Hibernate --> <property name="hibernate.hbm2ddl.auto" value="create-drop" /> <!-- Print's out the SQL statement Hibernate is using to the console, useful for debugging --> <property name="hibernate.show_sql" value="false" /> </properties> </persistence-unit> </persistence> {code} Specifically note that there are replacements in the comments, and that setting the persistence-unit name to the project name is not really necessary, as they are scoped to the deployment unit anyway and not used for anything much (unless you have >1, in which case the project name is not unique enough). Also note that we don't really recommend using hbm2ddl in update mode, so we shouldn't generate that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11394?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-11394. -------------------------------- -ds file is generated and persistence.xml is updated. Verified in JBT 4.0.Alfa1, L64 -- 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

[ https://issues.jboss.org/browse/JBIDE-11394?page=com.atlassian.jira.plugi... ] Isaac Rooskov updated JBIDE-11394: ---------------------------------- Release Notes Docs Status: Documented as Feature Request Writer: irooskov Release Notes Text: Projects with a Hibernate JPA configuration can now have their persistence.xml and -ds.xml files generated based on DTP connection information. -- 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