Google returns many results, including this and this blog posts. The summary (copied from the former) is: Added support for persistently ordered lists using OrderColumn and provider-managed ordering column Defined support for foreign key mapping strategy for unidirectional one-to-many relationships Added clear method to EntityManager interface to allow entities to be evicted from the persistence … Read more
Depending on whether the transaction encloses the loop, batching typically already happens in your case. JPA will collect all your updates in its L1 cache, and typically write that all to the DB in a batch when the transaction commits. This is not really that different with batching in JDBC, where every batch-item you add … Read more
Yes, it is possible. You can override the default generator name with the @SequenceGenerator annotation. Base class @MappedSuperclass public abstract class PersistentEntity implements Serializable { private static final long serialVersionUID = 1L; @Id @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = “default_gen”) protected Long id = 0L; public Long getId() { return id; } public void setId(Long id) … Read more
It is a good idea to have those two layers when your business logic is more complex than your data logic. The service layer implements the business logic. In most cases, this layer has to perform more operations than just calling a method from a DAO object. And if you’re thinking of making your application … Read more
You need aspectJ 1.8 to get Java 8 support.
First of all, there is no rollback of an exception, it’s a rollback of a transaction. If you throw your exception with @ApplicationException(rollback=true), you don’t have to rollback the transaction manually. Context.setRollbackOnly() forces the container to rollback the transaction, also if there is no exception. A checked exception itself doesn’t rollback a transaction. It needs … Read more
If only 1 timer may ever be active at the same time, there are a couple of solutions. First of all the @Timer should probably be present on an @Singleton. In a Singleton methods are by default write-locked, so the container will automatically be locked-out when trying to invoke the timer method while there’s still … Read more
I’d suggest learning Spring. Learn just the basics, and then when you do come to learn Hibernate you’ll be able to take advantage of all the Spring helpers which make Hibernate easier to use. There’s also the point that Spring is useful in many layers instead of just at the data access part 🙂
I followed the solution in the following link, and it works fine: Access Spring beans from a servlet in JBoss public class MyServlet extends HttpServlet { @Autowired private MyService myService; public void init(ServletConfig config) { super.init(config); SpringBeanAutowiringSupport.processInjectionBasedOnServletContext(this, config.getServletContext()); } }
Original Post: They’ve since moved from Google Code to BitBucket. Here’s the BitBucket Repo: https://bitbucket.org/xerial/sqlite-jdbc Update 8-13-2015: Now they’re off to GitHub: https://github.com/xerial/sqlite-jdbc I’ve left the bitbucket link because there is a wealth of project information there, even though the code has moved to git hub.