Hi,
I brought down the latest mavenized code for openjpa-lib and serp, and it
all builds cleanly. But, when the tests are run, I am hitting a few
failures. I'm wondering whether these are expected, or whether I have a
configuration or setup problem.
From the output from maven, I am getting
On 7/11/06, Patrick Linskey [EMAIL PROTECTED] wrote:
1) Have we decided how to resolve the Java EE 5 dependency?
I didn't see where we had set up a maven dependency for these
interfaces. For now, I can just use my own copy, but we
should decide the formal solution.
I don't follow --
Hi Patrick,
Now that the code drops seem to be slowing down a bit, I'm wondering whether
you can give me an update on the completeness of the OpenJPA code
repository. I'm attempting to verify some of the expected functionality and
I'm failing a few test scenarios. I'm just wondering whether the
Hi,
According to the JPA spec, we can define multiple persistence-units in a
single persistence.xml file. But, when I try to use this
persistence.xmlfile as input to the PCEnhancer, it is only processing
the first
persistence-unit that is defined. I traced through the code and found that
this
According to Section 3 (J2EE Tutorials, specifically 3.2 J2EE Installation
Types), the recommended approach to using OpenJPA in a managed environment
is via the JCA rar file:
JCA: OpenJPA implements the JCA 1.0 spec, and the
openjpa-persistence.rarfile that comes in the
jca/persistence directory
On 8/15/06, Patrick Linskey [EMAIL PROTECTED] wrote:
I agree that this is something that we should work out, and is the
reason that I mentioned earlier that we might want a Kodo-specific
PersistenceProvider at the end of the day. Seems like it's in everyone's
best interests for multiple
Hi,
Looking for some guidance from more experienced Apache developers...
Is there a means of enforcing the SVN commit process to include a JIRA bug
or enhancement number so that the code changes are associated with that
particular bug or enhancement? I searched some mailing list archives and
On 8/16/06, Abe White [EMAIL PROTECTED] wrote:
I'm not currently working on those changes. If no one else
implements them I'll end up doing so at some point, but the reason I
wrote those emails describing what I had in mind was to encourage
some other motivated dev (like one who wants to
://issues.apache.org/jira/browse/OPENJPA-3
svn commit -m Brett Porter's patch to resolve OPENJPA-3 openjpa-lib/
src/test/java/org/apache/openjpa/lib/util/TestPropertiesParser.java
But to answer your other questions,
On Aug 16, 2006, at 9:10 AM, Kevin Sutter wrote:
Hi,
Looking for some guidance
,
Kevin
On 8/18/06, Craig L Russell [EMAIL PROTECTED] wrote:
Hi Kevin,
On Aug 17, 2006, at 7:16 AM, Kevin Sutter wrote:
As a start, it would be good if we had this plugin support:
http://www.atlassian.com/software/jira/docs/v3.2/svn_integration.html
Do we know if this is available for our SVN
installation. I've made a note).
Try it now.
Craig
On Aug 18, 2006, at 6:17 AM, Kevin Sutter wrote:
Craig,
I must be blind or something. I looked at OPENJPA-3 before and I
don't see
the change history. I see the attached diff file, but that won't
always
be the case with committers. I am
, but as statics.
And, it's dependent on having a Provider. Can you explain the relationship
of this class in the bigger picture and how you think it might be affected
by thes changes?
That's it to be begin with. Thanks for any pointers you can provide.
Kevin
On 8/16/06, Kevin Sutter [EMAIL PROTECTED
If I am resolving some particular JIRA bug or feature and I come across a
condition like Patrick pointed out...
if (someCondition)
doSomething;
doSomethingElse;
I would just fix it as part of the JIRA bug I was already resolving. No new
JIRA bug, no new paperwork, just resolve the issue.
Hi,
I use an IDE (Eclipse) for developing OpenJPA. Whenever I synchronize with
the OpenJPA SVN repository, I have some common, minor updates to the
svn:ignore values in the SVN properties. For example, I add the target
directory to the svn:ignore property, and I add .* to the svn:ignore
this file is on Windows).
That will cause all these files to be automatically ignored by
subversion.
TTFN,
-bd-
On Aug 22, 2006, at 9:18 AM, Kevin Sutter wrote:
Okay, it seems like there was enough positive interest to do this
change. I
just committed the changes to the SVN properties to ignore
Now that we have successfully created a patch for OPENJPA-15, what is the
process for getting this validated and hopefully accepted into SVN? I have
been able to verify that the patch can be applied, everything builds, and
the existing testcases still work. But, I'm not an expert with the code
?
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
-Original Message-
From: Kevin Sutter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 22, 2006 2:21 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: [jira] Updated: (OPENJPA-15) EJBQL grammar needs
to be updated to relfect JPA
Hi,
Has there been any investigation into providing a JPA-like implementation
that would execute in the JDK 1.4 environment? I know we have the
Java 5.0requirements for generics and enums built right into the JPA
interfaces. I
was just wondering whether anybody has investigated down-grading the
You need to be added to the openjpa-developers list within JIRA. Craig did
this for me when I became a committer. I would guess either Craig or
Patrick can do this. I looked, but I don't seem to have enough authority.
Kevin
On 8/23/06, Abe White [EMAIL PROTECTED] wrote:
I'd like to apply
. Thanks.
On 8/24/06, Bryan Noll [EMAIL PROTECTED] wrote:
See this... Craig gave some good instructions...
http://mail-archives.apache.org/mod_mbox/incubator-open-jpa-dev/200608.mbox/browser
Kevin Sutter wrote:
How do we go about updating the main incubator page for OpenJPA (
http
Hi,
I'm looking to start a conversation on how we can coordinate timely
verification of patch submissions. As you have probably noticed, Catalina
and I have been working on a patch for OPENJPA-15 (
http://issues.apache.org/jira/browse/OPENJPA-15). Granted, we have had a
couple of miscues as we
BEA Systems, Inc.
-Original Message-
From: Kevin Sutter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 30, 2006 2:50 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Creating sandbox branches
Still looking for some response to this request... Looking at other
incubator
Yep, me too. Ton of errors with the latest updates...
On 9/7/06, Jacek Laskowski [EMAIL PROTECTED] wrote:
On 9/7/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: awhite
Date: Thu Sep 7 10:51:05 2006
New Revision: 441158
URL: http://svn.apache.org/viewvc?view=revrev=441158
Log:
Much better now. Thanks, Abe.
On 9/7/06, Abe White [EMAIL PROTECTED] wrote:
Is it me who experiences troubles with building OpenJPA after the
refactoring?
Sorry. Should be fixed now.
___
Notice: This email message,
Hi,
It seems that if I map an ID to an Identity Column, then, OpenJPA
automatically returns a type BigDecimal? I am not using this type
anywhere. It does not happen with other Integer or Long mappings, just with
generated strategy.
@Id
@GeneratedValue(strategy=GenerationType.IDENTITY)
Agree. The openjpa-version.jar should be sufficient for distribution.
Kevin
On 9/29/06, Patrick Linskey [EMAIL PROTECTED] wrote:
Hi,
Currently, the openjpa-version.zip that gets built in the
openjpa-project module contains all the individual module jars *and* the
openjpa-all-version.jar. Is
-0
Although it looks like you already have the three +1 votes to publish the
0.9.5 release, I'm hesitant with this publish since the current OpenJPA
implementation is using internal WebSphere methods. I knew about the
problem of not using the TransactionSynchronizationRegistry interface
, Marc Prud'hommeaux wrote:
Kevin-
On Oct 18, 2006, at 2:43 PM, Kevin Sutter wrote:
-0
Although it looks like you already have the three +1 votes to
publish the
0.9.5 release, I'm hesitant with this publish since the current
OpenJPA
implementation is using internal WebSphere methods. I
Hi,
A recent discussion concerning a patch for OPENJPA-63 (
http://issues.apache.org/jira/browse/OPENJPA-63http://issues.apache.org/jira/browse/OPENJPA-63?page=comments#action_1214)
has prompted a question that Patrick and I felt should be brought out into a
public discussion. It turns out
On 10/25/06, Abe White [EMAIL PROTECTED] wrote:
I thought we (OpenJPA) supported the mapping of Collections of
embedded
types.
OpenJPA never supported this. It was accidentally left in from the
Kodo docs.
Okay, was this a JDO feature? Does it still make sense to have OpenJPA
support
it provides a proprietary interface to register
for
+ * synchronization and obtain transaction ids.
+ *
+ * P
+ * WASManagedRuntime provides the wrapper classes needed to interact with
the
+ * WAS proprietary interface and the OpenJPA kernel.
+ *
+ * @author Michael Dick, Kevin Sutter
+ */
+public class
On 10/27/06, Abe White [EMAIL PROTECTED] wrote:
Kodo has additional performance and caching features, so there may be
hotspots in OpenJPA that don't exist in Kodo.
Fair enough. But, unless Kodo is replacing the JPQL parsing, I don't see
how you can get around this problem. I suppose it's
This is probably most directed at Marc since he did the first snapshot
release, but others may have input as well...
I'm looking to cut another snapshot release so that we can include the
updates for the WebSphere ExtendedJTATransaction interface, along with other
changes that have recently been
Abe,
I've got a couple of questions about this change...
1. What was changed in serp that required this change? Without the update
to serp v1.12, the only build problem I am having is with OpenJPA testcases,
not the shipped source code. So, what was the required update.
2. Shouldn't we have
To: open-jpa-dev@incubator.apache.org
Subject: Re: svn commit: r471080 -
/incubator/openjpa/trunk/openjpa-lib/pom.xml
On Nov 6, 2006, at 12:21 PM, Kevin Sutter wrote:
Abe,
I've got a couple of questions about this change...
1. What was changed in serp that required this change
+1
On 11/9/06, Abe White [EMAIL PROTECTED] wrote:
+1
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be
immediately return this
by email and then delete it.
-Original Message-
From: Kevin Sutter [mailto:[EMAIL PROTECTED]
Sent: Friday, November 10, 2006 7:28 AM
To: open-jpa-dev@incubator.apache.org
Subject: [RESULT][VOTE] Is JDK 1.3 support required?
Although we have started to process
I agree. I will volunteer myself for the next one release...
On 11/10/06, Patrick Linskey [EMAIL PROTECTED] wrote:
Agreed. I'll go further and nominate someone not employed by BEA, unless
it's Eddie, who doesn't do hands-on OpenJPA coding in his day job.
-Patrick
--
Patrick Linskey
BEA
+1 for the 0.9.6 release
On 11/13/06, Craig L Russell [EMAIL PROTECTED] wrote:
On Nov 13, 2006, at 5:33 AM, Geir Magnusson Jr. wrote:
Marc Prud'hommeaux wrote:
Geir-
On Nov 12, 2006, at 11:38 PM, Geir Magnusson Jr. wrote:
I see two issues.
The first, which I'm not so sure of, is that
Patrick,
Not getting a lot of activity on this thread yet... I'll kick in my two
cents worth...
I agree with your overall direction -- attempting to keep the annotation
support in synch with the xml support as outlined in the JPA spec. All
annotations defined by the JPA spec seem to have a
Hi,
Some experimenting with the @IdClass support is producing a strange
exception message when attempting to map an id field of type byte[].
According to the OpenJPA documentation, we need to use an Identity Class to
use byte[] as the id field type. Something like this:
@Entity
@IdClass
Don,
One clarification...
On 1/1/07, Don Brady [EMAIL PROTECTED] wrote:
This is under WebSphere 6.1.
Are you attempting to use OpenJPA with standard WebSphere 6.1 (ala the
DeveloperWorks article that Roland and I wrote --
Marc,
Concerning the infrastructure for sql batching support... Do you mean that
this support is pluggable into the OpenJPA runtime? That is, is there a
pluggable interface for other vendors to provide support for sql batching?
Or, is it just that the runtime could be updated to support sql
Craig,
I'm not an expert with namespaces, but it would be something along the lines
of first defining the openjpa namespace and then specifying the attributes
qualified by this namespace. We would also need to provide a schema for
this openjpa namespace. Something like this, following on from
Looking for some assistance (that is, background information) on how the
orm.xml parsing is supposed to work. I'm attempting to specify some entity
listeners in my orm.xml, but I continue to get the following TRACE message:
322664 my persistence unit TRACE [main] openjpa.MetaData - OpenJPA
On 1/17/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
I think we should ask our selves, what does a user expect to happen
and make that the default. If every JPA implements this with the
loaded+fetchgroup style by default, and OpenJPA doesn't that would be
quite surprising to users and will
elements is a valid question.
Any volunteers?
Kevin
On 1/16/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
That indeed does sound like a better solution.
On Jan 16, 2007, at 6:12 AM, Kevin Sutter wrote:
Craig,
I'm not an expert with namespaces, but it would be something along
the lines
Abe,
On 1/22/07, Abe White [EMAIL PROTECTED] wrote:
OpenJPA does not log exceptions that are thrown to your code.
So the assumption is that the caller will log the appropriate
exception-related message if such an exception is caught?
The processing that I am used to is to log any
Thank you, Albert, for your experimentation. The updated schema definition
(openjpa_orm_1_0.xsd) and the example openjpa_orm.xml seems to be what we
are looking for. I guess the only concern is whether we can count on other
JPA implementations to ignore this extra schema definition and just
Hi,
We've noticed that when EntityManager.clear() is invoked, an implicit
flush() is performed. Although the spec is cloudy in this area, I don't
think this processing is correct. The javadoc is as follows for clear():
/**
* Clear the persistence context, causing all managed
* entities to
would also like to see a CTS test made for this case. Do we have a
channel through BEA or IBM for requests for CTS test cases?
Another recent example is the EntityManager.getDelegate behavior
which surely should be a candidate for a CTS test.
Craig
On Jan 30, 2007, at 2:32 PM, Kevin Sutter wrote
Another possibility is that you need to explicitly declare the classes that
you want processed for automatic table creation via the class../class
elements. Scanning for available Entity classes won't work when attempting
to auto create the tables.
Kevin
On 1/30/07, Marc Prud'hommeaux [EMAIL
Yeah, I tend to agree. Just wanted to get something out there for the fix
that was provided... And, doing it this way allows me to experiment more
with getting these line ending characters correct... :-) JK!
On 1/31/07, Craig L Russell [EMAIL PROTECTED] wrote:
I'd prefer to see a separate
I see that they have a plugin for Eclipse, but I haven't tried it yet. It
doesn't look like it supports IntelliJ. On the surface, the conversion and
usage looks doable and would satisfy the failed testcase problem.
My question is whether it's worth the effort. If we have a testcase that
has
:-) His past comes back to haunt him... :-) Nice catch, Marc.
On 2/1/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
+ taskdef name=kodoc
classname=org.apache.openjpa.ant.PCEnhancerTask/
Shouldn't that be openjpac? Or maybe just enhance?
On Feb 1, 2007, at 2:03 PM, [EMAIL
I'm okay with the single line convention. I'm flexible. I'll change these
two comment blocks if that's the direction we want to go.
On 2/2/07, Patrick Linskey [EMAIL PROTECTED] wrote:
Hi,
To date, almost all of the OpenJPA code uses single-line-style comments
inside method blocks, instead
For some reason, my reply seems to have gotten lost... I don't care which
way we do it. I'm flexible. If we decide to go with the single line
comments, then I'll change the two blocks that Patrick pointed out in the
original note.
P.S. I kind of side with Geir on this. I just use Eclipse to
I'd agree with this assessment. New Features are bigger pieces of work --
more design, documentation, marketing, etc. Improvements are smaller bits
of work. Still may need some documentation tweaks, but these type of
changes would not make a big splash with marketing.
On 2/5/07, Dain
Rahul,
Where do I get it?
On 2/5/07, Rahul Thakur [EMAIL PROTECTED] wrote:
Hi,
I am pleased to announce the release of OpenJPA Maven Plugin version
1.0-alpha.
This release includes:
1) Mojo to invoke OpenJPA PCEnhancer tool on mapped persistable
classes.
2) Plugin documentation.
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
-
From: Kevin Sutter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 3:13 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: JIRA / svn integration
Yes, this is nice. Another good reason to use the JIRA
report number in
your commit message. The strange thing
Hi,
I've noticed that we capture the current call stack (via an
IllegalStateException creation) when close() is invoked on the
AbstractBrokerFactory and when free() is invoked on BrokerImpl. Then, if or
when assertOpen fails we include this exception (and call stack) as the
cause of a new
+1
Either move to the Geronimo version or get the dev.java version updated.
Either way, just so that we're using a spec-compliant version of the API.
Thanks!
Kevin
On 2/8/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
It turns out that the JPA API we've been building against (the one
from
Hi,
After synching up with the latest changes in SVN, I am hitting an
intermittent problem while running the new tests in
openjpa-persistence-jdbc. Every once in a while, I am getting hundreds of
messsages like the following:
Running
and let us know if the stack trace changes?
On Feb 10, 2007, at 6:21 PM, Kevin Sutter wrote:
Hi,
After synching up with the latest changes in SVN, I am hitting an
intermittent problem while running the new tests in
openjpa-persistence-jdbc. Every once in a while, I am getting
hundreds
Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement
(Unknown
which sounds like an issue with the xerces parser. Don't you hate
exceptions from parsers rather than error messages?
Craig
On Feb 10, 2007, at 8:08 PM, Kevin Sutter wrote:
Marc,
It took a while
Abe,
Thanks for the feedback. I know that we have been running with both the IBM
and Sun JDK's, but let me get together with my performance team and discuss
your concerns. We will try to provide more concrete data on these updates.
I understand your concerns, but instead of immediately backing
I have created OPENJPA-141 (
https://issues.apache.org/jira/browse/OPENJPA-141) to track these issues.
Kevin
On 2/12/07, Abe White [EMAIL PROTECTED] wrote:
==
---
is to dynamically
generate a subclass to the entity (which isn't possible if the entity
is final).
On Feb 12, 2007, at 4:33 AM, Kevin Sutter wrote:
Marc (and others),
Shouldn't OpenJPA be detecting these final classes and issuing an
error
message?
Kevin
On 2/12/07, Marc Prud'hommeaux
Just to add a me too to help out Dain... I have also seen this problem
while debugging other problems. At the time I figured I was doing something
wrong, so I didn't report it. I'll see if I can reproduce it again and
provide more insights.
Kevin
On 2/13/07, Marc Prud'hommeaux [EMAIL
Hi,
There have been several requests about the performance analysis that we've
been doing. This performance analysis has resulted in three JIRA Issues
thus far (OPENJPA-115, OPENJPA-138, and OPENJPA-141) with more to come, I'm
sure. We're not ready to go public with the specific results yet,
)
--
Key: OPENJPA-141
URL: https://issues.apache.org/jira/browse/OPENJPA-141
Project: OpenJPA
Issue Type: Sub-task
Components: jpa
Reporter: Kevin Sutter
Assigned To: Kevin Sutter
But, more often than not, if I don't include the -Dtest=false stanza, the
tests will fail as described earlier in this thread.
If nobody else is experiencing this, maybe it's a JDK thing again. I could
try to reproduce with the Sun JDK. Any other thoughts?
Kevin
On 2/12/07, Kevin Sutter [EMAIL
out by just hard-coding the data-seeding logic into the test case,
which I've been meaning to do since you reported the problem, but
just haven't had time yet.
I'll try to get it done today...
On Feb 15, 2007, at 9:29 AM, Kevin Sutter wrote:
I am still experiencing the same problem. Am I
Abe,
This change is causing problems in an application server environment. I
pulled in this change this morning, re-built, and tried our perf benchmark
(SunOne with OpenJPA) and I get the following exception:
Caused by: 0|false|0.9.7-incubating-SNAPSHOT
The WebSphere Transaction API does not allow for suspension of a
transaction. Even if we move to the official JPA transaction API
(TransactionSynchronizationRegistry), there is no suspend method available.
I would have to better understand OpenJPA's need for the transaction
suspension before
,
returning from the method would resume the suspended transaction. If
needed, an Object returned from the method could contain the results
of the method.
Craig
On Feb 19, 2007, at 8:14 AM, Kevin Sutter wrote:
The WebSphere Transaction API does not allow for suspension of a
transaction. Even if we
, 2007, at 12:37 PM, Kevin Sutter wrote:
Excellent use of the Java EE features! :-)
Kevin
On 2/19/07, Craig L Russell [EMAIL PROTECTED] wrote:
It is possible to suspend a transaction by the standard Java EE
technique. Unfortunately, this might be considered a hack, but AFAIK
it's perfectly
Segu,
In the future, could you please reference the JIRA Issue in your commit
message? Just a simple OPENJPA-155. Capturing reference to the
Column[]... would automatically put the SVN changed lines into the Jira
Issue for easy reference. Thanks.
Kevin
On 2/20/07, [EMAIL PROTECTED] [EMAIL
Hans,
Instead of managing the lifecycle of the EntityManagerFactory and
EntityManager yourself, why not use injection of the EM via
@PersistenceContext? There are several examples of this usage in the JPA
spec and the OpenJPA documentation.
Kevin
On 2/21/07, Hans Prueller [EMAIL PROTECTED]
Patrick,
This is really strange. At first, I thought this was just another case of
the line ending character problem. But, when I look at the svn history of
the DB2Dictionary.java file, it's as if this latest commit is the only
record of the file. But, when I look at previous revisions, the
for some agreement (or disagreement) before doing any of the
cleanup.
Kevin
On 2/22/07, Kevin Sutter [EMAIL PROTECTED] wrote:
Patrick,
This is really strange. At first, I thought this was just another case of
the line ending character problem. But, when I look at the svn history
Thanks for the confirmation of the optimization ideas. We'll work through
the issues and come back with another version.
On 2/22/07, Patrick Linskey [EMAIL PROTECTED] wrote:
+1. FTR, despite Abe's and my barrage of design suggestions, I love the
optimization. Abe: good call on using it for
My original thought with the code changes is that when the SystemClassLoader
is returned, the processing is no worse than it was before the change.
Granted, it's no better either, but I was focused on the Container-managed
environment...
Marc's suggestion would seem to resolve the issue by
I have backed out the original changes via svn revision 512327 -- just did
it this morning. Dave will create a JIRA report for this optimization so
that we can work through the issues and then we'll integrate a new set of
changes.
Kevin
On 2/22/07, Abe White [EMAIL PROTECTED] wrote:
3.
Patrick,
I'm a little confused with all of these updates you are doing with the JIRA
Issues. Most of the updates are related to specifying a Fix Version of
0.9.7. Does this mean you are planning on having all of these Issues
resolved for 0.9.7? Or, do you think this field specifies which
named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
-Original Message-
From: Kevin Sutter [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 01, 2007 4:55 AM
To: open-jpa-dev
Hi,
Can someone explain the difference between the @Dependent annotation and the
cascade=ALL (or any of the cascading actions) element of the relationship
annotations? From what I can tell in the documentation, they provide
similar function. Maybe the @Dependent (and associated
Thanks, Abe. This explanation helps a great deal. Should we update the
documentation with some of this information?
Kevin
On 3/7/07, Abe White [EMAIL PROTECTED] wrote:
First, dependent should be compared to cascade=REMOVE rather than (or
in addition to) cascade=ALL.
cascade=REMOVE means
Just curious,
Has there been any testing with Java 2 Security enabled and OpenJPA? I'm
hitting a semi-intermittent problem (it doesn't seem to show up on all
machines) which results in an NPE coming out of the
javax.persistence.Persistence.createEntityManager method. I know we have no
control
Hi,
John is having some problems with posting to the open-jpa-dev mailing list
via his e-mail account, so I am posting this message for him so that we can
start this conversation...
=
Fellow OpenJPAers, :)
As Craig had brought up (through Scott
bug with Windows
file handing.
Good idea. I was assuming that it was a standard file (ie. persistence.xml).
Let me try that as well.
Kevin
On Mar 13, 2007, at 5:55 AM, Kevin Sutter wrote:
Just curious,
Has there been any testing with Java 2 Security enabled and
OpenJPA? I'm
hitting
Craig,
I like the idea of putting together a roadmap. I had started this
conversation with Patrick earlier this week, so your timing is perfect.
Concerning the 0.9.7 release... I would like to shut down the development
of this release somewhat soon. We have produced so many CTS-related,
, which will contain many
bug fixes and performance improvements. Kevin Sutter has been
volunteered to cut the release once we decide there is enough done
on the list.
The JSR 220 TCK was passed.
JIRA now contains numerous proposed bug fixes and feature
enhancements, tentatively
On 4/10/07, Abe White [EMAIL PROTECTED] wrote:
OpenJPA expands the available ordering syntax. See ??? in the
Reference
Guide for details.
I'm assuming this should be referring to our Large Result Set
capabilities.
LRS capabilities don't affect OrderBy. The note should be
Dain,
When you mention the CMP test suite are you referring to the CTS TCK? If
so, how does CMP correspond to EJB's and their use of JPA (in the EJB3
sense)? I understand your request. I'm just trying to understand whether
this is a requirement or just a bad test case in the CTS TCK. The JPA
Question...
Now that Abe has graciously resolved OpenJPA-134 (
https://issues.apache.org/jira/browse/OPENJPA-134), I would really like to
see this get included into the 0.9.7 release. This fix looks to resolve the
redundant sql joins that were dogging the performance of certain
benchmarks. By
candidate
because it's the release candidate that the community should be
testing. And if this patch has any issues, we'll hear about it.
Craig
On Apr 11, 2007, at 2:09 PM, Kevin Sutter wrote:
Question...
Now that Abe has graciously resolved OpenJPA-134 (
https://issues.apache.org/jira
Armad,
This exception doesn't mean the table doesn't exist in the database, it
means that the metadata doesn't define a proper table for this persistence
type. Either the annotations or the xml are not properly defining the table
for this persistence type. It would be good to see the complete
Armad,
Your error seems to have shifted. The original posting indicated that the
exception text was concerning the table metadata:
org.apache.openjpa.persistence.ArgumentException: No table was given for
persistent type...
But, your latest append indicates that the actual database table does
1 - 100 of 212 matches
Mail list logo
