| Summary: | Jar file refs not resolved when placed in Ear | ||
|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | Chris Stodden <chris.stodden> |
| Component: | JPA | Assignee: | dali.general-inbox <dali.general-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | neil.hauge, paul.fullbright |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Chris Stodden
Sorry for the lack of comment on this... You may have to type in the jar file location that will work with your environment in some cases, but looking for comment from Paul on whether this is something we could/should support. Looking at this again. I have reread your comment and am a bit confused. Getting a jar file into this list on the General tab requires the user to specifically add the jar to the persistence.xml. It would not just end up in that list as there is no defaulting with jar refs. It also sounds like you are building an application with more than one persistence.xml, which is an advanced case. Just reviewing some older bugs. I think the issue here is a configuration issue. Dali (JPA facet) should be used in the project that builds the HRjpa.jar, and not in the EAR application project in the case you describe. jar-file refs are for identifying classes to pull into a persistence unit, not to define one. Using the JPA facet in the EAR project just adds confusion. Closing this for now, but let me know if you need more assistance configuring this application. |