RE: JIRA / svn integration

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 i

RE: Cache with two ConnectionFactories?

There are a lot of things that you could do. The simplest, and least cache-effective, would be to have two different EMFs that each have their own caches. These caches could be linked together (using the sjvm remote commit provider), so that data would stay consistent, but otherwise, this would be

[jira] Created: (OPENJPA-136) CommonJ WorkManager integration

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 Linsk

[jira] Commented: (OPENJPA-128) Automatic cache pre-fill on server start

[ 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 DataCach

[jira] Created: (OPENJPA-135) join fetch not returning duplicate references which not conforming to ejb3.0 spec

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: OpenJ

[jira] Created: (OPENJPA-134) Extra unneeded SQL joins for OneToMany relationship with fetch type EAGER

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 Issu

Cache with two ConnectionFactories?

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 acc

Re: JIRA / svn integration

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 report.

[jira] Created: (OPENJPA-133) Can't find non-public callback methods with superclass or interface parameters

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

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

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: Bu

RE: Exception when using java.sql.Date as an id

FTR, I think that I prefer separate classes as well; it's clearer, and avoids any ambiguity with other subclasses in the future. -Patrick -- Patrick Linskey BEA Systems, Inc. ___ Notice: This email message, together with any

Re: Exception when using java.sql.Date as an id

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

Re: Exception when using java.sql.Date as an id

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 looks

RE: Exception when using java.sql.Date as an id

> 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 looks like we either need a separate type for j

Re: Bug in insert of bidirectionally mapped many-to-one relationships

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 "

Exception when using java.sql.Date as an id

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 mikedd.entities.SqlDatePK

[jira] Created: (OPENJPA-131) 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 Currently

[jira] Updated: (OPENJPA-131) Dynamic property support

[ 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 > > >

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

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 Lin

[jira] Created: (OPENJPA-129) Oracle transaction log / DataCache integration

Oracle transaction log / DataCache integration -- Key: OPENJPA-129 URL: https://issues.apache.org/jira/browse/OPENJPA-129 Project: OpenJPA Issue Type: New Feature Components: datacache, j

[jira] Created: (OPENJPA-127) Auto-cluster-detecting cache implementation

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

[jira] Created: (OPENJPA-128) Automatic cache pre-fill on server start

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 b

[jira] Created: (OPENJPA-126) EntityManagers cannot be serialized

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:

[jira] Updated: (OPENJPA-125) OpenJPA-specific metadata cannot be specified in XML descriptors

[ 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

[jira] Created: (OPENJPA-125) OpenJPA-specific metadata cannot be specified in XML descriptors

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 Featur

Bug in insert of bidirectionally mapped many-to-one relationships

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(); Set tdts = new HashSet(); tdts.add(blob);

[jira] Updated: (OPENJPA-124) JOnAS integration: OpenJPA should auto-detect the JOnAS transaction manager

[ 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 mana

[jira] Created: (OPENJPA-124) JOnAS integration: OpenJPA should auto-detect the JOnAS transaction manager

JOnAS integration: OpenJPA should auto-detect the JOnAS transaction manager --- Key: OPENJPA-124 URL: https://issues.apache.org/jira/browse/OPENJPA-124 Project: OpenJPA