Exception « Glassfish « JPA Q&A





1. JPA/Glassfish 3 - NamingException injecting EJB into servlet    stackoverflow.com

I am deploying to Glassfish 3.1.1. I have a JPA project which creates a jar. It has standard data model classes annotated with @Entity and service classes annotated with @Stateless. ...

3. exception with JPA and mysql connector j    java.net

hi; i have decided to switch to a non-jta datasource configuration for 2 main reasons: 1. i already have an existing DS for several non jpa modules and it seems unreasonable that i would open another connection pool to the same DB. 2. i did not find sufficient support fo proeprties such as test sql statement on borrow and on idle ...

4. JPA Exception    java.net

Caused by: Exception [TOPLINK-200] (Oracle TopLink Essentials - 2.0 (Build b54-rc (07/03/2007))): oracle.toplink.essentials.exceptions.DescriptorException Exception Description: Attempt to register an object with dead indirection as a new object. Possibly the object was deleted or removed from the cache during a merge of a serialized clone. This is a concurrency violation, consider a locking strategy. Mapping: oracle.toplink.essentials.mappings.OneToManyMapping [servicesOfferedCollection] Descriptor: RelationalDescriptor( com.playground.concierge.model.entity.ServiceType --> [DatabaseTable(service_types)]) ...

6. org.hibernate.ejb.HibernatePersistence.isLoadedWithoutReference exception    java.net

glassfish@javadesktop.org wrote: > Hi, > I am migrating a application I am developing from Glassfish v2.1 to v3. The application makes use of JPA and hibernate. > > I have downloaded the glassfish v3 preview and run the update tool to get teh latest stable modules. I have also downloaded the "Hibernate JPA" add-in module. > > When I go to ...

7. JPA 2.0 Validaton Exceptions and unknown protocol: osgi    java.net

I'm working on setting up an ExceptionMapper with JAX-RS/Jersey in Glassfish 3.1-b14. That part is working fine and as part of my testing, I tried setting up a JPA 2.0 Validation annotation (@Size specifically) so I could see how the validation exception would come back; using Hibernate 3.5 as my JPA implementation.