• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

qwickr turbo-charges EJB 3 persistence  RSS feed

Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
qwickr is revolutionary new tool for managing JPA persistence used in EJB 3.0 applications. With qwickr, users can execute ad-hoc JPQL statements against the persistence units deployed in the application. This is much faster than querying the database directly with SQL tools because JPQL is easier to write. With qwickr, users can be sure that changes to the database are reflected in the application, which is not always the case with because of caching by the application server.

qwickr adds an 'Insert' statement in addition to the standard 'Select','Update' and 'Delete' JPQL constructs. Users can also run multiple JPQL statements in a single transaction, offering all the tools needed to manage persistent data.

As well as being a great tool for data maintenance and ad-hoc querying, qwickr can help users during development. Users can view their persistence model alongside the query window, which saves a number of build cycles when prototyping JPQL statements used in an application.

qwickr has been tested on JBoss 4.0.4 GA and Glassfish application severs. A beta version of the tool can be downloaded at qwickr.com.
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!