eclipselink

I am new to JPA 2.0/EclipseLink/Glassfish/JEE6, and have kind of a basic question. I have a DAO in which most of the entities are mapped directly to columns using JPA annotations, so I use the EntityManager, and it works great with no issues. However there are some tables in which I am constructing the SQL statements myself b/c they use oracle-specific functions (spatial), and I want very fine-grained control of the SQL. So I am building it with string concatenation. I would like to be able to enroll my SQL executions in the current transaction, if there is one already underway. So naturally I

I am declaring a List object property with: @XmlRootElement(namespace = "...") @XmlType public class Test { private List<String> myList; @XmlElementWrapper(name = "myListWrapper") @XmlElement(name = "myList") public List<String> getMyList() { return myList; } } When an instance of this class with an empty list myList is marshalled, MOXy is not generating an empty wrapper MyListWrapper . However, JAXB RI would do it. The generated XML looks like this when using the RI: <ns2:test xmlns:ns2="..."> <myListWrapper/> </ns2:intensionalSet> Is there a way to obtain the same result with MOXy? Note: I'm

I successfully performed static weaving in EclipseLink-2.4.0 with eclipselink-staticweave-maven-plugin 1.0.3 , but when I also run integration tests. going through all layers in the system, they breaks. In startUp() method I create it's created an User entity which it's committed in the test DB. But in tearDown() method where I clear the DB state that entity (already weaved) could not be removed by same EntityManager. The test goes without errors when entities are not weaved. What do you think the problem could be here ? Here the exception status also: java.lang.AbstractMethodError: nl

I have a @ManyToMany relationship between two entities. When I perform an update on the owning side, it appears that JPA deletes all the linked records from my database and re-inserts them. For me this is a problem because I have a MySQL trigger that fires before a record is deleted. Any ideas on how to get around this problem? @Entity public class User { @Id @Column(name="username") private String username; ... @ManyToMany @JoinTable(name="groups", joinColumns= @JoinColumn(name="username", referencedColumnName="username"), inverseJoinColumns=@JoinColumn(name="groupname", referencedColumnName=

Consider this simple association: @Entity public class Employee { @OneToMany(fetch=FetchType.LAZY) private Set<Address> addresses; } Using this code the addresses are not fetched in the result: Query query=entityManager.createQuery("select e from Employee e"); query.setHint("eclipselink.batch.type", "JOIN"); query.setHint("eclipselink.batch", "e.addresses"); List list=query.getResultList(); While in this one the addresses are fetched: Query query=entityManager.createQuery("select e from Employee e"); query.setHint("eclipselink.join-fetch", "e.addresses"); List list=query.getResultList(); Why