Oliver Hutchison wrote:
>
> Todd, I have also found this problem and have raised it as a bug with the castor
>developers, see:
> http://bugzilla.exolab.org/show_bug.cgi?id=834
>
> I had to argue hard to get this accepted as a bug, but there's been no movement with
>regards to a fix and I hav
On 2/12/02 9:06 PM, [EMAIL PROTECTED] wrote:
> Could you try to have an attribute
> for your collection fields and see if it work for you.
Sure, though I don't understand why it should make a difference. Isn't
"setFoo" the default set-method for a field named "foo" ??
Anyway... using:
C
Todd, I have also found this problem and have raised it as a bug with the castor
developers, see:
http://bugzilla.exolab.org/show_bug.cgi?id=834
I had to argue hard to get this accepted as a bug, but there's been no movement with
regards to a fix and I haven't had the time to produce one myself
Martin and Bruce,
thanks for your answers, everything is ok now.
Cheers,
Ben
Martin, Margaret wrote:
> Ben,
> In a 1:M, you have to tell Castor what field to use for the mapping if you
> want to use something other than the identity. In your case, I believe if
> you change the mapping for subsc
Could you try to have an attribute
for your collection fields and see if it work for you.
Thomas
-Original Message-
>From: Todd V. Jonker [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, February 12, 2002 5:18 PM
>To: [EMAIL PROTECTED]
>Subject: [castor-dev] 0.9.3.9 collection incompatibi
Hello,
I'm attempting to migrate from Castor 0.9.3 to 0.9.3.9 and have discovered
some strange problems. I'm using Castor JDO on top of PostreSQL.
My problem is that a mapping file that worked fine now fails to work
properly with regards to the collections used for many-to-many mappings.
I get
Hello fellow plight attendants,
Since this happens intermittently among multiple users, and the library that calls JDO
is a singleton, I'm leaning towards thread issues for this one. The method that
returns the singleton is:
public synchronized static ActionLib getInstance() {...}
I was doing
I have two XSDs fruit.xsd (tns=http://www.xyz.com/fruit) and
apple.xsd(tns=http://www.xyz.com/fruit) as below
AppleType defined in apple.xsd references complexType "nutritionInfoType" and
simpleType enumeration "stateType" defined in fruit.xsd
Similarly FruitType defined in fruit.xsd also refer
Thanks David,
that fixed it...
-Original Message-
From: David Jencks [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 12, 2002 1:32 PM
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] interbase "unitialized object" problem
As I recall from the distant past when I was struggling with i
This one time, at band camp, Gustavo Pistoia said:
GP>
GP>Bruce:
GP> 1) I generate my classes from a xsd file. Just data objects. Then I set
GP>the relations with the fields of my database.. But all this objects obly
GP>contains attributes, no logic. I want to know where to put the logic. I
GP>gu
Bruce:
1) I generate my classes from a xsd file. Just data objects. Then I set
the relations with the fields of my database.. But all this objects obly
contains attributes, no logic. I want to know where to put the logic. I
guess I need lot of extra classes.
2) I found a bug in the source gener
Hi Glenn,
Thank you for your persistence.
I would really rather to have a test case for each patch I commit.
If patch writer don't do a test, I would do it myself, even if it means
the latency takes very long. A test case would ensure the quality
of a patch. But even more important, ensure other
As I recall from the distant past when I was struggling with interclient
this is usually caused by using the Borland distro compiled in jdk 1.2 with
a 1.3 vm. Recompiling the source for the jdk you are using fixes this.
There are also a couple of precompiled versions at the firebird download
are
Remi,
The simplest solution is to add get/setBVector methods to A, then reference
these as the get-method and set-method in the mapping file. If you are going
to be generating a lot of code, you can extend CollectionInfo to
automatically do this.
Hope this helps...
Margaret
-Original Message
Hi all, here's the Exception:
org.exolab.castor.jdo.ObjectNotPersistentException: The object of type
x.y.z.ServiceInfo is not persistent -- it was not queried or created within this
transaction
at
org.exolab.castor.persist.TransactionContext.writeLock(TransactionContext.java:1177)
15 matches
Mail list logo