juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Cunningham (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Resolved: (JUDDI-166) Need review persistence.xml setup
Date Tue, 07 Apr 2009 16:54:12 GMT

     [ https://issues.apache.org/jira/browse/JUDDI-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tom Cunningham resolved JUDDI-166.

    Resolution: Fixed

hibernate and openjpa both now have persistence.xml's in WEB-INF/classes/META-INF, and there
is a context.xml in META-INF that contains the data source being used (derby by default).
      The nice thing about doing it this way is that everything is uncompressed in our tomcat
bundle, so the user does not have to edit the persistence.xml in the WAR.

> Need review persistence.xml setup
> ---------------------------------
>                 Key: JUDDI-166
>                 URL: https://issues.apache.org/jira/browse/JUDDI-166
>             Project: jUDDI
>          Issue Type: Bug
>            Reporter: Tom Cunningham
>            Assignee: Tom Cunningham
>             Fix For: 3.0beta
> Currently, our persistence.xml's are stored in juddi-core/src/main/resources/persistence.
       The user chooses the persistence framework they want using a property during the build
> cd juddi-core
> mvn -Dpersistence=(hibernate|openjpa) clean install (where persistence= one of hibernate/openjpa)
> The persistence.xml then ends up in the built juddi-core.jar.     Should we be shipping
a persistence.xml inside of juddi-core.jar?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message