0

I've got a JPA entity that is loaded via dynamic ejb ql queries that can be configured by the user fairly freely. In comes a new requirement: Users should be allowed to create new entities only iff these new entites would be returned by their user specific queries. So, I think I'd need to instanciate a JPA-Entity, create an EJB-Query dynamically and figure out if the entity would be loaded by this query if it existed in the database.

How could I do that? Is there, for example, a standalone JPA cache so that I could push the new JPA entity into the cache and question it with my query, without ever hitting the database?

Tim van Beek
  • 385
  • 3
  • 12

1 Answers1

1

You could just insert the new entity in database, perform the query, see if the entity is found, and rollback if not found (or delete the entity in the same transaction if you don't want to rollback).

JB Nizet
  • 678,734
  • 91
  • 1,224
  • 1,255
  • Yeah I know, but it does not seem to be "right" to insert an entity into the database that you shouldn't insert - besides, the query may load a lot of entities, not just the new one, so it isn't terribly efficient either. But it is a fallback plan B :-) – Tim van Beek May 27 '11 at 14:13