Hi Craig/Patrick,
Thanks for your guidance. I did try the options given by you
people. In fact, as Craig pointed out I had a identity property in the
bean, which I never used it. After I removed it, I got a different
exception. As Patrick suggested, I have moved the InnerProduct as a
to
So, going back to the original thread, one of the suggestions for
naming was:
http://svn.apache.org/repos/asf/openjpa/branches/r547073/
It sounds like you'd prefer that approach. What about Craig and Kevin?
I'm assuming that Srinivasa is ok with that approach, since he
suggested it in
Hi Arun,
Do you have any identity property in your beans? The missing identity
property might be disguised as wrong default for the other persistent
properties.
And what Patrick says...
Craig
On Jun 25, 2008, at 10:32 AM, Arun Nagarajan wrote:
Hi,
I have a set of java classes whi
Just my $0.02
I have no problems with 1. Posthumously creating a branch will happen from
time to time.
I think that 2 can cause problems. It's not clear to me from the branch name
where wlsmaintenance fits. Is it before or after 1.1.0? If I'm a new
developer should I try to merge my patch from tr
Personally, I don't see anything wrong with the approach taken so far.
It's definitely not the most ideal, but it seems to be a fair approach
given the situation (no branch was made at the time that WebLogic 10.0
shipped initially, and now there are changes that need to be made
against that
Hi,
I haven't written it up yet. I will put up a skeleton on the wiki later
today though. I'm expecting that (like the original instructions) we'll have
to add to it as we go through the process and find things that we missed.
-Mike
On Wed, Jun 25, 2008 at 3:57 PM, Patrick Linskey <[EMAIL PROTE
Hi,
Have you documented the process anywhere? I'd love to scan through the
new process and see what it looks like. It could also be useful to get
some input from other Apache folks to see if we're working more in
harmony with mvn than we had been.
-Patrick
On Jun 25, 2008, at 11:14 AM, M
I am definitely open to changing the name of the branch to conform to the
conventions. As far as the intent in creating the branch - it was to start-off
from the revision of OpenJPA that was used for a Weblogic release, and only
include vital non-intrusive changes that would help in maintenance
Sorry for the late response (hadn't been watching the alias). The intent of the
branch (original email) was to see if we could only have minimal set of vital
changes in the branch that could be used for Weblogic maintenance-packs.
- Srinivasa
-Original Message-
From: [EMAIL PROTECTED]
I agree with Craig and Kevin. Vendor tags in the Apache SVN repository
should be avoided.
I'm also leery of adding another branch to maintain. Patrick alluded to
potentially dangerous changes which went into the 1.0.x branch which caused
some concern for BEA. I'm guessing that rev 547073 is a poin
[
https://issues.apache.org/jira/browse/OPENJPA-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608170#action_12608170
]
Jeremy Bauer commented on OPENJPA-637:
--
Since Patrick agrees that we should do someth
[
https://issues.apache.org/jira/browse/OPENJPA-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Russell closed OPENJPA-499.
-
> Missing dependencies in openjpa-persistence and openjpa-persistence-jdbc
> ---
[
https://issues.apache.org/jira/browse/OPENJPA-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Russell resolved OPENJPA-499.
---
Resolution: Invalid
This is no longer an issue, since there are no sub-projects specifically
I agree with Kevin that we should eschew vendor tags in the OpenJPA
repository.
It should be sufficient to have maintenance folks know from which
branch a maintenance release was cut (r547073, openjpa/trunk/ is
really where you shipped from??? After creating a 1.1.0 tag?). And we
now have
Add cache store implementation option to data cache
---
Key: OPENJPA-643
URL: https://issues.apache.org/jira/browse/OPENJPA-643
Project: OpenJPA
Issue Type: Sub-task
Components: datac
Hi all,
I think I've made most of the pom.xml changes that will make the release
process a bit easier.
To that end I'd like to do a 1.0.3 release to test out the process for real.
I'll take a quick pass through the open JIRA issues and defer the ones that
don't seem critical. If there are any iss
Hi,
Can you post the source file and the full stack trace? Also, just in
case something is going wrong with inner class support, could you try
moving InnerProduct to be a top-level class?
-Patrick
On Jun 25, 2008, at 10:32 AM, Arun Nagarajan wrote:
Hi,
I have a set of java classes
Hi,
I have a set of java classes which has only setter and getter
methods (as they are generated using XML beans). At the entity level, I
have defined the access as 'PROPERTY'. But when I try to persist them, I
am getting the following error. Can you please let me know how to persist
j
Note that this is available within the JPA spec via the orm.xml's
persistence-unit-defaults section.
I'd rather see this configuration setting get promoted into JPA2's
persistence.xml instead of introducing a new setting of our own.
(In fact, I'd rather see cascade-persist at least be turne
Hi,
You should be able to work with static inner classes. I think that you
might need to use $ notation for the last separator, though:
com.ibm.retail.Product$InnerProduct
-Patrick
On Jun 25, 2008, at 9:09 AM, Arun Nagarajan wrote:
Hi,
I am using OpenJPA for persistence. The ja
Hi,
I am using OpenJPA for persistence. The java classes are generated
from XML Schema using XML beans technology. The java types to be persisted
are being generated as inner classes by XML Beans. After writing the
mapping information in the form of xml to map those persistable classes t
[
https://issues.apache.org/jira/browse/OPENJPA-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick resolved OPENJPA-642.
--
Resolution: Fixed
Fix Version/s: 1.2.0
Assignee: Michael Dick
Committed fix un
[
https://issues.apache.org/jira/browse/OPENJPA-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608083#action_12608083
]
Michael Dick commented on OPENJPA-642:
--
Thanks for the patch Fay!
> Sybase create fo
23 matches
Mail list logo
