Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Talk:EclipseLink/Development/JPA 2.0/weblogic"
(New page: I managed to get JPA2.0 working in Weblogic in a slightly different way then what is described in "DI 1.1: Alternative 3: Application Level Shared Library". - I did not put anything in AP...) |
|||
| Line 1: | Line 1: | ||
I managed to get JPA2.0 working in Weblogic in a slightly different way then what is described in "DI 1.1: Alternative 3: Application Level Shared Library". | I managed to get JPA2.0 working in Weblogic in a slightly different way then what is described in "DI 1.1: Alternative 3: Application Level Shared Library". | ||
| − | + | * I did not put anything in APP-INF/lib neither in war/WEB-INF/classes/META-INF/MANIFEST.MF | |
| − | + | ||
| − | + | * at first Weblogic was still trying to parse my persistence.xml that is inside war/WEB-INF/classes/META-INF, this happened before Spring initialization started, so at that point my application was not even trying to use JPA | |
| + | |||
| + | * to fix this I renamed it to persistenceWeblogic.xml and changed the Spring configuration to use this name instead of the default | ||
For me it looks like Weblogic was just validating the persistence.xml, so by renaming it this validation was disabled. | For me it looks like Weblogic was just validating the persistence.xml, so by renaming it this validation was disabled. | ||
Latest revision as of 10:00, 1 December 2010
I managed to get JPA2.0 working in Weblogic in a slightly different way then what is described in "DI 1.1: Alternative 3: Application Level Shared Library".
- I did not put anything in APP-INF/lib neither in war/WEB-INF/classes/META-INF/MANIFEST.MF
- at first Weblogic was still trying to parse my persistence.xml that is inside war/WEB-INF/classes/META-INF, this happened before Spring initialization started, so at that point my application was not even trying to use JPA
- to fix this I renamed it to persistenceWeblogic.xml and changed the Spring configuration to use this name instead of the default
For me it looks like Weblogic was just validating the persistence.xml, so by renaming it this validation was disabled.