Older

• Nov 26, 2009

  issue 28 (getNamedQuery not supported) commented on by treeder   -   Hi Tim, it would be great if you could provide code to the JPA spec. Or if you want, I'll give you commit access and you can do it directly.

  Hi Tim, it would be great if you could provide code to the JPA spec. Or if you want, I'll give you commit access and you can do it directly.
• Nov 25, 2009

  issue 28 (getNamedQuery not supported) reported by tim.darby.uk   -   First, nice component, enjoying using it! I have existing JPA code though, and in porting it to work with SimpleJPA, I have a pretty wide use of 'getNamedQuery', which throws a 'TODO' exception when using SimpleJPA EntityManager. In my use of SimpleJPA, I've wrapped my use of entity manager with the following, in order to avoid hitting this exception, but it would be cleaner and great if getNamedQuery were directly supported (obviously I get the advantage of knowing the Class I'm looking for the query on, but it shouldn't be too onerous for SimpleJPA to search through its list of known annotated classes (I could look into that if you like, and provide code for it). private Query createSimpleQuery(Class clazz, String queryName) { NamedQueries namedQueriesAnnotation = (NamedQueries)clazz.getAnnotation(NamedQueries.class); if (namedQueriesAnnotation == null) { return null; } NamedQuery namedQueryAnnotations[] = namedQueriesAnnotation.value(); if (namedQueryAnnotations == null) { return null; } for (NamedQuery namedQueryAnnotation : namedQueryAnnotations) { String name = namedQueryAnnotation.name(); if (name.equalsIgnoreCase(queryName)) { String jql = namedQueryAnnotation.query(); Query query = getEntityManager().createQuery(jql); return query; } } return null; }

  First, nice component, enjoying using it! I have existing JPA code though, and in porting it to work with SimpleJPA, I have a pretty wide use of 'getNamedQuery', which throws a 'TODO' exception when using SimpleJPA EntityManager. In my use of SimpleJPA, I've wrapped my use of entity manager with the following, in order to avoid hitting this exception, but it would be cleaner and great if getNamedQuery were directly supported (obviously I get the advantage of knowing the Class I'm looking for the query on, but it shouldn't be too onerous for SimpleJPA to search through its list of known annotated classes (I could look into that if you like, and provide code for it). private Query createSimpleQuery(Class clazz, String queryName) { NamedQueries namedQueriesAnnotation = (NamedQueries)clazz.getAnnotation(NamedQueries.class); if (namedQueriesAnnotation == null) { return null; } NamedQuery namedQueryAnnotations[] = namedQueriesAnnotation.value(); if (namedQueryAnnotations == null) { return null; } for (NamedQuery namedQueryAnnotation : namedQueryAnnotations) { String name = namedQueryAnnotation.name(); if (name.equalsIgnoreCase(queryName)) { String jql = namedQueryAnnotation.query(); Query query = getEntityManager().createQuery(jql); return query; } } return null; }
• Sep 21, 2009

  issue 27 (support for DELETE query) reported by dan.mihai.dumitriu   -   If we don't have DELETE query support, the only way to delete is via the EntityManager.remove(Object) call, which is obviously a very inefficient method.

  If we don't have DELETE query support, the only way to delete is via the EntityManager.remove(Object) call, which is obviously a very inefficient method.
