There must be something wrong either with your configuration or your environment. You need to provide more details in order to get help.
On Sun, Oct 16, 2011 at 9:54 PM, jesse <jessegr...@hotmail.com> wrote: > Hi, I've run in to a couple of JPA related issues that are keeping me from > moving to 5.3. My app previously worked fine with tynamo jpa, but now > throws eclipselink exceptions and won't start with Tapestry 5.3 > (5.3-beta-22). > > My app works great with tynamo JPA, tynamo resteasy, eclipselink (2.2.1), > and Tapestry 5.2.6. I had to do one small hack due to the fact that the > tynamo code relies on Defense. No big deal though, and it's all working. > > I've tried to switch to 5.3, and I believe I have everything set up > correctly (obviously I've removed the tynamo jpa dependency from my pom). > I > don't know if this is important or not, but my entities are not > auto-discovered, but rather explicitly listed in persistence.xml (the > package name is not entities, but I would change this if I got everything > working). > > I now have the following issues > > 1) I can't start my application due to errors from Eclipselink. Here's the > important parts: > > Exception [EclipseLink-60] (Eclipse Persistence Services - > 2.2.1.v20110722-r9776): > org.eclipse.persistence.exceptions.DescriptorException > Exception Description: The method [_persistence_set_section_vh] or > [_persistence_get_section_vh] is not defined in the object > [com.stellalingua.app.entity.MyEntity]. > Internal Exception: java.lang.NoSuchMethodException: > com.stellalingua.app.entity.MyEntity._persistence_get_section_vh() > Mapping: org.eclipse.persistence.mappings.ManyToOneMapping[section] > Descriptor: RelationalDescriptor(com.stellalingua.app.entity.MyEntity--> > []) > > Exception [EclipseLink-218] (Eclipse Persistence Services - > 2.2.1.v20110722-r9776): > org.eclipse.persistence.exceptions.DescriptorException > Exception Description: A NullPointerException would have occurred accessing > a non-existent weaved _vh_ method [_persistence_get_section_vh]. The class > was not weaved properly - for EE deployments, check the module order in the > application.xml deployment descriptor and verify that the module containing > the persistence unit is ahead of any other module that uses it. > > 2) To even get this far, I had to change the name used for my data source > in > persistence.xml even though I did not actually change the name of the data > source in jetty. Minor, but still odd. > > I'd really like to switch to 5.3, but can't because of this. > Unfortunately, > also tynamo jpa seems to not work with tapestry 5.3. > > > > -- > View this message in context: > http://tapestry-users.832.n2.nabble.com/Problems-using-JPA-with-5-3-tp6898469p6898469.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Best regards, Igor Drobiazko http://tapestry5.de
