[castor-dev] compiler errors during test case

All, I'm writing a testcase for the CTF. When I run the CTF, it tries to compile some code, but gets an error. What's the best way to find the compiler error messages? The errors "should have been provided" but weren't. Time: 2.944 There was 1 error: 1) testWithReferenceDocument(org.exolab.cast

[castor-dev] help on using castor.properties from within a jar file

Hi, When I run a test program, castor generates element tags for even those attributes in java class(that I marshal) that are null(like for instance . But the same when I try to do within a jar file, the attributes that are null are not represented as elements in the xml file generated by casto

Re: [castor-dev] update problem

You don't need the db.update(view). That's only for long transactions. --On Friday, January 17, 2003 8:22 PM +0100 fabrice jean <[EMAIL PROTECTED]> wrote: I've got a problem with an update : db.begin(); reqOql = db.getOQLQuery("SELECT p FROM MyApp.Value p"); results = reqOql.execute(); val

[castor-dev] update problem

I've got a problem with an update : db.begin(); reqOql = db.getOQLQuery("SELECT p FROM MyApp.Value p"); results = reqOql.execute(); value = (Value) results.next(); value.setNumber(45); db.update(value); db.commit(); ...I have the following exception org.exolab.castor.jdo.Duplica

Re: [castor-dev] Unmarshaller.unmarshal(Reader) thread-safe ?

From personal experience, I can say no. This is an issue we're still having. Somewhere down the call stack of the unmarshal method, there is a race condition. Jerome Michaudon wrote: Hi, before diving into casto sources, I'd like to know if so can tell me if the following method is thread-safe:

[castor-dev] Update relationship

Hello, I am having problems when update a relationship beetwen two Objects in long transactions. The updates do not have effects. The attach files contains mapping, classes and diagram class of the data model. I am autoStore=true What can is happening? Thanks for your help. Fabio example:

[castor-dev] Problem with SAPDB sequence

Hello, I've been working with castor 0.9.4.1 so far and my sequences were working. Now that I've switched to castor 0.9.4.2 i cannnot store objects to the database anymore. Here's a part of my mapping.xml: Forum object ... When I remove the sequence from the mappin

Re: [castor-dev] SourceGen - ClassCast Exception - builder.FieldInfo bug?

Hi Alan, I can confirm it is working fine from the CVS but it may not have been updated yet on the snapshot. Arnaud > -Original Message- > From: Alan Holland [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 17, 2003 6:38 PM > To: [EMAIL PROTECTED] > Subject: Re: [castor-dev] SourceGen

[castor-dev] Timestamp mismatched exception when using long transaction

Hello: I am using Castor 0.9.4.1 on RedHat Linux 8.0 running Apache 2.0.43, Tomcat 4.0.6, and MySql 3.23.53a. Here is a simple test case: package test; import java.io.*; import java.net.*; import javax.servlet.*; import javax.servlet.http.*; import org.exolab.castor.jdo.*; import persistent.*;

Re: [castor-dev] SourceGen - ClassCast Exception - builder.FieldInfo bug?

Arnaud, I downloaed and built the latest snapshot of Castor but I'm afraid I still had the same ClassCastException in FieldInfo using SourceGen on (http://4c.ucc.ie/~aholland/scheddl.xsd). Alan > -Original Message- > From: Arnaud Blandin [mailto:[EMAIL PROTECTED]] > Sent: 17 January 2003

Re: [castor-dev] SourceGen - ClassCast Exception - builder.FieldInfo bug?

Hi Alan, This bug should have been fixed in the CVS. Let us know if it works ok for you. Arnaud > -Original Message- > From: Alan Holland [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 17, 2003 4:15 PM > To: [EMAIL PROTECTED] > Subject: [castor-dev] SourceGen - ClassCast Exception -