+1
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential,
+1
-Original Message-
From: Michael Dick [mailto:[EMAIL PROTECTED]
Sent: April 16, 2007 12:10 PM
To: open-jpa-dev@incubator.apache.org
Subject: [VOTE] publish openjpa 0.9.7-incubating release
OpenJPA People-
In accordance with the Incubating Releases guidelines at
OpenJPA People-
In accordance with the Incubating Releases guidelines at
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
, I've taken another shot at making a release and start a vote on publishing
a 0.9.7-incubating release of OpenJPA.
The release candidate is at:
[
https://issues.apache.org/jira/browse/OPENJPA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489156
]
Michael Dick commented on OPENJPA-153:
--
Confirming Kevin's comments above, support for non-jta-datasources is
[
https://issues.apache.org/jira/browse/OPENJPA-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick resolved OPENJPA-184.
--
Resolution: Fixed
Resolving issue per Ritika's comments on the dev mailing list.
use DB2
+1 for release
I ran Robert's Donkin's RAT program on the release, and it reported a
few anomalies:
No license:
openjpa-project-0.9.7-incubating-source/CHANGES.txt
ok: No IP here
openjpa-project-0.9.7-incubating-source/RELEASE-NOTES.html
don't know: I'd approve it but others in the
openjpa-project-0.9.7-incubating-source/openjpa-jdbc/src/main/
resources/org/apache/openjpa/jdbc/schema/schemas-doctype.rsrc
don't know: This is a dtd describing document type schemas. It
doesn't appear to be generated and certainly has some IP in it.
I think that our parser doesn't deal
Phill-
Was there a JIRA issue created for this? I didn't see one.
I do recall not being able to reproduce it when you mentioned it, so
I didn't proceed with entering one...
On Apr 16, 2007, at 12:11 PM, Phill Moran wrote:
I am still getting a duplicate query where no duplicate exists.
On 4/16/07, Hans J. Prueller [EMAIL PROTECTED] wrote:
363 lbsims INFO [RMI TCP Connection(3)-127.0.1.1] openjpa.jdbc.JDBC -
OpenJPA will now connect to the database to attempt to determine what type
of database dictionary to use. To prevent this connection in the future,
set your
Armad,
Are you using GlassFish with OpenJPA? If yes, there is a special integration
with the Toplink code to be able to drop and create tables at deployment time.
No other JPA provider has this support. I was looking at adding the same level
of support for OpenJPA but the existing options
[
https://issues.apache.org/jira/browse/OPENJPA-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Sutter reopened OPENJPA-184:
--
Assignee: David Wisneski
Sorry, I'm going to re-open this Issue. I don't see any mention
Hi all,
I've come across another defect since moving openjpa to tomcat's shared/lib
shared classloader. Unfortunately, try as I might, I can't reliably
reproduce this one, so I'm posting the problem here in the hope that
somebody might be able to offer some suggestions.
The problem is that one
Sounds fair.
Ideally, we should figure out some way to mark things as
resolved-but-undocumented in JIRA. This would be particularly useful to
facilitate the process of building release notes that discuss issues
that are maybe underdocumented.
-Patrick
-Original Message-
From: Kevin
Patrick Linskey wrote:
Also, could you describe the use case where it makes sense to change an
entity name in XML? To date, I've mostly been of the opinion that
changing entity names in XML is a pretty bad thing, as it will cause any
queries that relied on the annotation-specified (or
Ah yes, I can see now that an annotation would be better for
this. I just had all my metadata in XML. Isn't there an
XML-metadata-complete attribute or something that might force
you to use XML though?
Yes, there is one of those. I guess it's necessary in that case.
IMO, we shouldn't even
Patrick Linskey wrote:
Ah yes, I can see now that an annotation would be better for
this. I just had all my metadata in XML. Isn't there an
XML-metadata-complete attribute or something that might force
you to use XML though?
Yes, there is one of those. I guess it's necessary in that
16 matches
Mail list logo
