Welcome Felipe! Starting with contribution is quite simple. If you find a new bug then you can create a Jira issue for the Olingo project here:
https://issues.apache.org/jira/browse/OLINGO If you want to contribute a fix for this bug then you can attach a patch to the issue. One of the committers will pick it up and commit to the source repository if it is accepted. Is this applicable to you? Greetings, Stephan PS.: Just as hint, Apache mailing lists do not accept attachments. The images within you mail are not shown. At least not to me. From: <Taiarol>, Felipe <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Dienstag, 13. Mai 2014 14:51 To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Contributing to Olingo Hi All, I work in the SAP Cloud Custom Development and we will probably start using Olingo in future projects. I would like to start contributing to the Olingo project and eventually become a committer. I cloned the git repository https://git-wip-us.apache.org/repos/asf/olingo-odata2 and started playing around with Olingo. First thing I noticed is that there is bug when you try to create an OData service for a JPA entity which has an OneToMany relationship. This is the error you get: [cid:[email protected]] I found out this happens because jpaAttribute.getJavaType() return java.util.List which is not an entity. I guess the list generic type should be passed as parameter instead ? org.apache.olingo.odata2.jpa.processor.core.model.JPAEdmProperty [cid:[email protected]] This was working in version 1.0.0 so I don’t know if you are already aware of that or if this is happening because of some code restructuring or something but I think it doesn’t hurt to point that out. :) The second thing I noticed is that when the OData entities are created from the JPA entities Olingo just adds an “s” at the end of the name. I modified the class org.apache.olingo.odata2.jpa.processor.core.access.model.JPAEdmNameBuilder using the this library https://github.com/atteo/evo-inflector and now the entities are created using the correct plural name. [cid:[email protected]][cid:[email protected]] I never particpated in an open source project before so I am not really sure how it works. Is this a desirable change ? Can I commit it ? Best regards, Felipe
