[jira] Commented: (OPENJPA-242) JCache (JSR 107) support in the OpenJPA DataCache

[ https://issues.apache.org/jira/browse/OPENJPA-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499202 ] Patrick Linskey commented on OPENJPA-242: - With a small amount of work, we could abstract away the needs of

[jira] Commented: (OPENJPA-235) SQL reordering to avoid non-nullable foreign key constraint violations

[ https://issues.apache.org/jira/browse/OPENJPA-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499200 ] Patrick Linskey commented on OPENJPA-235: - Hi, Attach the patch to the JIRA and one of those of us with TCK

[jira] Commented: (OPENJPA-235) SQL reordering to avoid non-nullable foreign key constraint violations

[ https://issues.apache.org/jira/browse/OPENJPA-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497632 ] Patrick Linskey commented on OPENJPA-235: - Any idea about the nature of the failure? Was the patch reorderin

[jira] Commented: (OPENJPA-243) IntelliJ IDEA plugin to integrate OpenJPA enhancer into build process

[ https://issues.apache.org/jira/browse/OPENJPA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497626 ] Patrick Linskey commented on OPENJPA-243: - One missing instruction from the previous comment: the 0.1 plugin

[jira] Commented: (OPENJPA-243) IntelliJ IDEA plugin to integrate OpenJPA enhancer into build process

[ https://issues.apache.org/jira/browse/OPENJPA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497624 ] Patrick Linskey commented on OPENJPA-243: - The plugin as of r540340 integrates the OpenJPA enhancer with Int

[jira] Updated: (OPENJPA-243) IntelliJ IDEA plugin to integrate OpenJPA enhancer into build process

[ https://issues.apache.org/jira/browse/OPENJPA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-243: Attachment: OpenJPA-0.1.zip Build of sandboxes/IDEA-plugin at r540340. This was built with

[jira] Commented: (OPENJPA-130) Streaming LOB support

[ https://issues.apache.org/jira/browse/OPENJPA-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497601 ] Patrick Linskey commented on OPENJPA-130: - Ignacio Andreu will be working on this issue for the Google Summe

[jira] Assigned: (OPENJPA-130) Streaming LOB support

[ https://issues.apache.org/jira/browse/OPENJPA-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey reassigned OPENJPA-130: --- Assignee: Patrick Linskey > Streaming LOB support > - > >

[jira] Created: (OPENJPA-243) IntelliJ IDEA plugin to integrate OpenJPA enhancer into build process

IntelliJ IDEA plugin to integrate OpenJPA enhancer into build process - Key: OPENJPA-243 URL: https://issues.apache.org/jira/browse/OPENJPA-243 Project: OpenJPA Issue Type:

[jira] Commented: (OPENJPA-194) Correct suffixes of build artifacts to elimiate '-all' and '-project'

[ https://issues.apache.org/jira/browse/OPENJPA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493962 ] Patrick Linskey commented on OPENJPA-194: - I think that it's more common to see things like 'openjpa-0.9.7-s

[jira] Resolved: (OPENJPA-235) SQL reordering to avoid non-nullable foreign key constraint violations

[ https://issues.apache.org/jira/browse/OPENJPA-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-235. - Resolution: Fixed > SQL reordering to avoid non-nullable foreign key constraint violatio

[jira] Assigned: (OPENJPA-235) SQL reordering to avoid non-nullable foreign key constraint violations

[ https://issues.apache.org/jira/browse/OPENJPA-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey reassigned OPENJPA-235: --- Assignee: Patrick Linskey > SQL reordering to avoid non-nullable foreign key constra

[jira] Updated: (OPENJPA-230) Handle guaranteed delivery of Data Cache events on normal JVM termination using TCPRemoteCommitProvider

[ https://issues.apache.org/jira/browse/OPENJPA-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-230: Attachment: OPENJPA-230.patch Good point -- _keepRunning is a bit too abrupt. How does th

[jira] Updated: (OPENJPA-230) Handle guaranteed delivery of Data Cache events on normal JVM termination using TCPRemoteCommitProvider

[ https://issues.apache.org/jira/browse/OPENJPA-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-230: Attachment: OPENJPA-230.patch It'd be nice to not have to synchronize. What about if we ma

[jira] Resolved: (OPENJPA-226) Change openjpa.DetachState 'fgs' setting to 'fetch-groups'

[ https://issues.apache.org/jira/browse/OPENJPA-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-226. - Resolution: Fixed > Change openjpa.DetachState 'fgs' setting to 'fetch-groups' > ---

[jira] Resolved: (OPENJPA-229) OpenJPA fails with MappedSuperclasses and Entities with the same short names

[ https://issues.apache.org/jira/browse/OPENJPA-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-229. - Resolution: Fixed > OpenJPA fails with MappedSuperclasses and Entities with the same sho

[jira] Updated: (OPENJPA-229) OpenJPA fails with MappedSuperclasses and Entities with the same short names

[ https://issues.apache.org/jira/browse/OPENJPA-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-229: Attachment: OPENJPA-229.patch This fixes the problem by changing the enhancer to not regis

[jira] Updated: (OPENJPA-229) OpenJPA fails with MappedSuperclasses and Entities with the same short names

[ https://issues.apache.org/jira/browse/OPENJPA-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-229: Component/s: kernel Fix Version/s: 0.9.8 Description: When running

[jira] Created: (OPENJPA-229) OpenJPA fails with MappedSuperclasses and Entities with the same short names

OpenJPA fails with MappedSuperclasses and Entities with the same short names Key: OPENJPA-229 URL: https://issues.apache.org/jira/browse/OPENJPA-229 Project: OpenJPA

[jira] Closed: (OPENJPA-228) Could not locate metadata for the class using alias

[ https://issues.apache.org/jira/browse/OPENJPA-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey closed OPENJPA-228. --- Resolution: Fixed Persistent classes were not enhanced prior to use. Added a better error me

[jira] Commented: (OPENJPA-228) Could not locate metadata for the class using alias

[ https://issues.apache.org/jira/browse/OPENJPA-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491537 ] Patrick Linskey commented on OPENJPA-228: - I haven't run it yet, but a couple of things look suspicious: 1.

[jira] Updated: (OPENJPA-226) Change openjpa.DetachState 'fgs' setting to 'fetch-groups'

[ https://issues.apache.org/jira/browse/OPENJPA-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-226: Attachment: OPENJPA-226.patch Here's a patch that does this. Thoughts? > Change openjpa.D

[jira] Created: (OPENJPA-226) Change openjpa.DetachState 'fgs' setting to 'fetch-groups'

Change openjpa.DetachState 'fgs' setting to 'fetch-groups' -- Key: OPENJPA-226 URL: https://issues.apache.org/jira/browse/OPENJPA-226 Project: OpenJPA Issue Type: Improvement

[jira] Resolved: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-219. - Resolution: Fixed > Reflection: negative caching would be beneficial in redeployment sce

[jira] Commented: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491458 ] Patrick Linskey commented on OPENJPA-219: - How does this compare to the leaky-patch version? > Reflection:

[jira] Assigned: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey reassigned OPENJPA-219: --- Assignee: Patrick Linskey > Reflection: negative caching would be beneficial in rede

[jira] Commented: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491316 ] Patrick Linskey commented on OPENJPA-219: - > another way to approach this would be not to cache at all, > an

[jira] Commented: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491104 ] Patrick Linskey commented on OPENJPA-219: - I agree about the mem leak problem in the patch that I created; h

[jira] Commented: (OPENJPA-221) DerbyDictionary doesn't describe a working mapping for char fields.

[ https://issues.apache.org/jira/browse/OPENJPA-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489820 ] Patrick Linskey commented on OPENJPA-221: - It's not surprising that the OpenJPA tests storeCharsAsNumbers to

[jira] Commented: (OPENJPA-221) DerbyDictionary doesn't describe a working mapping for char fields.

[ https://issues.apache.org/jira/browse/OPENJPA-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489761 ] Patrick Linskey commented on OPENJPA-221: - What happens if, without your patch, you set the DBDictionary 'S

[jira] Updated: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-219: Attachment: OPENJPA-219.patch New version of patch that uses iterated class instead of met

[jira] Updated: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-219: Attachment: (was: OPENJPA-219.patch) > Reflection: negative caching would be beneficia

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489558 ] Patrick Linskey commented on OPENJPA-182: - Some comments: 1. I don't think that we should be doing work on

[jira] Updated: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-219: Attachment: OPENJPA-219.patch I think that this patch should fix the issue, but haven't te

[jira] Created: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

Reflection: negative caching would be beneficial in redeployment scenarios -- Key: OPENJPA-219 URL: https://issues.apache.org/jira/browse/OPENJPA-219 Project: OpenJPA Is

[jira] Commented: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489536 ] Patrick Linskey commented on OPENJPA-219: - Note that we invoke Class.getDeclaredField() (and Class.getDeclar

[jira] Commented: (OPENJPA-5) OpenJPA doesn't compile with JDBC 4

[ https://issues.apache.org/jira/browse/OPENJPA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489145 ] Patrick Linskey commented on OPENJPA-5: --- We do similar work for mutable type proxies. Is there an opportunity to

[jira] Commented: (OPENJPA-211) CLONE -java.lang.VerifyError on websphere 6.1 with Spring 2.0.3 and OpenJpa 0.96/0.97

[ https://issues.apache.org/jira/browse/OPENJPA-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487951 ] Patrick Linskey commented on OPENJPA-211: - Sadly, I'm not really up-to-speed on the WebSphere integration st

[jira] Commented: (OPENJPA-91) java.lang.VerifyError on websphere after application reload

[ https://issues.apache.org/jira/browse/OPENJPA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487950 ] Patrick Linskey commented on OPENJPA-91: > Hi, Patrick, what kind of DB2 driver info we should put into the c

[jira] Commented: (OPENJPA-212) Constructor expression permits no other expressions in SELECT clause

[ https://issues.apache.org/jira/browse/OPENJPA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487948 ] Patrick Linskey commented on OPENJPA-212: - You don't have a test case handy for this by any chance, do you?

[jira] Commented: (OPENJPA-211) CLONE -java.lang.VerifyError on websphere 6.1 with Spring 2.0.3 and OpenJpa 0.96/0.97

[ https://issues.apache.org/jira/browse/OPENJPA-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487650 ] Patrick Linskey commented on OPENJPA-211: - Provided that meth is a static method, this method should run wit

[jira] Commented: (OPENJPA-184) use DB2 Diagnostic interface to report extended error diagnostics on SQL Exception

[ https://issues.apache.org/jira/browse/OPENJPA-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487365 ] Patrick Linskey commented on OPENJPA-184: - Is this issue still open? > use DB2 Diagnostic interface to repo

[jira] Resolved: (OPENJPA-182) db2 update lock syntax WITH USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-182. - Resolution: Fixed Assignee: (was: David Wisneski) I think that, aside from doc

[jira] Commented: (OPENJPA-202) after invoking LRS processing in a client by calling an @LRS annotated relationship, the next em.clear()/em.close() gets org.apache.openjpa.persistence.InvalidStateExce

[ https://issues.apache.org/jira/browse/OPENJPA-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487324 ] Patrick Linskey commented on OPENJPA-202: - Another possibility would be to detach the field if it is explici

[jira] Updated: (OPENJPA-182) db2 update lock syntax WITH USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-182: Attachment: OPENJPA-182.patch Remove forUpdate from DBDictionary.toOperation()'s signature

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487099 ] Patrick Linskey commented on OPENJPA-182: - Between Ritika's SQLServer email on the dev list and Mike's Sybas

[jira] Created: (OPENJPA-205) JPA2 Follow-Up

JPA2 Follow-Up -- Key: OPENJPA-205 URL: https://issues.apache.org/jira/browse/OPENJPA-205 Project: OpenJPA Issue Type: Improvement Components: jpa Reporter: Patrick Linskey This is an umbrella issue for al

[jira] Resolved: (OPENJPA-204) Nesting of Emebedded in Embeddable element

[ https://issues.apache.org/jira/browse/OPENJPA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-204. - Resolution: Won't Fix This is a limitation of the JPA spec. From section 9.1.34: Only

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487086 ] Patrick Linskey commented on OPENJPA-182: - > > I know that Oracle allows you to add a FOR UPDATE clause > >

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487046 ] Patrick Linskey commented on OPENJPA-182: - > > Hopefully, this will be useful for applications where there a

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486821 ] Patrick Linskey commented on OPENJPA-182: - It's probably worth noting that everything in the FetchPlan is co

[jira] Commented: (OPENJPA-168) sql optimize n rows query hint

[ https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486820 ] Patrick Linskey commented on OPENJPA-168: - Has this new feature been documented? > sql optimize n rows quer

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486819 ] Patrick Linskey commented on OPENJPA-182: - In the hint-based approach, you could set the hints on a particul

[jira] Updated: (OPENJPA-182) db2 update lock syntax WITH USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-182: Attachment: OPENJPA-182.patch For the sake of discussion, I've attached an alternate patch

[jira] Resolved: (OPENJPA-57) persistence_1_0.xsd is missing

[ https://issues.apache.org/jira/browse/OPENJPA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-57. Resolution: Won't Fix Fix Version/s: (was: 0.9.8) 0.9.7 If th

[jira] Commented: (OPENJPA-197) @Version property doesn't ensure integrity when performing the merge operation

[ https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486091 ] Patrick Linskey commented on OPENJPA-197: - Note that there are significant performance impacts to doing the

[jira] Commented: (OPENJPA-197) @Version property doesn't ensure integrity when performing the merge operation

[ https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486065 ] Patrick Linskey commented on OPENJPA-197: - I'm a bit confused. Where did Hibernate and Toplink fail? The onl

[jira] Resolved: (OPENJPA-186) Build failure of OpenJPA sources from trunk

[ https://issues.apache.org/jira/browse/OPENJPA-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-186. - Resolution: Fixed Sorry about that -- I don't think that many of us run 'mvn install' al

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485103 ] Patrick Linskey commented on OPENJPA-182: - Wow... that's a lot more DB2 locking knowledge than I've ever see

[jira] Updated: (OPENJPA-184) use DB2 Diagnostic interface to report extended error diagnostics on SQL Exception

[ https://issues.apache.org/jira/browse/OPENJPA-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-184: > This message will be appended to the persistence exception > error message already created

[jira] Created: (OPENJPA-183) OpenJPAEntityManager large transaction APIs should take class arguments to narrow behavior

OpenJPAEntityManager large transaction APIs should take class arguments to narrow behavior -- Key: OPENJPA-183 URL: https://issues.apache.org/jira/browse/OPENJPA-183

[jira] Commented: (OPENJPA-168) sql optimize n rows query hint

[ https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484288 ] Patrick Linskey commented on OPENJPA-168: - > 2. I don't think we need a FetchConfiguration instance variable

[jira] Updated: (OPENJPA-172) DSRA9250E: Operation setTransactionIsolation is not allowed during a global transaction for Shareable Connections.

[ https://issues.apache.org/jira/browse/OPENJPA-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-172: Fix Version/s: (was: 0.9.6) 0.9.7 0.9.6 is released; moving the fix

[jira] Created: (OPENJPA-169) Queries against dirty extents and flushing: should provide an option to set savepoint, flush, query, rollback to savepoint

Queries against dirty extents and flushing: should provide an option to set savepoint, flush, query, rollback to savepoint -- Key: OPENJPA-169

[jira] Created: (OPENJPA-170) Constrain types to be flushed

Constrain types to be flushed - Key: OPENJPA-170 URL: https://issues.apache.org/jira/browse/OPENJPA-170 Project: OpenJPA Issue Type: Improvement Reporter: Patrick Linskey When invoking EntityManager.

[jira] Resolved: (OPENJPA-35) In-memory Delete operation fails with active DataCache

[ https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-35. Resolution: Fixed Fix Version/s: (was: 0.9.7) > In-memory Delete operation fails

[jira] Updated: (OPENJPA-35) In-memory Delete operation fails with active DataCache

[ https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-35: --- Fix Version/s: 0.9.7 > In-memory Delete operation fails with active DataCache > -

[jira] Updated: (OPENJPA-142) Entity name is ignored when specified in the orm.xml file

[ https://issues.apache.org/jira/browse/OPENJPA-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-142: Fix Version/s: 0.9.7 Affects Version/s: 0.9.0 0.9.6 > Entit

[jira] Resolved: (OPENJPA-142) Entity name is ignored when specified in the orm.xml file

[ https://issues.apache.org/jira/browse/OPENJPA-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-142. - Resolution: Fixed Fix Version/s: (was: 0.9.7) > Entity name is ignored when s

[jira] Created: (OPENJPA-167) Named queries and no listed entities: bad error message

Named queries and no listed entities: bad error message --- Key: OPENJPA-167 URL: https://issues.apache.org/jira/browse/OPENJPA-167 Project: OpenJPA Issue Type: Bug Components: di

[jira] Updated: (OPENJPA-71) Caching primitive array types consumes excessive memory

[ https://issues.apache.org/jira/browse/OPENJPA-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-71: --- Fix Version/s: 0.9.7 Affects Version/s: 0.9.0 0.9.6 > Caching

[jira] Resolved: (OPENJPA-46) true, false not case insensitive, gets null pointer exception

[ https://issues.apache.org/jira/browse/OPENJPA-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-46. Resolution: Fixed Fix Version/s: (was: 0.9.7) Assignee: (was: Patric

[jira] Commented: (OPENJPA-35) In-memory Delete operation fails with active DataCache

[ https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479277 ] Patrick Linskey commented on OPENJPA-35: > b) When openjpa.datacache=false, the application can still obtain

[jira] Commented: (OPENJPA-71) Caching primitive array types consumes excessive memory

[ https://issues.apache.org/jira/browse/OPENJPA-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479276 ] Patrick Linskey commented on OPENJPA-71: Resolved. I changed AbstractPCData to not marshal / unmarshal arrays

[jira] Resolved: (OPENJPA-71) Caching primitive array types consumes excessive memory

[ https://issues.apache.org/jira/browse/OPENJPA-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-71. Resolution: Fixed Fix Version/s: (was: 0.9.7) > Caching primitive array types co

[jira] Updated: (OPENJPA-164) Need better logging on Java field type to SQL type mapping and exceptions

[ https://issues.apache.org/jira/browse/OPENJPA-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-164: Component/s: jdbc diagnostics Fix Version/s: 0.9.7

[jira] Commented: (OPENJPA-121) Table name defaults to the class name instead of the entity name

[ https://issues.apache.org/jira/browse/OPENJPA-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478670 ] Patrick Linskey commented on OPENJPA-121: - Tested with annotations; have not tested with XML-based entity na

[jira] Resolved: (OPENJPA-121) Table name defaults to the class name instead of the entity name

[ https://issues.apache.org/jira/browse/OPENJPA-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-121. - Resolution: Fixed > Table name defaults to the class name instead of the entity name > -

[jira] Created: (OPENJPA-163) @OneToOne should not be legal as back-pointer of @OneToMany

@OneToOne should not be legal as back-pointer of @OneToMany --- Key: OPENJPA-163 URL: https://issues.apache.org/jira/browse/OPENJPA-163 Project: OpenJPA Issue Type: Improvement

[jira] Resolved: (OPENJPA-80) Bad Escaping for LIKE in MySQL

[ https://issues.apache.org/jira/browse/OPENJPA-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-80. Resolution: Fixed > Bad Escaping for LIKE in MySQL > -- > >

[jira] Commented: (OPENJPA-162) @OrderBy on @OneToMany does not allow ordering by @Id value

[ https://issues.apache.org/jira/browse/OPENJPA-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478122 ] Patrick Linskey commented on OPENJPA-162: - I believe that the issue is that the field is not in the current

[jira] Updated: (OPENJPA-79) Please add Eclipse artifacts to svn ignore

[ https://issues.apache.org/jira/browse/OPENJPA-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-79: --- Component/s: build / infrastructure > Please add Eclipse artifacts to svn ignore > --

[jira] Updated: (OPENJPA-91) java.lang.VerifyError on websphere after application reload

[ https://issues.apache.org/jira/browse/OPENJPA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-91: --- Fix Version/s: 0.9.7 > java.lang.VerifyError on websphere after application reload >

[jira] Updated: (OPENJPA-33) Need Query Engine test bucket

[ https://issues.apache.org/jira/browse/OPENJPA-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-33: --- Component/s: build / infrastructure > Need Query Engine test bucket > ---

[jira] Updated: (OPENJPA-137) Perform parameter validation for annotated callback methods

[ https://issues.apache.org/jira/browse/OPENJPA-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-137: Fix Version/s: 1.0.0 > Perform parameter validation for annotated callback methods > -

[jira] Updated: (OPENJPA-5) OpenJPA doesn't compile with JDBC 4

[ https://issues.apache.org/jira/browse/OPENJPA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-5: -- Component/s: build / infrastructure > OpenJPA doesn't compile with JDBC 4 >

[jira] Updated: (OPENJPA-105) Put together a test suite for Enhancer

[ https://issues.apache.org/jira/browse/OPENJPA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-105: Component/s: build / infrastructure > Put together a test suite for Enhancer > ---

[jira] Updated: (OPENJPA-113) when you specify columm table="empbean" in the xml file entity id or basic type when empbean is the default table name, the mapping tool generates extra foreign key fiel

[ https://issues.apache.org/jira/browse/OPENJPA-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-113: Priority: Minor (was: Major) > when you specify columm table="empbean" in the xml file e

[jira] Updated: (OPENJPA-153) WebSphere and non-jta-data-source and default ManagedRuntime

[ https://issues.apache.org/jira/browse/OPENJPA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-153: Fix Version/s: 0.9.7 > WebSphere and non-jta-data-source and default ManagedRuntime >

[jira] Updated: (OPENJPA-93) Sequence generation in a JTA environment should not require non-JTA datasource

[ https://issues.apache.org/jira/browse/OPENJPA-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-93: --- Fix Version/s: 0.9.7 > Sequence generation in a JTA environment should not require non-JTA da

[jira] Updated: (OPENJPA-75) error message for missing query id var needs improvement

[ https://issues.apache.org/jira/browse/OPENJPA-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-75: --- Priority: Minor (was: Major) > error message for missing query id var needs improvement > --

[jira] Updated: (OPENJPA-112) Native queries and named parameters: poor error message

[ https://issues.apache.org/jira/browse/OPENJPA-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-112: Priority: Minor (was: Major) > Native queries and named parameters: poor error message >

[jira] Updated: (OPENJPA-78) Automatic runtime enhancement only works when the class is listed in the first persistence-unit

[ https://issues.apache.org/jira/browse/OPENJPA-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-78: --- Priority: Minor (was: Major) > Automatic runtime enhancement only works when the class is li

[jira] Updated: (OPENJPA-132) java.lang.NoSuchMethodError for entity with ID of type java.sql.Date

[ https://issues.apache.org/jira/browse/OPENJPA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-132: Priority: Minor (was: Major) > java.lang.NoSuchMethodError for entity with ID of type jav

[jira] Updated: (OPENJPA-46) true, false not case insensitive, gets null pointer exception

[ https://issues.apache.org/jira/browse/OPENJPA-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-46: --- Priority: Minor (was: Major) > true, false not case insensitive, gets null pointer exception

[jira] Updated: (OPENJPA-9) PCEnhancer not processing multiple PU's defined within a single persistence.xml file

[ https://issues.apache.org/jira/browse/OPENJPA-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-9: -- Priority: Minor (was: Major) > PCEnhancer not processing multiple PU's defined within a single

[jira] Updated: (OPENJPA-148) Parsing exception while using an "exploded" archive

[ https://issues.apache.org/jira/browse/OPENJPA-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-148: Priority: Minor (was: Major) > Parsing exception while using an "exploded" archive >

[jira] Commented: (OPENJPA-152) Warn or throw an exception when a persistence unit has multiple named queries with the same name

[ https://issues.apache.org/jira/browse/OPENJPA-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476813 ] Patrick Linskey commented on OPENJPA-152: - +1 to throwing an exception rather than logging. > Warn or throw

[jira] Updated: (OPENJPA-152) Warn or throw an exception when a persistence unit has multiple named queries with the same name

[ https://issues.apache.org/jira/browse/OPENJPA-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-152: Component/s: query logging Priority: Minor (was: Major) > Warn or

[jira] Commented: (OPENJPA-20) Query can return embeddable class

[ https://issues.apache.org/jira/browse/OPENJPA-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476812 ] Patrick Linskey commented on OPENJPA-20: I think of this as a feature, not a bug. Thoughts? > Query can retu

  1   2   3   4   >