[ 
https://issues.apache.org/jira/browse/OLINGO-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588870#comment-15588870
 ] 

Alexandre Desjardins commented on OLINGO-1010:
----------------------------------------------

Hi [~grande],

I am currently going through your tutorial using Hibernate for JPA provider. 
There seems to be problems occurring when a "@Column" or "@joinColumn" name 
does not equal the name of the java property. For example, in the class 
BusinessPartnerRole, there is a joinColumn with the name BusinessPartnerID. 
This seems to give referential constraints errors. I haven't delved too deep in 
your code, but it seems that in the method "determienReferentialConstraints" it 
is calling getPropertyByDBField however this method is trying to compare the 
dbFieldName "BusinessPartnerID" to the property.getDBFieldName() 
"businessPartnerID" which never works since one is capitalized and the other 
isn't.

Another example is with the property "roleCategory" annotated with column name 
"BusinessPartnerRole". If I leave it as is, the queries generated are using 
"roleCategory" as a column name instead of businessPartnerRole. 





> OData V4 JPA Processor
> ----------------------
>
>                 Key: OLINGO-1010
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1010
>             Project: Olingo
>          Issue Type: New Feature
>          Components: odata4-server
>    Affects Versions: (Java) V4 4.0.0, (Java) V4 4.2.0, (Java) V4 4.3.0
>            Reporter: Oliver Grande
>         Attachments: OlingoV4JPA-apache.zip, 
> odata-jpa-annotation-0.0.1-SNAPSHOT.jar, 
> odata-jpa-metadata-0.0.1-SNAPSHOT.jar, odata-jpa-processor-0.0.1-SNAPSHOT.jar
>
>
> Hello,
> I have created a first version of a JPA Processor for Olingo V4. The 
> Processor is, as of now able to generate metadata document and perform GET 
> requests. I like to contribute with this to Olingo.
> Regards,
> Oliver 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to