This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 98085 - ProviderUtil assumes there is only one persistence.xml per project
Summary: ProviderUtil assumes there is only one persistence.xml per project
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Persistence (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@javaee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-16 13:52 UTC by Erno Mononen
Modified: 2008-01-15 15:24 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erno Mononen 2007-03-16 13:52:17 UTC
The methods for retrieving a PUDataObject instance in the 
o.n.m.j2ee.persistence.provider.ProviderUtil class assume that there is only 
one persistence.xml file per project. This is incorrect since the JPA 
specification allows to have several persistence.xml files. See also issue 
96777 desc 6 for more information.
Comment 1 Erno Mononen 2007-03-16 20:33:55 UTC
To clarify this issue a bit: The spec allows multiple persistence.xml files in 
an *application*. What I had in mind was persistence units defined at the EAR 
level, but thinking about it now it is questionable whether that use case 
should (or can) be supported by the ProviderUtil. In any case, the issue is 
still valid for the case Andrei describes.
Comment 2 Erno Mononen 2007-07-26 15:40:27 UTC
There are currently no clients that would need this for 6.0, so the correct priority for this is rather P3. Need to be 
re-evaluated when there are clients that would need this, such as the freeform projects.
Comment 3 Erno Mononen 2007-10-17 16:01:51 UTC
Setting the TM to future as per desc3.
Comment 4 Andrei Badea 2008-01-15 15:24:20 UTC
I guess there is no point in keeping this issue open as long as we don't plan to fix it (which we currently don't, as it
would require major changes).