[
https://issues.apache.org/jira/browse/OPENJPA-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-124:
Priority: Minor
JOnAS integration: OpenJPA should auto-detect the JOnAS transaction
I have a bidirectional mapping of a many-to-one relationship as listed
below. If I have the following code:
TestDatatypes blob = new TestDatatypes();
TestLookup lookup = new TestLookup();
SetTestDatatypes tdts = new HashSetTestDatatypes();
OpenJPA-specific metadata cannot be specified in XML descriptors
Key: OPENJPA-125
URL: https://issues.apache.org/jira/browse/OPENJPA-125
Project: OpenJPA
Issue Type: New
[
https://issues.apache.org/jira/browse/OPENJPA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-125:
Component/s: jpa
Priority: Critical
OpenJPA-specific metadata cannot be specified
EntityManagers cannot be serialized
---
Key: OPENJPA-126
URL: https://issues.apache.org/jira/browse/OPENJPA-126
Project: OpenJPA
Issue Type: New Feature
Components: kernel, jpa
Reporter:
Auto-cluster-detecting cache implementation
---
Key: OPENJPA-127
URL: https://issues.apache.org/jira/browse/OPENJPA-127
Project: OpenJPA
Issue Type: New Feature
Components: datacache
Automatic cache pre-fill on server start
Key: OPENJPA-128
URL: https://issues.apache.org/jira/browse/OPENJPA-128
Project: OpenJPA
Issue Type: New Feature
Reporter: Patrick Linskey
It'd
Streaming LOB support
-
Key: OPENJPA-130
URL: https://issues.apache.org/jira/browse/OPENJPA-130
Project: OpenJPA
Issue Type: New Feature
Components: jdbc, jpa, kernel, datacache
Reporter: Patrick
[
https://issues.apache.org/jira/browse/OPENJPA-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-131:
Priority: Minor
Dynamic property support
Dynamic property support
Key: OPENJPA-131
URL: https://issues.apache.org/jira/browse/OPENJPA-131
Project: OpenJPA
Issue Type: New Feature
Components: kernel
Reporter: Patrick Linskey
Hi,
I'm getting the following exception when I try to fetch an entity with a
java.sql.Date as the id :
java.lang.NoSuchMethodError: org.apache.openjpa.util.DateId.getId
()Ljava/sql/Date;
at mikedd.entities.SqlDatePK.pcCopyKeyFieldsFromObjectId (SqlDatePK.java
)
at
Jeff-
Why is that order bad? Is it because it violates your foreign key
constraints, or some other reason?
If it is a foreign key issue, you need to tell OpenJPA to read
foreign keys from the schema in order to ensure that SQL ordering is
done correctly. You can do this by setting the
On Feb 7, 2007, at 1:55 PM, Patrick Linskey wrote:
It's coming from the generated bytecode which expects there
to be a getId
method that returns the same type of the Id, however
java.sql.Date is using
the same ID class as java.util.Date. Do we need a separate class for
java.sql.Date?
It
Thanks, I'll open a JIRA report and take a crack at a solution.
On 2/7/07, Craig L Russell [EMAIL PROTECTED] wrote:
On Feb 7, 2007, at 1:55 PM, Patrick Linskey wrote:
It's coming from the generated bytecode which expects there
to be a getId
method that returns the same type of the Id,
java.lang.NoSuchMethodError for entity with ID of type java.sql.Date
Key: OPENJPA-132
URL: https://issues.apache.org/jira/browse/OPENJPA-132
Project: OpenJPA
Issue Type:
Can't find non-public callback methods with superclass or interface parameters
--
Key: OPENJPA-133
URL: https://issues.apache.org/jira/browse/OPENJPA-133
Project: OpenJPA
Yes, this is nice. Another good reason to use the JIRA report number in
your commit message. The strange thing is that this doesn't always seem to
work. Every once in a while, the svn commit changes don't get documented in
the JIRA report, even when the commit message indicates the JIRA
I could not figure this out in reading the OpenJPA documentation.
We have just the one database and set of tables, but we need to have two
separate Connection Pools to the same database in order to have two
different userid's.
(We want to set the priorities on the database differently for
Extra unneeded SQL joins for OneToMany relationship with fetch type EAGER
-
Key: OPENJPA-134
URL: https://issues.apache.org/jira/browse/OPENJPA-134
Project: OpenJPA
join fetch not returning duplicate references which not conforming to ejb3.0
spec
-
Key: OPENJPA-135
URL: https://issues.apache.org/jira/browse/OPENJPA-135
Project:
CommonJ WorkManager integration
---
Key: OPENJPA-136
URL: https://issues.apache.org/jira/browse/OPENJPA-136
Project: OpenJPA
Issue Type: New Feature
Components: kernel
Reporter: Patrick
[
https://issues.apache.org/jira/browse/OPENJPA-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471195
]
Patrick Linskey commented on OPENJPA-128:
-
We could also do this by specifying named queries in the
Maybe just latency? The JIRA plugin periodically scans, I think. Maybe
you just checked at a bad time?
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
23 matches
Mail list logo