Positional parameters (in)order within query and query.setParameter (in)order
-
Key: OPENJPA-188
URL: https://issues.apache.org/jira/browse/OPENJPA-188
Project: OpenJPA
MEMBER OF query fails on OpenJPA, but works fine with TopLink and Hibernate EM
--
Key: OPENJPA-187
URL: https://issues.apache.org/jira/browse/OPENJPA-187
Project: OpenJPA
Build failure of OpenJPA sources from trunk
---
Key: OPENJPA-186
URL: https://issues.apache.org/jira/browse/OPENJPA-186
Project: OpenJPA
Issue Type: Bug
Components: build / infrastructure
Hi -
I just downloaded the source through svn and failed at building openjpa. It
failed at a NoClassDefFoundError for SurefireBooter. What did I miss?
This is the output:
$ mvn package -Dtest=false
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] OpenJPA
[INFO] OpenJPA Uti
[
https://issues.apache.org/jira/browse/OPENJPA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-185:
-
Attachment: OpenJPA-185.patch.txt
> optional attribute is not overriden by xml descriptor
>
optional attribute is not overriden by xml descriptor
-
Key: OPENJPA-185
URL: https://issues.apache.org/jira/browse/OPENJPA-185
Project: OpenJPA
Issue Type: Bug
Affects Versions: 0.9.6,
use DB2 Diagnostic interface to report extended error diagnostics on SQL
Exception
--
Key: OPENJPA-184
URL: https://issues.apache.org/jira/browse/OPENJPA-184
Project: Ope
Fair enough. Cutting a candidate release would be a good way to provide the
"deadline". This would allow any in-flight Issues to be resolved before we
make this 0.9.7 final.
Kevin
On 3/27/07, Craig L Russell <[EMAIL PROTECTED]> wrote:
I hate to bring this up, but it takes more than a day or
I hate to bring this up, but it takes more than a day or two to cut a
release and have it approved. Take a look at the 0.9.6 release.
Granted, we're smarter than that now, but it still takes some time.
Let's say we built a candidate release right now. You want to give
the community a chance
Sounds great, especially since I'll be off skiing from Thursday to
Sunday or Monday.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
information of BE
Are you still seeing that same problem with the code that you attached?
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, I
Patrick,
I tend to agree. Just to give us a little bit of time to wrap up a couple
of fixes for pending Issues, how about if we set Thursday or Friday as the
deadline for the 0.9.7 release?
Kevin
On 3/27/07, Patrick Linskey <[EMAIL PROTECTED]> wrote:
I don't think that any of the pending 0.9.
Patrick Linskey <[EMAIL PROTECTED]> wrote: > my ID class has a book field, and
getters and setters for it
> to match Page's book field. i wonder about the last line
> where it says "java.lang.String". that seems odd.
Can you post your Book and Page classes and the Page's IdClass?
attached. i ke
> my ID class has a book field, and getters and setters for it
> to match Page's book field. i wonder about the last line
> where it says "java.lang.String". that seems odd.
Can you post your Book and Page classes and the Page's IdClass?
> so, regardless, even if that did work, correct me if i
hi patrick, thanks for your response ...
sorry i forgot to mention that the Book's name is it's ID. maybe that is not
realistic but that's the test case i was playing with. yes, i want to use the
Book's ID in the Page's composite ID, whatever that may be.
when i try calling out the Page's book
I don't think that any of the pending 0.9.7 issues are showstoppers; if
we want to create a 0.9.7 release ASAP, I'd be content with all of the
0.9.7 issues being moved out to 0.9.8.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
__
[
https://issues.apache.org/jira/browse/OPENJPA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abe White resolved OPENJPA-181.
---
Resolution: Fixed
Fix Version/s: 0.9.7
Fixed in SVN revision 523046. See test case added to
We'll be ready for the first RC in about 2 weeks so it's only going to be a
problem at that time. We could work that around by doing our own build of
OpenJPA and distributing it with ODE but that wouldn't be ideal. And OpenJPA
0.9.6 is aging now :-)
Matthieu
On 3/27/07, Marc Prud'hommeaux <[EMAI
Matthieu-
I don't think we have any date estimates yet. Craig was going to put
together the beginnings of a roadmap summary that should be useful
for this.
Looking at the JIRA roadmap for OpenJPA (http://issues.apache.org/
jira/browse/OPENJPA?
report=com.atlassian.jira.plugin.system.proje
It's actually a pretty shameless (albeit attributed) ripoff of http://
activemq.apache.org/. Something with the previous templates broke
recently (which itself was a shameless ripoff of http://
geronimo.apache.org/), so I figured it was a good opportunity to play
around with the styles.
I
+1 -- excellent work. Who knew!
Eddie
On 3/27/07, Patrick Linskey <[EMAIL PROTECTED]> wrote:
Dude when did Marc figure out how to make pretty HTML?
I love the new look. Thanks!
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
_
Dude when did Marc figure out how to make pretty HTML?
I love the new look. Thanks!
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
information of
> i want the Page's ID to be based on it's number, and ALSO the
> owning Book's name. i could make an ID class for Page, but
If you wanted to make the ID be based on it's number and the owning Book
itself (i.e., not the name), you could do this with OpenJPA, but not
with vanilla JPA. OpenJPA sup
say i have Book and Page classes. a Book has a name and can also have many
Pages. a Page has a number, and a reference to the owning Book.
i want the Page's ID to be based on it's number, and ALSO the owning Book's
name. i could make an ID class for Page, but the fields of the ID class need to
[
https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484474
]
Abe White commented on OPENJPA-168:
---
Something is wrong with my email system so instead of replying to the SVN
co
I found what I had missed. I am also using Spring and in the applicationContext
is the reference to Toplink. Removed that and replaced it with the open JPA and
bingo.
We should think about adding a small blurb on the site about configuring for
Spring since it is likely to be heavily used. I only f
26 matches
Mail list logo
