[ http://issues.apache.org/jira/browse/OJB-55?page=comments#action_12315954 
] 

Armin Waibel commented on OJB-55:
---------------------------------

Did you get any side-effects when apply your patch? If we change method  
getForeignKeyFieldDescriptors()  as you suggest OJB will return FieldDescriptor 
from different ClassDescriptor, these ClassDescriptor can represent different 
DB tables.

Could you describe in detailed how to set up a test to reproduce your problem. 
This will be really helpful.

> Getting foreignkeyField's FieldDescriptor is failing if the foreignkey field 
> is defined in the base class
> ---------------------------------------------------------------------------------------------------------
>
>          Key: OJB-55
>          URL: http://issues.apache.org/jira/browse/OJB-55
>      Project: OJB
>         Type: Bug
>   Components: PB-API
>     Versions: 1.0.3
>  Environment: Windows 2000, Jboss application server
>     Reporter: Rajadurai
>  Attachments: ObjectReferenceDescriptor.java
>
> Hi,
>    we are using ojb in one of our application.  
> We got  the exception when we try to find the entity whos parent's foreign 
> key field is null.
> that is out critier will be "attr IS NULL"
> Basically getForeignKeyFieldDescriptors() method in 
> ObjectReferenceDescriptor.java is trying to find the 
> foreignkeyfieldDescritpros in the current class only, thats why its giving 
> exception.
> If it is not available in the current class then it has to find from base 
> class.
>  I have changed ObjectReferenceDescriptor.java -> 
> getForeignKeyFieldDescriptors() method. 
> i m attaching that file also.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to