jQuery in Action, 3rd edition
The moose likes Object Relational Mapping and the fly likes Best practice for persistence unit Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » Object Relational Mapping
Bookmark "Best practice for persistence unit" Watch "Best practice for persistence unit" New topic

Best practice for persistence unit

Christian Plaetzinger

Joined: Jun 17, 2008
Posts: 1

imagine following setup:
I have multiple packages with entity beans. Currently each package contains a persistence.xml and the names of persistence units are different for each package. Each package is packed into a separate jar file. But all persistence units use the same data source and configuration.

In my opinion this doesn't make much sense. It would be easier to have only one persistence.xml containing the configuration only once and to use the same persistence unit in all packages.

What do you thing about it? For which case or for which reason would it be a good idea to have more than one persistence unit within an application?

I agree. Here's the link: http://aspose.com/file-tools
subject: Best practice for persistence unit
It's not a secret anymore!