Hi, Werner and thanks! I think my boss can see the advantages. It's just that I've been struggling with this on and off for well over a week now and the client is getting restless (to him "on and off" doesn't count, understandably), so we need a quick solution. Had the application been in the development stage, I think we would have tried to figure the problem out. We've had timestamp mismatch errors before, but have always been able to figure them out, partly thanks to this list, but this one...
Once again, thanks for taking the time. Places like these are invaluable! Marit -----Ursprungligt meddelande----- Fr�n: Werner Guttmann [mailto:[EMAIL PROTECTED] Skickat: den 24 mars 2004 10:50 Till: [EMAIL PROTECTED] �mne: Re: [castor-dev] New timestamps created when reloading webpage - no update involved? Marit, You are always welcome to return ... ;-). It's a pity, though, that your boss cannot see the advantages of a tool/framework like Castor (and others in this arena) offers to a development team, despite it's shortcomings. Werner On Wed, 24 Mar 2004 10:17:00 +0100, Marit Hansson wrote: > >Hi, and thank you for your answer! > >OK, I've recieved new orders. My boss has come back from his holiday and he >wants me to rewrite it in JDBC, so I just wanted to say thanks for your time >and effort! > >Thanks, >Marit > > >-----Ursprungligt meddelande----- >Fran: Stein M. Hugubakken [mailto:[EMAIL PROTECTED] >Skickat: den 24 mars 2004 06:00 >Till: [EMAIL PROTECTED] >Amne: Re: [castor-dev] New timestamps created when reloading webpage - >no update involved? > > > >Marit Hansson wrote: >> Hello, >> >> I've searched extensively for a solution to my problem, but haven't found >> one, so now I have to ask. It's the old ObjectModifiedException/Timestamp >> mismatched thing, but with a twist... I think. >> > >What version of castor do you use? > >The latest version had a fix for a timestamp-problem I think, but not >sure if that has anything to do with your problem. > >> The node-object class extends a class that implements the TimeStampable >> interface... Well, no, actually it extends it!? Could that make a >> difference? I didn't write that code, so I don't know what considerations >> were made at the time. >> > >TimeStampable is an interface, but your class perhaps extends another >class implementing the TimeStampable-inteface? > >Perhaps you can post the relevant mapping and code? > >If we can't fix your problem at once then the best option is to create a >small test-case. > >Stein > >----------------------------------------------------------- >If you wish to unsubscribe from this mailing, send mail to >[EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > >----------------------------------------------------------- >If you wish to unsubscribe from this mailing, send mail to >[EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
