additional info

when using an odmg-query instead of a pb-Query (in the code that fails to execute), I get the following error: What is the reason for this? I have the db openend read-write, Transaction is is also open, Any clue? -Gunnar [org.apache.ojb.odmg.TransactionImpl] ERROR: Locking obj [EMAIL PROTECTED

identical code fails one place, works in an other

Hello, I got a serious problem with a strange class cast exception: Collection ress=tipp.getReservierungen(); Iterator j=ress.iterator(); causes a ClassCassException in the second line, but only in one program, an other one works with the same repository (snippet): Complete stack

Sequence Manager for HSQLDB + JBOSS

Fellow OJBers, I have an application running on JBoss 3.0.8, using the latest version of OJB (from CVS). I'm using the provided HSQLDB version that comes with JBoss. I have a couple of questions on the setup: 1). Which OJB internal tables do I need? When are this tables generated. I see them in

Re: timeout attribute in ObjectCacheDefaultImpl

Hi Armin, Thank you very much for your reply. I forgot to ask you one thing: can I set the ObjectCacheDefaultImpl timeout to infinite (object cache never timeouts)? For example, timeout = -1? Thanks, Jair Jr > Hi, > > Jair da Silva Ferreira Júnior wrote: > > > Hi, > > I am using

Re: cache implementation change in rc5?

Hi Armin, > Hi Jair jr, > > Jair da Silva Ferreira Júnior wrote: > > Hi Armin, > > Thank you very much for your fast reply. > > > > > >>it's a(/my) bug in ObjectCacheDefaultImpl (rc5) causing this strange > >>behaviour. I will check in a fixed version tomorrow. > > > > > > Ok. How can I g

Issue: PBLifeCycleListener.afterLookup() and batch load in RC5

Just a note: In RC5 in case of batch load event PBLifeCycleListener.afterLookup () may be called when some references in target object is not yet initialized. Thanks, Andy

Re: timeout attribute in ObjectCacheDefaultImpl

Hi, Jair da Silva Ferreira Júnior wrote: Hi, I am using ojb1.0_rc5, ODMG api with OJB queries, mysql4 (innodb tables) in Linux Red Hat 7.3 (kernel 2.4.20-20.7). I am using ObjectCacheDefaultImpl in my application as it's read-intensive. I have some questions about the behavior of the

timeout attribute in ObjectCacheDefaultImpl

Hi, I am using ojb1.0_rc5, ODMG api with OJB queries, mysql4 (innodb tables) in Linux Red Hat 7.3 (kernel 2.4.20-20.7). I am using ObjectCacheDefaultImpl in my application as it's read-intensive. I have some questions about the behavior of the timeout attribute in ObjectCacheDefaultImpl

Re: objects in cache after transaction abort

Hi, > Is this fix going to be available in the final 1.0 version coming out in > 1 or 2 days? yes, a fix or workaround regards, Armin Jair da Silva Ferreira Júnior wrote: Hi Armin, Hi Jair jr, Jair da Silva Ferreira Júnior wrote: Hi Armin, Thank you for your fast reply. hmm, thi

Re: objects in cache after transaction abort

Hi Armin, > Hi Jair jr, > > Jair da Silva Ferreira Júnior wrote: > > Hi Armin, > > > > Thank you for your fast reply. > > > > > >>hmm, this should not happend. Do you use checkpoint() or flush() > >>in your code? > >>This only could happens when the object was already in DB. Only the > >>Pers

Re: Desperately need help with my repository

Luis Cruz wrote: Is it possible for you to post the snip of code that does the query? My guess is that you're doing something like this: Here's one of my DAO methods in which the Exception is thrown: public Collection findAllCategories() throws DataAccessException { PersistenceBroker broke

Re: XDoclet OJB module update

On Fri, 2 Jan 2004, Brian Sam-Bodden wrote: > Thomas, > Is there any place to find information about building the XDoclet > OJB module? You'll have to grab OJB from CVS, then you do ant docs in the OJB root directory (which will generate the documentation). You'll get the xdoclet module d

Re: OrderBy of ref class having same property name = problem

hi terry, ojb always adds orderby or grouppby columns to the select columns if they are not already there. the only thing i did in my patch was adding an alias ojb_col_x to the automatically added columns. the two columns in your sample are treatd as two *different* columns because the lookup