[jira] Updated: (OPENJPA-1387) Unique colums automatically defined as non-nullable

[ https://issues.apache.org/jira/browse/OPENJPA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-1387: --- Attachment: openjpa-test.zip it seems that this bug is still not fixed (tested with latest

AW: providing integration tests for known bugs?

Hoi! I was now able to reproduce the issue. I've created an own small project and attached it to OPENJPA-1387 [1]. This also contains a sample for the issue which is described in OPENJPA-525 [2] Can anyone test this and show me a workaround (or reopen those 2 bugs)? txs and LieGrue, strub [1]

[jira] Reopened: (OPENJPA-1387) Unique colums automatically defined as non-nullable

[ https://issues.apache.org/jira/browse/OPENJPA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar reopened OPENJPA-1387: Reopening as per further discussion. > Unique colums automatically defined as non-nullable >

[jira] Commented: (OPENJPA-1387) Unique colums automatically defined as non-nullable

[ https://issues.apache.org/jira/browse/OPENJPA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864365#action_12864365 ] Mark Struberg commented on OPENJPA-1387: A few tips on my sample project: The NOT

[jira] Created: (OPENJPA-1651) Unique colums automatically defined as non-nullable (part 2)

Unique colums automatically defined as non-nullable (part 2) Key: OPENJPA-1651 URL: https://issues.apache.org/jira/browse/OPENJPA-1651 Project: OpenJPA Issue Type: Bug

[jira] Updated: (OPENJPA-1651) Unique colums automatically defined as non-nullable (part 2)

[ https://issues.apache.org/jira/browse/OPENJPA-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dick updated OPENJPA-1651: -- Attachment: openjpa-test.zip > Unique colums automatically defined as non-nullable (part 2) >

[jira] Closed: (OPENJPA-1387) Unique colums automatically defined as non-nullable

[ https://issues.apache.org/jira/browse/OPENJPA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dick closed OPENJPA-1387. - Resolution: Fixed Once the issue has been marked as fixed in the release notes it's confusing t

[jira] Commented: (OPENJPA-1651) Unique colums automatically defined as non-nullable (part 2)

[ https://issues.apache.org/jira/browse/OPENJPA-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864371#action_12864371 ] Michael Dick commented on OPENJPA-1651: --- Re posting Mark's comments : A few tips on

[jira] Updated: (OPENJPA-1635) Reduce lock contention in MetaDataRepository.processRegisteredClasses

[ https://issues.apache.org/jira/browse/OPENJPA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Curtis updated OPENJPA-1635: - Attachment: OPENJPA-1635.patch > Reduce lock contention in MetaDataRepository.processRegistered

[jira] Updated: (OPENJPA-1649) Refactor property processing for distributed Slice configuration

[ https://issues.apache.org/jira/browse/OPENJPA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-1649: --- Assignee: Pinaki Poddar > Refactor property processing for distributed Slice configuration

[jira] Updated: (OPENJPA-1650) Adding a slice dynamically should be done via persistence unit only

[ https://issues.apache.org/jira/browse/OPENJPA-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-1650: --- Assignee: Pinaki Poddar > Adding a slice dynamically should be done via persistence unit on

[jira] Updated: (OPENJPA-1648) Slice thread pool breaks down under high concurrency

[ https://issues.apache.org/jira/browse/OPENJPA-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-1648: --- Assignee: Pinaki Poddar > Slice thread pool breaks down under high concurrency > -

[jira] Updated: (OPENJPA-1651) Unique colums automatically defined as non-nullable (part 2)

[ https://issues.apache.org/jira/browse/OPENJPA-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-1651: --- Assignee: Pinaki Poddar > Unique colums automatically defined as non-nullable (part 2) > --

[jira] Created: (OPENJPA-1652) implement @ReturnUpdate for Sequences

implement @ReturnUpdate for Sequences - Key: OPENJPA-1652 URL: https://issues.apache.org/jira/browse/OPENJPA-1652 Project: OpenJPA Issue Type: New Feature Components: jpa Affects Versions: 1.

[jira] Created: (OPENJPA-1653) Why getting null for EntityManagerFactory and EntityManager

Why getting null for EntityManagerFactory and EntityManager Key: OPENJPA-1653 URL: https://issues.apache.org/jira/browse/OPENJPA-1653 Project: OpenJPA Issue Type: Question

Re: [jira] Created: (OPENJPA-1653) Why getting null for EntityManagerFactory and EntityManager

Injection of a persistence unit is often a container's (weblogic, in this case) responsibility. Normally, the containers do not/can not inject persistence unit/context in a entity. Session Bean/Servlet etc are normally the injection target. Depends of specific capability of the containers. So yo