eclipselink

问题 I am getting below error while trying to configure spring data in my applciation. I am using spring data and EclipseLink, along with spring-security and oauth2. SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener java.lang.NoSuchMethodError: org.springframework.beans.BeanUtils.findPropertyForMethod(Ljava/lang/reflect/Method;Ljava/lang/Class;)Ljava/beans/PropertyDescriptor; at org.springframework.orm.jpa

问题 I have a xml file generated using moxy implementation of jaxb. However standalone value does not appear in the xml document. 回答1: Note: I'm the EclipseLink JAXB (MOXy) lead and a member of the JAXB (JSR-222) expert group. The standalone attribute is seldom used, and is only relevant if you are using a DTD. Since JAXB (JSR-222) is primarily used with XML Schema it doesn't apply. We chose not to output that attribute in the MOXy implemenation of JAXB (JSR-222). Other XML technologies chose not

问题 I'm developing a student manager application in Java with JPA entities provided by Eclipselink. I'm trying to implement a many-to-many relationship between two entities for a while, but I ran into some weird exceptions. My implementations are based on: Java persistence Wiki page of ManyToMany relationship and this StackOverflow post. Here is my Homework.java file's relevant parts: @Entity @Table(name = "db_homework") public class Homework { @Id @GeneratedValue(strategy = IDENTITY) private

问题 Using JPA with EclipseLink I have 2 classes: User and Address. Simplifying, in the same transaction I creates a new user, a new address and add that address to the user knowing that each user can have many addresses: User = new User(); Address address= new Address(); user.addAddress(address); This is the mapping in User class: @OneToMany(mappedBy = "idUser") private Set<Address> addresses; This is the mapping in Address class: @ManyToOne(cascade = { javax.persistence.CascadeType.REFRESH,

问题 I'm trying Eclipse Kepler 4.3 EE After open it over my old workspace, my project starts with an build error: This project has the JPA facet, but no JPA project could be created. See the error log for more details. This is the details: eclipse.buildId=4.3.0.I20130605-2000 java.version=1.7.0_21 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=pt_BR Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -data D:\JJW

问题 I'm trying Eclipse Kepler 4.3 EE After open it over my old workspace, my project starts with an build error: This project has the JPA facet, but no JPA project could be created. See the error log for more details. This is the details: eclipse.buildId=4.3.0.I20130605-2000 java.version=1.7.0_21 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=pt_BR Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -data D:\JJW

问题 I use glassfish-embedded-web for integration tests inside a maven project: <dependency> <groupId>org.glassfish.extras</groupId> <artifactId>glassfish-embedded-web</artifactId> <version>3.2-b06</version> <scope>test</scope> </dependency> glassfish-embedded-web comes with Eclipselink 2.2.0, but the project requires features of 2.4. For regular deployment, this is solved by adding je required jars to glassfish's modules directory and this dependency: <dependency> <groupId>org.eclipse.persistence

问题 Currently, the JPA entities that comprise my application have an @NamedQueries block that contains many @NamedQuery annotations. This works well but some of my entities have over 80 @NamedQuery annotations and are getting difficult to maintain. I now need to add sorting to my queries and do not want to create additional @NamedQuery annotations. During my research, I discover the JPA 2.1 EntityManagerFactory.addNamedQuery method. This seems to be the answer to my prayers. I could create an

问题 It'll be weeks that I'm stuck with EclipseLink. I can not persist an object in my database. I use netbeans 7.3. I encountered this problem when I started designing a web application. What follows is the approach I have adopted. It may be that I do without me realize a mistake. After that netbeans has finished generating the project files I configured the jndi. Then I converted automatically with netbeans, the database tables in entity object. here is the link then, from these classes, I

问题 I'm making a database migration tool and am dealing with a source database that's very unwieldy. It's basically one giant table that has upwards of 40-50 columns. However not all of these columns are useful to me. I only want maybe a dozen or so of them. Once I get that data I'm making requests to a web service that will handle everything on the destination end of migration. My options are basically creating queries manually to only select the columns I want, or make an Entity that maps the