db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Armin Waibel <arm...@apache.org>
Subject Re: getObjectByIdentity fails after cvs update
Date Sun, 29 Feb 2004 19:14:40 GMT
Hi again,

Michael Mogley wrote:

> Hi Armin,
> 
> I don't do anything exotic.  The scenario is this:
> 
> 1) app.ear is deployed.
> 2) I go to the app.war home-page.  No problems.
> 3) I go to the entity-listing page that retrieves a collection of OJB-mapped
> entities from the db.  No problems.
> 4) I click on a specific entity to go to its detail page (which uses the
> getObjectByIdentity - which worked before the cvs-update).  Problems.
> 
> It is hard to see how the descriptor repository can be null if step 3
> succeeded.  One thing I should mention is I'm retrieving proxies for the
> collection.  However, as I said, this worked before.
> 

indeed this sounds strange!
When did you the last CVS update that works?
Proxy could be a problem, but as long as all is done in the same JVM 
this should work.
Did you get any other error/warn log messages?


regards,
Armin

> Any other ideas?
> 
> Michael
> 
> ----- Original Message ----- 
> From: "Armin Waibel" <arminw@apache.org>
> To: "OJB Developers List" <ojb-dev@db.apache.org>
> Sent: Sunday, February 29, 2004 2:35 AM
> Subject: Re: getObjectByIdentity fails after cvs update
> 
> 
> 
>>Hi Michael,
>>
>>current CVS head pass all PB-Tests without problems. Seems that in your
>>case, the DescriptorRepository was not set for used PB instance or was
>>set to 'null'. Do you do "any exotic things" in your application,
>>setting of DescriptorRepository for PB instance, using own PB
>>implementation, ...?
>>
>>regards,
>>Armin
>>
>>Michael Mogley wrote:
>>
>>
>>>Hi Dev Guys,
>>>
>>>I just cvs-updated the last few weeks worth of changes and now get this
> 
> error from my web-app when looking up an object by identity:
> 
>>>java.lang.NullPointerException
>>>        at
> 
> org.apache.ojb.broker.core.PersistenceBrokerImpl.getClassDescriptor(Persiste
> nceBrokerImpl.java:1602)
> 
>>>        at
> 
> org.apache.ojb.broker.cache.CacheDistributor.searchInClassDescriptor(CacheDi
> stributor.java:276)
> 
>>>        at
> 
> org.apache.ojb.broker.cache.CacheDistributor.getCache(CacheDistributor.java:
> 198)
> 
>>>        at
> 
> org.apache.ojb.broker.cache.AbstractMetaCache.lookup(AbstractMetaCache.java:
> 117)
> 
>>>        at
> 
> org.apache.ojb.broker.cache.InternalCache.lookup(InternalCache.java:80)
> 
>>>        at
> 
> org.apache.ojb.broker.core.PersistenceBrokerImpl.doGetObjectByIdentity(Persi
> stenceBrokerImpl.java:1229)
> 
>>>        at
> 
> org.apache.ojb.broker.core.PersistenceBrokerImpl.getObjectByIdentity(Persist
> enceBrokerImpl.java:1212)
> 
>>>        at
> 
> org.apache.ojb.broker.core.DelegatingPersistenceBroker.getObjectByIdentity(D
> elegatingPersistenceBroker.java:296)
> 
>>>        at
> 
> org.apache.ojb.broker.core.DelegatingPersistenceBroker.getObjectByIdentity(D
> elegatingPersistenceBroker.java:296)
> 
>>>I have tried with various cache implementations including
> 
> ObjectCacheEmptyImpl.
> 
>>>Could this be due to some recent OJB code changes?  Do I need to add
> 
> something new to my class descriptors?
> 
>>>Grateful for any help.
>>>
>>>Michael
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>>For additional commands, e-mail: ojb-dev-help@db.apache.org
>>
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Mime
View raw message