://java.sun.com/
products/jdo
408 276-5638 mailto: [EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!
--
Marc Prud'hommeaux
BEA Systems, Inc.
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities
Unfortunately, you do need to be able to connect to a database in
order to generate a SQL DDL. I think it would be a pretty minor
project to remove this restriction, but as of right now, it exists.
Note that you can generate a database-independent schema XML file
without connecting to
David-
That is very interesting.
Did you also take a look at the one at http://sourceforge.net/
projects/high-scale-lib ? They say its performance only shines for
high thread/cpu counts, but it might be interesting to see where its
numbers lie in the range.
On May 29, 2007, at 11:01
group already but
this is part of the migration so it might not be set up yet.
Craig
On May 25, 2007, at 11:12 AM, Marc Prud'hommeaux wrote:
I'll try to look into this sometime this evening (PST).
On May 25, 2007, at 11:07 AM, Joshua Slive wrote:
On 5/25/07, Craig L Russell [EMAIL
I'll try to look into this sometime this evening (PST).
On May 25, 2007, at 11:07 AM, Joshua Slive wrote:
On 5/25/07, Craig L Russell [EMAIL PROTECTED] wrote:
Hi Joshua,
I would appreciate some help here. I have no time to troll through
all other Apache web sites looking for models.
Is
Praveen-
On May 24, 2007, at 7:06 AM, Praveen G wrote:
Hi,
We are struck with 2 problems:
1. We have written orm.xml file for our application and we are
getting the following exception. We are also attaching our orm.xml
and persistance.xml files for your reference.
[openjpac]
[
https://issues.apache.org/jira/browse/OPENJPA-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498746
]
Marc Prud'hommeaux commented on OPENJPA-242:
I think that EHCache is the only one to support the JSR107
I've created https://issues.apache.org/jira/browse/INFRA-1254 with
this request (David Blevin mentioned last time we had Continuum
issues that the best way to approach it was to make a JIRA issue).
On May 23, 2007, at 7:47 AM, Craig L Russell wrote:
We need to fix the continuum builds
We recently discussed committing ourselves to the next release being
OpenJPA 1.0.0. The general consensus seems to be in favor, so I'm
putting it to a vote.
+1 Make the current release be 1.0.0-SNAPSHOT, which indicates that
the next released version will be 1.0.0
-1 Leave the current
We recently discussed committing ourselves to the next release being
OpenJPA 1.0.0. The general consensus seems to be in favor, so I'm
putting it to a vote.
+1 Make the current release be 1.0.0-SNAPSHOT, which indicates that
the next released version will be 1.0.0
-1 Leave the current
about going through the open
JIRA issues and really making sure that we'll address the major
functionality, performance, and usability deficiencies. So this will
affect the schedule but not the naming of the release.
Craig
On May 23, 2007, at 12:30 PM, Marc Prud'hommeaux wrote:
We recently
I agree: let's just do the move now and deal with any breakage as we
find it.
On May 22, 2007, at 4:47 PM, Craig L Russell wrote:
Well, having both copies I think would possibly lead to confusion.
I think it's cleaner just to move the repo and svn switch relocate
when it's done.
Gokhan-
On a related note, does the build process support/plan to support
TestNG tests or should I stick to junit?
I looked into this a little while back: Maven supposedly supports
both TestNG and JUnit used together in tandem, but I was never able
to get it working at all. The bugs I
Running svn switch https://svn.apache.org/repos/asf/openjpa/trunk;
worked for me.
On May 22, 2007, at 8:00 PM, Craig L Russell wrote:
I haven't been successful yet in switching my local workspace. When
someone gets it, please send out what you did...
Craig
On May 22, 2007, at 7:38 PM,
I've gone ahead and renamed the versions in the pom.xml files from
0.9.8-incubating-SNAPSHOT to 0.9.8-SNAPSHOT and built and
deployed a snapshot:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/
openjpa/apache-openjpa/0.9.8-SNAPSHOT/apache-openjpa-0.9.8-SNAPSHOT-
[
https://issues.apache.org/jira/browse/OPENJPA-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-237.
Resolution: Fixed
Fix Version/s: 0.9.8
Committed patch.
Value.setAliases
I hope the bruises heal soon btw :)
Time heals all wounds. At least, that's what I'm told.
On May 21, 2007, at 10:09 AM, James.Strachan wrote:
Marc Prud'hommeaux wrote:
I think this is a very worthwhile project. James and a few others
excoriated me about this issue over beers
[
https://issues.apache.org/jira/browse/OPENJPA-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497575
]
Marc Prud'hommeaux commented on OPENJPA-148:
I've gone ahead and applied OPENJPA-148-2.patch
Praveen-
It looks like we might be calling getInt() on a column type that
isn't compatible. How are the columns defined for your tables? For
example, if DB_PARTITION is really a VARCHAR, then I can see this
happening.
If that is the case, then you might be able to get around it by
I personally lean towards just bumping it up to 1.0 and cutting a
release as soon as possible after we complete the incubator-TLP
process. A release number 1.0 suggests to so many people that a
product is not production-ready, and OpenJPA is so mature and in use
in so many
: datacache
Affects Versions: 0.9.7, 0.9.6, 0.9.0
Reporter: Marc Prud'hommeaux
Priority: Minor
JSR 107 (JCache: http://jcp.org/en/jsr/detail?id=107 ) support would enable
OpenJPA to integrate its data cache with supporting products in a transparent
way. This would allow us
On May 19, 2007, at 5:03 PM, Marc Prud'hommeaux (JIRA) wrote:
JCache (JSR 107) support in the OpenJPA DataCache
-
Key: OPENJPA-242
URL: https://issues.apache.org/jira/browse/
OPENJPA-242
Project
Sadly, no. We don't have any built-in support for historical support
at this time, although we have thought for a long time that this
would be a great feature to have.
You can, of course, do it yourself manually with a bunch of
persistent Date fields, but I agree that this is pretty
I think this is a very worthwhile project. James and a few others
excoriated me about this issue over beers after JavaOne last week,
and, while the bruises from their rhetorical assault are still
healing, their observations about the comparative out of the box
ease of use OpenJPA
I recall Patrick was looking into replacing some of our slower Map
plumbing recently. If he is still working on that, it would be
interesting to see if these could be dropped in to see what the
performance differences were.
On May 16, 2007, at 9:21 PM, Craig L Russell wrote:
Don't
That is correct: the reversemappingtool only currently supports
generating an orm.xml file. We would like to add support for
generating annotations someday, but it is not there yet.
Take a look at the reversemapping example in a recent openjpa
snapshot for an example of running the
Feature
Components: jdbc, jpa
Affects Versions: 0.9.7, 0.9.6, 0.9.0
Reporter: Marc Prud'hommeaux
The reverse mapping tool currently only generates mappings in a separate
orm.xml file. It would be useful if there was an option to instead generate
annotations
. in classes, and obviously the ability to
not write any XML at all and put everything in annotations instead.
-Patrick
On 5/16/07, Gokhan Ergul [EMAIL PROTECTED] wrote:
Marc Prud'hommeaux wrote:
That is correct: the reversemappingtool only currently supports
generating an orm.xml file. We would
/
implementation details? This mailing list / jira or somewhere else?
Gokhan.
Marc Prud'hommeaux wrote:
I've gone ahead and created https://issues.apache.org/jira/browse/
OPENJPA-239 in order to track comments and patches for this issue.
On May 16, 2007, at 12:56 PM, Patrick Linskey wrote
Sanku-
If you look in Main.java, you can see we are passing the System
properties to the EntityManager creation process:
EntityManagerFactory factory = Persistence.
createEntityManagerFactory(hellojpa,
System.getProperties());
In the parent directory's build.xml file,
James-
It should be possible. The easiest way (and the most implementation-
agnostic) would be to simply generate the classes with the
appropriate mapping annotations, and then just load them at runtime.
The somewhat tricky part would be to ensure they get enhanced by the
system when they
Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of
Marc Prud'hommeaux
Sent: Monday, May 14, 2007 10:30 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Entity creation at Runtime
James-
It should be possible. The easiest way (and the most implementation-
agnostic) would be to simply
What level of testing do we need to do before we can add a new
version of
DB2 to the list of supported databases? Is just running our unit
test bucket
sufficient to add a new database to the list or do we need a more
formal
process?
That's a very good question, and one that I don't
[
https://issues.apache.org/jira/browse/OPENJPA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494583
]
Marc Prud'hommeaux commented on OPENJPA-51:
---
This patch caused 17 TCK tests to start failing, so it needs
[
https://issues.apache.org/jira/browse/OPENJPA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-194.
Resolution: Fixed
Committed patch. The binary artifact will be named
apache
if people deem it a worthwhile endeavor.
On May 6, 2007, at 2:27 PM, Marc Prud'hommeaux wrote:
Poking around the ActiveMQ pom.xml files, I notice that you can
have a different artifactId than the module name (i.e., directory)
you are in. I hadn't known you could do this.
Currently, our
and explain. Maybe there's an impact to changing the directory
name that I
missed though.
-Mike
On 5/6/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
Poking around the ActiveMQ pom.xml files, I notice that you can
have
a different artifactId than the module name (i.e., directory)
you
On May 7, 2007, at 9:35 AM, Patrick Linskey wrote:
Isn't that one too many 'openjpa' tokens? Couldn't it just be
http://svn.apache.org/repos/asf/openjpa/trunk/openjpa, instead of
http://svn.apache.org/repos/asf/openjpa/trunk/openjpa-all?
Yes, you're right.
Out of curiosity, is there an existing problem that this fixes, or
did you just notice through code inspection they we weren't passing
the ClassLoader in places where it appeared we should?
On May 7, 2007, at 2:38 PM, [EMAIL PROTECTED] wrote:
Author: pcl
Date: Mon May 7 14:38:20 2007
Poking around the ActiveMQ pom.xml files, I notice that you can have
a different artifactId than the module name (i.e., directory) you are
in. I hadn't known you could do this.
Currently, our artifacts name are:
trunk/pom.xml: openjpa
trunk/openjpa-all/pom.xml: openjpa-all
[
https://issues.apache.org/jira/browse/OPENJPA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux updated OPENJPA-194:
---
Attachment: OPENJPA-194.patch
Patch that changes artifact names so that the openjpa
David-
This part of the patch fixes what is clearly a bug with scanning
directories:
-scan(new FileMetaDataIterator(dir,
newMetaDataFilter()),
+//TODO should this call setStoreDirectory(file)
+scan(new
[
https://issues.apache.org/jira/browse/OPENJPA-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-148.
Resolution: Fixed
Applied (partial) patch.
Parsing exception while using
[
https://issues.apache.org/jira/browse/OPENJPA-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493735
]
Marc Prud'hommeaux commented on OPENJPA-148:
I understand the reason for that part now. I've applied
PROTECTED]
Craig Russell [EMAIL PROTECTED]
Kevin Sutter[EMAIL PROTECTED]
Abe White [EMAIL PROTECTED]
Marc Prud'hommeaux [EMAIL PROTECTED]
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Craig Russell
Henning-
Do you have the User class listed in a class tag in your
persistence.xml file? Can you show us your persistence.xml file?
On May 3, 2007, at 9:07 AM, Blume H., ITSC Bonn, RTB, DA wrote:
I tried to execute an unnamed query (using the 0.9.7 release) and got
the following
It might be that the JDK 1.5 beta you were using doesn't support XML
Schema (which is used by the JPA XML format)...
On May 2, 2007, at 10:42 AM, Philippe Alexis wrote:
On 5/2/07, Patrick Linskey [EMAIL PROTECTED] wrote:
Could you run ant with the '-e' option to get full stack traces?
I was able to delete it (I'm an administrator for Confluence; I
thought Patrick was as well).
To delete it, I went to the page, clicked Edit, then clicked the
link Remove Page.
On Apr 28, 2007, at 10:49 AM, Eddie O'Neil wrote:
I'm not a cwiki expert by any stretch -- one thing to do
Phill-
The maximum verbosity of logging is obtained by specifying the
openjpa.Log property to DefaultLevel=TRACE.
What is the full exception stack trace? We might be able to help
identify the problem. In any case OpenJPA should never be throwing an
NPE, so we should at least probably fix
.
Personally, I think both are valuable as they serve
different needs
for different development environments.
Eddie
On 4/24/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
On Apr 24, 2007, at 7:27 PM, Patrick Linskey wrote:
Hmm. I wonder if we're really using Maven
in some detail at:
http://incubator.apache.org/openjpa/docs/latest/manual/
manual.html#ref_guide_perfpack_eager
I assumed it makes one select per object. So in this case I
would get two selects (which I thought I saw).
Phill
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL
[
https://issues.apache.org/jira/browse/OPENJPA-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491423
]
Marc Prud'hommeaux commented on OPENJPA-61:
---
Note that you should make sure that you are really using
On Apr 24, 2007, at 3:07 PM, Marc Prud'hommeaux wrote:
Dain-
Can you send the embedded exception as well? That should tell us
who closed the query, and it might give us a hint why...
On Apr 24, 2007, at 3:03 PM, Dain Sundstrom wrote:
I have some code that runs outside of a transaction
On Apr 24, 2007, at 7:27 PM, Patrick Linskey wrote:
Hmm. I wonder if we're really using Maven repositories correctly.
Do we
need our dist to be in Maven at all?
We don't need to. It was just easy to set up that way.
I do think that we should have something that's easy to depend on that
Phill-
It sounds like a bug, but it would help to know what the exception
was :)
On Apr 23, 2007, at 7:02 AM, Phill Moran wrote:
I have been working with the validate tool and was getting an
exception on
classes that used @table(name=XXX, schema=YYY). If I took out
the schema
portion
I'm personally rather neutral on whether OpenJPA should be a TLP vs.
a sub-project. TLP seems like it allows us more flexibility and
independence, so by default I would lean towards being a TLP.
However, I do notice that the DB TLP already holds other similar
projects (Torque, OJB, and
Jacek-
On Apr 22, 2007, at 3:14 AM, Jacek Laskowski wrote:
I like it very much! Awesome! I need it for other projects, too.
Good work Marc.
Would it be possible to change OpenJPA with Apache OpenJPA in this
document? I couldn't find any reference of it in the whole document
other than
All-
The people at yWorks have graciously provided OpenJPA with an open-
source license to use their UML-generating plugin to javadoc. I've
run it on our docs, and you can see the output here:
http://people.apache.org/~mprudhom/openjpa-umldocs/
Do people think this would be sufficiently
[
https://issues.apache.org/jira/browse/OPENJPA-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux updated OPENJPA-61:
--
Attachment: OPENJPA-61.patch
The attached patch might work. It contains a new
I was messing around with our docbook processing today, and I found
the docbkx-maven-plugin plugin, which makes the docbook handling much
easier, and allows us to easily generate PDF from the documentation
(something I was having a hard time doing with our embedded ant tasks).
You can
+1
On Apr 20, 2007, at 12:41 PM, Michael Dick wrote:
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
Jay-
Nothing jumps out at me as being wrong with your mapping...
Note: I don't get any errors or exceptions, just no secondary
queries when I do a 'find('
If you call ComponentClass.getAttributes(), are you saying that no
SQL is executed? That would be surprising. Can you enable SQL
] close
About to do a 'getAttributes' call...
Finished the 'getAttributes' call...
Nothing happened at all in between the two System.out.println's -
is there a more verbose level of logging than TRACE?
Jay
Marc Prud'hommeaux wrote:
Jay-
Nothing jumps out at me as being wrong with your mapping
did not work.
So, I tried your suggestion of trying to add ClassAttrib entities
and persisting them individually - the ComponentClass completely
ignored them - I'll play with it some more.
Thanks for your time so far Marc.
I'll let you know what I come up with.
Jay
Marc Prud'hommeaux wrote
solely for the use of the
individual
or entity 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: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED
Michael-
On Apr 18, 2007, at 11:35 AM, Michael Dick wrote:
Thanks Marc,
How do I upload my key to http://incubator.apache.org/openjpa/
KEYS ? The
only documentation I've found indicates that I need to upload it,
but not
where the key needs to go.
As Eddie mentioned, you should be able
Michael-
On Apr 18, 2007, at 12:27 PM, Michael Dick wrote:
I'd rather not cut another release, but I think we do need to
resolve the
issue with the docbook jar. If we can live with the extra jar then
the vote
can proceed.
Personally, I think it is sufficiently ugly to release with the
Jonathan-
It looks like we indeed do ignore the columnNames field of the index.
This is a bug, and I've entered it at:
https://issues.apache.org/jira/browse/OPENJPA-223
I don't think there is a workaround, unless the index is unique, in
which case you can use the JPA standard
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.
I just went ahead and manually updated the license headers, just to
get this taken care of quickly.
On Apr 14, 2007, at 2:30 PM, Craig L Russell wrote:
Hi Eddie,
Removing Cliff from this discussion; sorry for the spam, Cliff, but
I recall you asking for it... ;-)
On Apr 14, 2007,
Craig-
I thought we were going to also release a maven download for the
jar file containing all the openjpa stuff and a pom that contains
the dependencies. This would enable folks using maven to simply put
the five lines of code naming the dependency into their pom and put
the incubating
. The pom.xml and the openjpa-
all.0.9.7-incubating.jar should be part of the vote and available
in the staging repository.
Craig
On Apr 13, 2007, at 12:09 PM, Marc Prud'hommeaux wrote:
Craig-
I thought we were going to also release a maven download for the
jar file containing all the openjpa
Docs seem OK and the examples all run. Looks good to me!
+1 for the release.
On Apr 12, 2007, at 3:20 PM, Michael Dick wrote:
OpenJPA People-
In accordance with the Incubating Releases guidelines at
http://incubator.apache.org/incubation/
Incubation_Policy.html#Releases ,
I've taken a
[
https://issues.apache.org/jira/browse/OPENJPA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux updated OPENJPA-5:
-
Attachment: OPENJPA-5.patch
The attached patch solves this problem by making all the JDBC
Michael-
I personally think that keeping -project- in the artifact zip name
is tolerable. I too had looked around (albeit briefly) for a solution
to this a while ago, and found none.
Once OpenJPA is out of incubation and we are deploying releases to
the Apache mirror system, we'll
wrote:
On 4/10/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
Glad you got it fixed. It's annoying that
javax.persistence.Persistence doesn't provide more of a clue as to
why it failed.
I wonder what else you'd like to see other than what's already printed
out? It tells exactly why it's failed
[
https://issues.apache.org/jira/browse/OPENJPA-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux reopened OPENJPA-208:
From Abe on mailing list: That breaks the single result optimization that was
added
[
https://issues.apache.org/jira/browse/OPENJPA-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-208.
Resolution: Fixed
Fix Version/s: (was: 0.9.7)
0.9.8
Matthieu-
Note that there shouldn't be any problem with running against a
directory versus a jar (I do it all the time), so there is probably
some environment issue.
Can you post your persistence.xml? If you write a little main()
method that just does:
classorg.apache.ode.store.jpa.DeploymentUnitDaoImpl/class
classorg.apache.ode.store.jpa.VersionTrackerDAOImpl/class
/persistence-unit
/persistence
Thanks,
Matthieu
On 4/9/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
Matthieu-
Note that there shouldn't be any problem with running against a
directory versus
Craig-
Yeah, we ran into this issue with the last release, where we kept re-
building release candidates that were all labeled 0.9.6-incubating
and were getting re-deployed to the official repository.
It would be easy enough to deploy to an alternate repository for
release approval (I
Phill-
It sounds like you have the tool set up to use the openjpa-all-0.9.6-
incubating.jar, but you haven't added any of the other required
dependencies to the environment's classpath. You should put
everything (except the derby jar) in the lib/ directory of the
OpenJPA distribution in
FWIW, my personal naming preference in descending order:
1. setTransactionIsolationLevel
2. setTransactionIsolation (user: Is this a boolean? Of course I
want my transactions to be isolated!)
3. setIsolation (user: What exactly is being 'isolated'? The
EntityManager or the cache or
[
https://issues.apache.org/jira/browse/OPENJPA-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-193.
Resolution: Fixed
Fix Version/s: (was: 0.9.8)
0.9.7
[
https://issues.apache.org/jira/browse/OPENJPA-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487348
]
Marc Prud'hommeaux commented on OPENJPA-208:
This seems to have slipped in in the fix for OPENJPA-168
[
https://issues.apache.org/jira/browse/OPENJPA-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487352
]
Marc Prud'hommeaux commented on OPENJPA-208:
The change to OPENJPA-168 seems to have been done to make
@JoinColumn(name = categoryTypeFK, referencedColumnName = id)
public CategoryType getType() {
return this.type;
}
Persistable is my base JPA persistable class housing the String id
for all
persistable classes
-Original Message-
From: Marc Prud'hommeaux [mailto
again
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of Marc
Prud'hommeaux
Sent: April 5, 2007 2:42 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Duplicate Query - where none exists
How is the category.categoryTypeFK column defined
George-
I'm not sure the exact problem (your model looks OK to me at first
glance), but FTR, I just tried a simple test with a query that
returns ob, ob.someOneToOne, and it returned the expected values
(in this case, a
org.apache.openjpa.persistence.models.company.basic.Customer and
Phill-
While I'm not sure the cause of the duplicate query error, I do
notice the original cause in the nested stack trace is:
Caused by: 4|true|0.0.0
org.apache.openjpa.persistence.ArgumentException: You cannot join on
column category.categoryTypeFK. It is not managed by a mapping that
Hiram-
I'm the guy that put the original ActiveMQ design together. If you
want
I'll tweak it some more for you guys. Perhaps change the color
scheme? Or
do you just want a better integrated banner/logo?
Personally, I think it would be fantastic if we had someone with
clear design
are
missing, the query should be considered sufficient.
Craig
On Apr 1, 2007, at 9:30 AM, Marc Prud'hommeaux wrote:
Seem fair enough to get rid of the description. I've opened
https://issues.apache.org/jira/browse/OPENJPA-196 describing the
issue.
+1 from me to remove the restriction
[
https://issues.apache.org/jira/browse/OPENJPA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-196.
Resolution: Fixed
Fix Version/s: 0.9.7
Ease the restrictions on forcing
Dain-
Also, I'm using 0.9.6 so is this a known problem?
I have a very hazy recollection of this being something that was
fixed recently, but a quick search through JIRA doesn't reveal anything.
Could you try it out against the latest 0.9.7-incubating-SNAPSHOT and
let us know if still
[
https://issues.apache.org/jira/browse/OPENJPA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on OPENJPA-196 started by Marc Prud'hommeaux.
Ease the restrictions on forcing a matche between the number of declared and
assigned positional parameters
Seem fair enough to get rid of the description. I've opened https://
issues.apache.org/jira/browse/OPENJPA-196 describing the issue.
+1 from me to remove the restriction that there be exactly as many
positional parameters declared as were assigned.
On Mar 31, 2007, at 7:32 PM, Dain
[
https://issues.apache.org/jira/browse/OPENJPA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux updated OPENJPA-196:
---
Attachment: OPENJPA-196.patch
This siple patch removed the restirction.
Ease
persistence.xml has jta-data-source), and I can't find in the
docs how to specify the DBDictionary without persistence.xml.
thanks,
-marina
Marc Prud'hommeaux wrote:
Marina-
The problem is that OpenJPA just ignores extra, unmapped columns.
Since we don't require that you map all
don't require that the
column actually be declared to be a primary key in order for OpenJPA
to work correctly (although I can't envision any reason why you
wouldn't want to make it a proper primary key).
thanks,
-marina
Marc Prud'hommeaux wrote:
Marina-
The problem is that OpenJPA just
This is briefly discussed at:
http://incubator.apache.org/openjpa/docs/latest/manual/
manual.html#jpa_overview_meta_gen
An example of how the annotation might look:
@javax.persistence.Entity
@kodo.persistence.DataStoreId(strategy =
javax.persistence.GenerationType.SEQUENCE, generator =
1 - 100 of 310 matches
Mail list logo
