You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2014/07/22 12:32:39 UTC

[jira] [Resolved] (OLINGO-373) should support reading proxy code' META-INF files in eclipse ADT app' way

     [ https://issues.apache.org/jira/browse/OLINGO-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Chicchiriccò resolved OLINGO-373.
-------------------------------------------

    Resolution: Incomplete

In accordance with [~challenh], this issue is going to be fixed in the master branch by changing the way in which the {{pojogen-maven-plugin}} generates information about complex types, enum types and terms.

Basically, no more files that need to be included under {{META-INF/}} but instead some java Map instances directly included in the {{Service}} class.

> should support reading proxy code' META-INF files in eclipse ADT app' way
> -------------------------------------------------------------------------
>
>                 Key: OLINGO-373
>                 URL: https://issues.apache.org/jira/browse/OLINGO-373
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-client
>    Affects Versions: V4 0.2.0
>         Environment: app using olingo proxy codes in eclipse ADT (not maven)
>            Reporter: Challen
>            Assignee: Challen
>             Fix For: V4 0.2.0
>
>
> currently CoreUtils.java always try to read META-INF/org.apache.olingo.ext.proxy.complex,enum,term from apk's root folder:
> ------------
>   private static Class<?> getEnumTypeRef(final ODataValue value) {
>     return getTypeRef(value, "META-INF/" + Constants.PROXY_ENUM_CLASS_LIST, EnumType.class);
>   }
>   private static Class<?> getComplexTypeRef(final ODataValue value) {
>     return getTypeRef(value, "META-INF/" + Constants.PROXY_COMPLEX_CLASS_LIST, ComplexType.class);
>   }
> ------------
> maven can easily build those files to META-INF/ folder, but if user wants to use eclipse ADT, not maven, they can't do that. the app will be broken by exception at runtime.
> the temp fix is : when reading from META-INF/ folder fails, then try reading those 3 files from 'asserts/META-INF/' folder, where eclipse ADT is able to place those 3 files.



--
This message was sent by Atlassian JIRA
(v6.2#6252)