slices query.getSingleResult is broken
--
Key: OPENJPA-787
URL: https://issues.apache.org/jira/browse/OPENJPA-787
Project: OpenJPA
Issue Type: Bug
Components: query
Affects Versions: 2.0.0
It sucks that it's more work, but definitely better in the long run.
I don't think this is something I can volunteer for, but I will give you
lots of moral support for taking this on :) :)
David Jencks wrote:
IIUC the discussion on legal-discuss is not going too well for inclusion
of this IB
IIUC the discussion on legal-discuss is not going too well for
inclusion of this IBM jar in apache svn.
If the idea behind this jar is the work-in-new-tx "work manager" I'd
suggest one way to proceed is to have someone who has not ever seen
the IBM code such as perhaps myself write an inter
Patrick,
Nice to hear from you... ;-)
I'm coming to the same conclusion about the Handler vs Strategy argument.
It seems that we have overloaded the Strategy term to mean either a Strategy
or a Handler. This not only makes the documentation confusing, but also the
code.
Here's what I have found
slices documentation needs to mention requirement for global username/password
--
Key: OPENJPA-786
URL: https://issues.apache.org/jira/browse/OPENJPA-786
Project: OpenJPA
On Tue, Nov 25, 2008 at 5:54 PM, Kevin Sutter <[EMAIL PROTECTED]> wrote:
> Hi,
> With the recent posting of Public Review Draft of the JPA 2.0 specification
> [1], we need to publicly kick off the development of JPA 2.0 within the
> OpenJPA development team. There have been a few other related pos
>> Person p1 = em2.getReference( p1Id );
>> Address a1 = p1.getAddress();
So.. Thank you agreeing with what we thought that this won't work. But,
is there anyway I can get this to work :) :) :) Like I keep saying, I'm
cool with reviewing openjpa source and submitting patches, any ideas on
ho
> Person p1 = em2.getReference( p1Id );
> Address a1 = p1.getAddress();
> logger.debug( "a1: " + a1 );
If DistributionPolicy.distribute(p1) = DistributionPolicy.distribute(a1),
then
assertNotNull(a1);
else
assertNull(a1);
SlicePersistence.getSlice(x) for any managed instance x return the s
[
https://issues.apache.org/jira/browse/OPENJPA-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick reassigned OPENJPA-780:
Assignee: Pinaki Poddar (was: Michael Dick)
Pinaki is a better candidate to determine whe
[
https://issues.apache.org/jira/browse/OPENJPA-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650718#action_12650718
]
Fay Wang commented on OPENJPA-782:
--
Another piece of information: in Spec 2.6: "The embed
Below is the precise usecase I'm trying to get to work reliably. And
trying to understand "collocation constraint". So you're saying that I
can always distribute objects into different slices if I call persist on
each one.
The question I have is what would I expect when I try doing
p1.getAd
SQLException from findObject
Key: OPENJPA-785
URL: https://issues.apache.org/jira/browse/OPENJPA-785
Project: OpenJPA
Issue Type: Bug
Components: jdbc
Affects Versions: 1.2.0, 1.3.0
Environ
- What is the difference between ClassMetadata and MappingInfo? It
seems
that the latter is a temporary holder of schema objects until the
final
ClassMetadata is assembled. Is that correct?
Yes. OpenJPA parses from various different formats into MappingInfo
data structures, and then the Cl
[
https://issues.apache.org/jira/browse/OPENJPA-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fernando updated OPENJPA-784:
-
Attachment: poms.diff
just a diff to cleanup pom files.
> more pom.xml dependency cleanup
> ---
Hi,
I appreciate your thoughtful observations and comments. I hope that your
project will benefit from Slice and design/implementation of Slice, in turn,
will improve from practical use cases and independent views.
> hmm. So maybe I was too quick to say that the collocation constraint is
> t
Hi,
(I'm offline at the moment, so my research abilities are diminished.)
Yes, I think that that's a bit of tragic naming. Last time I looked at
the *Handler / @Strategy dichotomy, my conclusion was that it seemed
like the annotation should be renamed @Handler. But I've never really
chased
more pom.xml dependency cleanup
---
Key: OPENJPA-784
URL: https://issues.apache.org/jira/browse/OPENJPA-784
Project: OpenJPA
Issue Type: Improvement
Components: build / infrastructure
Affects Version
Hi,
With the recent posting of Public Review Draft of the JPA 2.0 specification
[1], we need to publicly kick off the development of JPA 2.0 within the
OpenJPA development team. There have been a few other related postings to
the dev mailing list [2]. This shows the team's interest in pursuing th
> it looks like an "operation" just maps to one single call of the broker, no
matter how many calls are done within one transaction.
> ust like when you persist one object, but the system actually persists
> many objects as a side effect..
Correct.
>> Not sure if this forum is the correct place
[
https://issues.apache.org/jira/browse/OPENJPA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fernando updated OPENJPA-779:
-
Attachment: fix_svn_ignore.sh
this is a small script to apply an updated svn:ignore property to project
[
https://issues.apache.org/jira/browse/OPENJPA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fernando updated OPENJPA-779:
-
Attachment: fix_svn_ignore.sh
oops, i didn't give license on the last upload, but I meant to.. so
re-up
[
https://issues.apache.org/jira/browse/OPENJPA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650637#action_12650637
]
Fernando commented on OPENJPA-779:
--
well, we all agree that maven is the authoritative bu
[
https://issues.apache.org/jira/browse/OPENJPA-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick resolved OPENJPA-783.
--
Resolution: Fixed
Fix Version/s: 2.0.0
1.3.0
Thanks again for the pa
[
https://issues.apache.org/jira/browse/OPENJPA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650614#action_12650614
]
Kevin Sutter commented on OPENJPA-779:
--
I agree with Mike that we shouldn't attempt t
[
https://issues.apache.org/jira/browse/OPENJPA-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick reassigned OPENJPA-783:
Assignee: Michael Dick
> openjpa-lib/pom.xml has extraneous code
> ---
[
https://issues.apache.org/jira/browse/OPENJPA-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick resolved OPENJPA-781.
--
Resolution: Fixed
Fix Version/s: 2.0.0
1.3.0
Thanks for the patch. T
[
https://issues.apache.org/jira/browse/OPENJPA-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick reassigned OPENJPA-781:
Assignee: Michael Dick
> openjpa-jdbc depends on postgres driver, should be "provided"
> -
[
https://issues.apache.org/jira/browse/OPENJPA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650601#action_12650601
]
Michael Dick commented on OPENJPA-779:
--
As developers can't we all just agree to use
[
https://issues.apache.org/jira/browse/OPENJPA-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650522#action_12650522
]
Milosz Tylenda commented on OPENJPA-773:
The [1] link points to the Early Draft. T
29 matches
Mail list logo
