| Re: [eclipselink-users] Help with static weaving on OC4J seeing ._toplink_setmyColumn |
|
I'm not sure your options are correct. The problem you are encountering is that you have specified that the jar uses static weaving, but it has not been statically woven for TopLink Essentials. So the options are: 1) Use EclipseLink, but you will need to add the EclipseLink.jar as a shared library or add it to the Ear, and change the persistence.xml so that it references it as the provider via the <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> tag. With this, you can then use dynamic weaving or static weaving (be sure your jar is statically woven though) 2) Use TopLink Essentials. Either change the persistence.xml so that it uses dynamic weaving, or statically weave your jar. There is a demo showing EclipseLink being used in OC4J at: http://wiki.eclipse.org/EclipseLink/Examples/JPA/OC4J_Web_Tutorial Best Regards, Chris On 02/07/2010 2:08 PM, Tim Hollosy wrote: Ah, I think that's the issue. I was never actually _using_ static weaving in the past. So when I was deploying since I had eclipselink.jar in my WEB-INF/lib directory. Eclipselink was still used, but now that eclipselink needs to use the weaved classes that must happen at some deeper level. So OC4J is trying to use toplink essentials instead. So my options are: -Don't weave (bad because all this eager fetching will kill me). -Replace toplink with eclipselink on the server (bad because i have to convince sysadmins to change something!) ./tch On Fri, Jul 2, 2010 at 1:18 PM, Christopher Delahunt <christopher.delahunt@xxxxxxxxxx> wrote: |