• Sep 21, 2009

  issue 14 (Support field based access from the JPA spec) commented on by dan.mihai.dumitriu   -   This is a bit of a hack, but perhaps still better than no annotation support on fields. (Need to always have getters and setters on every non-transient field.

  This is a bit of a hack, but perhaps still better than no annotation support on fields. (Need to always have getters and setters on every non-transient field.
• Sep 01, 2009

  GettingStarted (Getting Started with SimpleJPA) Wiki page commented on by olostan   -   I think that link to {WebApplications} page would be very usefull here and should be added into 'What Next?'.

  I think that link to {WebApplications} page would be very usefull here and should be added into 'What Next?'.
• Sep 01, 2009

  WebApplications (How to use SimpleJPA in a web application.) Wiki page commented on by olostan   -   Just a snippet for 'Way 2' (without simplejpa.properties files): {{{ private static EntityManagerFactoryImpl factory; @Override public void init(ServletConfig config) throws ServletException { super.init(config); Map<String,String> props = new HashMap<String,String>(); props.put("accessKey","<key>"); props.put("secretKey","<secret_key>"); factory = new EntityManagerFactoryImpl("UnitName", props, getLibPaths(config.getServletContext())); } }}} May be it would be usefull.

  Just a snippet for 'Way 2' (without simplejpa.properties files): {{{ private static EntityManagerFactoryImpl factory; @Override public void init(ServletConfig config) throws ServletException { super.init(config); Map<String,String> props = new HashMap<String,String>(); props.put("accessKey","<key>"); props.put("secretKey","<secret_key>"); factory = new EntityManagerFactoryImpl("UnitName", props, getLibPaths(config.getServletContext())); } }}} May be it would be usefull.
• Aug 17, 2009

  issue 10 (Maven build support) commented on by german.eichberger   -   The lates svn checkout needs the attached pom --

  The lates svn checkout needs the attached pom --
• Aug 06, 2009

  simplejpa-1.0-RC1.jar (SimpleJPA 1.0 RC1) file uploaded by treeder   -  

  Labels: Featured

  Labels: Featured
• Aug 06, 2009

  r153 (* junit import got into here somehow.) committed by treeder   -   * junit import got into here somehow.

  * junit import got into here somehow.
• Aug 06, 2009

  simplejpa-1.0-RC1.jar (SimpleJPA 1.0 RC1) file uploaded by treeder   -  

  Labels: Featured

  Labels: Featured
• Aug 04, 2009

  r152 (Some serious SimpleDB query hit reduction which equals some ...) committed by treeder   -   Some serious SimpleDB query hit reduction which equals some serious performance increases which in turn means less benjamin's.

  Some serious SimpleDB query hit reduction which equals some serious performance increases which in turn means less benjamin's.
• Aug 04, 2009

  r151 (Made LazyList do a COUNT(*) query on size. Much more efficie...) committed by treeder   -   Made LazyList do a COUNT(*) query on size. Much more efficient than before.

  Made LazyList do a COUNT(*) query on size. Much more efficient than before.
• Aug 02, 2009

  r150 (Added global Factory based stats.) committed by treeder   -   Added global Factory based stats.

  Added global Factory based stats.
• Aug 02, 2009

  r149 (Fixed up caching to be compatabile with KittyCache and Ehcac...) committed by treeder   -   Fixed up caching to be compatabile with KittyCache and Ehcache.

  Fixed up caching to be compatabile with KittyCache and Ehcache.
• Aug 02, 2009

  issue 26 (byte[]-support) Status changed by treeder   -   Fixed in revision 148.

  Status: Fixed

  Fixed in revision 148.

  Status: Fixed
• Aug 02, 2009

  r148 (Fixed http://code.google.com/p/simplejpa/issues/detail?id=26...) committed by treeder   -   Fixed http://code.google.com/p/simplejpa/issues/detail?id=26, added byte support directly into SimpleDB.

  Fixed http://code.google.com/p/simplejpa/issues/detail?id=26, added byte support directly into SimpleDB.
• Aug 02, 2009

  issue 18 (NPE when using "en.find" and the domain doesn't exist) Status changed by treeder   -   Will return null now if domain doesn't yet exist (ie: no puts on it yet).

  Status: Fixed

  Will return null now if domain doesn't yet exist (ie: no puts on it yet).

  Status: Fixed
• Aug 02, 2009

  issue 23 (SimpleJPA generates invalid select query) Status changed by treeder   -  

  Status: Fixed

  Status: Fixed
• Aug 02, 2009

  r147 (Ok, added backticks to attribute names now, so dashes can wo...) committed by treeder   -   Ok, added backticks to attribute names now, so dashes can work.

  Ok, added backticks to attribute names now, so dashes can work.
• Aug 02, 2009

  issue 23 (SimpleJPA generates invalid select query) commented on by treeder   -   You're probably right, required backticks or something. Will look into it.

  You're probably right, required backticks or something. Will look into it.
• Aug 02, 2009

  issue 22 (Can't use Lob fields in select statment "where" and "sort') Status changed by treeder   -   Unfortunately, you can't query on Lobs and probably never will be able to unless SimpleDB supports it.

  Status: WontFix

  Unfortunately, you can't query on Lobs and probably never will be able to unless SimpleDB supports it.

  Status: WontFix
• Aug 02, 2009

  issue 20 (warning from RestS3Service) Status changed by treeder   -   Believe this is fixed already.

  Status: Fixed

  Believe this is fixed already.

  Status: Fixed
• Aug 02, 2009

  r146 (Upgraded caching stuff to fix ehcache 1.6 breakage, but ende...) committed by treeder   -   Upgraded caching stuff to fix ehcache 1.6 breakage, but ended up pulling out most ehcache dependencies.

  Upgraded caching stuff to fix ehcache 1.6 breakage, but ended up pulling out most ehcache dependencies.
• Aug 02, 2009

  Configuration (Configuration options for simplejpa.properties) Wiki page edited by treeder   -   Revision r145 Edited wiki page through web user interface.

  Revision r145 Edited wiki page through web user interface.
• Aug 02, 2009

  GettingStarted (Getting Started with SimpleJPA) Wiki page edited by treeder   -   Revision r144 Edited wiki page through web user interface.

  Revision r144 Edited wiki page through web user interface.
• Aug 02, 2009

  GettingStarted (Getting Started with SimpleJPA) Wiki page edited by treeder   -   Revision r143 Edited wiki page through web user interface.

  Revision r143 Edited wiki page through web user interface.
• Aug 02, 2009

  Configuration (Configuration options for simplejpa.properties) Wiki page edited by treeder   -   Revision r142 Edited wiki page through web user interface.

  Revision r142 Edited wiki page through web user interface.
• Aug 02, 2009

  Configuration (Configuration options for simplejpa.properties) Wiki page edited by treeder   -   Revision r141 Edited wiki page through web user interface.

  Revision r141 Edited wiki page through web user interface.
• Aug 02, 2009

  Configuration (Configuration options for simplejpa.properties) Wiki page edited by treeder   -   Revision r140 Edited wiki page through web user interface.

  Revision r140 Edited wiki page through web user interface.
• Aug 02, 2009

  SecondLevelCache (Second level cache information.) Wiki page edited by treeder   -   Revision r139 Edited wiki page through web user interface.

  Revision r139 Edited wiki page through web user interface.
• Jul 30, 2009

  issue 26 (byte[]-support) reported by carlhasselskog   -   Save byte[]-fields which do not have the LOB-annotation as Base64-encoded Strings in SimpleDB. The attached files adds support for this.

  Save byte[]-fields which do not have the LOB-annotation as Base64-encoded Strings in SimpleDB. The attached files adds support for this.
• Jul 25, 2009

  WhatsSupported (Supported JPA Features) Wiki page commented on by google-a...@historygames.de   -   How about transactions? Are they fully supported? Including operations on several entity types during 1 transaction?

  How about transactions? Are they fully supported? Including operations on several entity types during 1 transaction?
• Jul 14, 2009

  GettingStarted (Getting Started with SimpleJPA) Wiki page edited by treeder
• Jul 13, 2009

  GettingStarted (Getting Started with SimpleJPA) Wiki page edited by treeder
• Jul 07, 2009

  r136 (Fixed NPE exception.) committed by treeder   -   Fixed NPE exception.

  Fixed NPE exception.
• Jun 09, 2009

  r135 (Ability to set lobBucketName in configuration.) committed by treeder   -   Ability to set lobBucketName in configuration.

  Ability to set lobBucketName in configuration.
• May 31, 2009

  r134 (Add pom.xml to support building with maven) committed by e...@molitor.org   -   Add pom.xml to support building with maven

  Add pom.xml to support building with maven
• May 18, 2009

  issue 25 (NoSuchMethodException) commented on by amir.wasim   -   I am getting it on a field in my entity which is Arraylist of another class ArrayList<DynamicProperty> dynamicProperties; The class looks like as follows @Entity public class DynamicProperty { String value, name, ID; ............. }

  I am getting it on a field in my entity which is Arraylist of another class ArrayList<DynamicProperty> dynamicProperties; The class looks like as follows @Entity public class DynamicProperty { String value, name, ID; ............. }
• May 18, 2009

  issue 25 (NoSuchMethodException) reported by amir.wasim   -   Hi, I am getting NoSuchMethodException when i try to invoke get() from the list. Any idea how i can fix this problem?

  Hi, I am getting NoSuchMethodException when i try to invoke get() from the list. Any idea how i can fix this problem?
• Apr 17, 2009

  issue 24 (Patch to use a single S3Service instance) reported by craigwblake   -   Currently the S3Service instance is recreated every time the entity manager calls EntityManagerFactoryImpl.getS3Service(), which is quite a bit. Since the Jets3t service implementation seems to do a lot of its connection pooling and optimization on a per-service basis, this seems to be pretty inefficient. I keep getting errors from Jets3t in my logs, and I think it's because of this. The S3Service class is specifically noted to be thread-safe, so it is guaranteed safe to use a single instance. Once the factory was changed to use a single instance, I have seen no more connection pool errors from Jets3t.

  Currently the S3Service instance is recreated every time the entity manager calls EntityManagerFactoryImpl.getS3Service(), which is quite a bit. Since the Jets3t service implementation seems to do a lot of its connection pooling and optimization on a per-service basis, this seems to be pretty inefficient. I keep getting errors from Jets3t in my logs, and I think it's because of this. The S3Service class is specifically noted to be thread-safe, so it is guaranteed safe to use a single instance. Once the factory was changed to use a single instance, I have seen no more connection pool errors from Jets3t.
• Apr 16, 2009

  issue 17 (Add support for max results.) Status changed by treeder   -   Applied patch.

  Status: Fixed

  Applied patch.

  Status: Fixed
• Apr 16, 2009

  r133 (re #17. Applied patch.) committed by treeder   -   re #17. Applied patch.

  re #17. Applied patch.
• Apr 16, 2009

  issue 17 (Add support for max results.) commented on by craigwblake   -   I've updated the patch to use the new Select API limit clause, which whittles it down to a whole one line.

  I've updated the patch to use the new Select API limit clause, which whittles it down to a whole one line.
• Apr 16, 2009

  issue 23 (SimpleJPA generates invalid select query) commented on by craigwblake   -   It looks like this centers around the xml-lobkey field. If I remove that predicate from the query it completes. Is there a problem with attributes containing a dash in the Select API?

  It looks like this centers around the xml-lobkey field. If I remove that predicate from the query it completes. Is there a problem with attributes containing a dash in the Select API?
• Apr 16, 2009

  issue 23 (SimpleJPA generates invalid select query) reported by craigwblake   -   When building a query with sorting AWS complains that the query syntax is invalid. Caused by: javax.persistence.PersistenceException: Query failed: Domain=dev-Object -> select * from `dev-Object` where account_id = '7bbb373d-a770-4d36-a4ab-4e5937230fed' and start is not null and xml-lobkey is not null and DTYPE = 'Report' order by start desc at com.spaceprogram.simplejpa.LazyList.loadItems(LazyList.java:197) at com.spaceprogram.simplejpa.LazyList.loadAllItems(LazyList.java:228) at com.spaceprogram.simplejpa.LazyList.size(LazyList.java:69) at com.spaceprogram.simplejpa.LazyList.isEmpty(LazyList.java:64) ... 2 more Caused by: com.xerox.amazonws.sdb.SDBException: Client error : The specified query expression syntax is not valid. at com.xerox.amazonws.sdb.Domain.makeRequestInt(Domain.java:555) at com.xerox.amazonws.sdb.Domain.selectItems(Domain.java:450) at com.spaceprogram.simplejpa.LazyList.loadItems(LazyList.java:176) ... 8 more

  When building a query with sorting AWS complains that the query syntax is invalid. Caused by: javax.persistence.PersistenceException: Query failed: Domain=dev-Object -> select * from `dev-Object` where account_id = '7bbb373d-a770-4d36-a4ab-4e5937230fed' and start is not null and xml-lobkey is not null and DTYPE = 'Report' order by start desc at com.spaceprogram.simplejpa.LazyList.loadItems(LazyList.java:197) at com.spaceprogram.simplejpa.LazyList.loadAllItems(LazyList.java:228) at com.spaceprogram.simplejpa.LazyList.size(LazyList.java:69) at com.spaceprogram.simplejpa.LazyList.isEmpty(LazyList.java:64) ... 2 more Caused by: com.xerox.amazonws.sdb.SDBException: Client error : The specified query expression syntax is not valid. at com.xerox.amazonws.sdb.Domain.makeRequestInt(Domain.java:555) at com.xerox.amazonws.sdb.Domain.selectItems(Domain.java:450) at com.spaceprogram.simplejpa.LazyList.loadItems(LazyList.java:176) ... 8 more
• Mar 24, 2009

  r132 (Minors) committed by treeder   -   Minors

  Minors
• Mar 24, 2009

  r131 (Set the content length on lobs to remove jets3t warning mess...) committed by treeder   -   Set the content length on lobs to remove jets3t warning message.

  Set the content length on lobs to remove jets3t warning message.
• Mar 24, 2009

  issue 22 (Can't use Lob fields in select statment "where" and "sort') reported by reformy   -   What steps will reproduce the problem? 1. Define MyObject entity with a Lob field names "decription". 2. Try to execute: select * from MyObject where description='something' What is the expected output? What do you see instead? It tries to use the "description-lob" field as a simple string. What version of the product are you using? On what operating system? 0.8. Windows XP SP3. Please provide any additional information below.

  What steps will reproduce the problem? 1. Define MyObject entity with a Lob field names "decription". 2. Try to execute: select * from MyObject where description='something' What is the expected output? What do you see instead? It tries to use the "description-lob" field as a simple string. What version of the product are you using? On what operating system? 0.8. Windows XP SP3. Please provide any additional information below.
• Mar 19, 2009

  issue 15 (S3 errors under load) Status changed by treeder   -   Fixed. Only calls createBucket once per entitymanagerfactory now (and then, only if bucket was not found on startup).

  Status: Fixed

  Fixed. Only calls createBucket once per entitymanagerfactory now (and then, only if bucket was not found on startup).

  Status: Fixed
• Mar 19, 2009

  issue 19 (System.out ...) Status changed by treeder   -  

  Status: Fixed

  Status: Fixed