[jira] [Updated] (OLINGO-489) JPAEDMMappingModel should also support the exclusion of relationships or hide relationships to excluded entities
[ https://issues.apache.org/jira/browse/OLINGO-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-489: --- Assignee: (was: Chandan V.A) > JPAEDMMappingModel should also support the exclusion of relationships or hide > relationships to excluded entities > > > Key: OLINGO-489 > URL: https://issues.apache.org/jira/browse/OLINGO-489 > Project: Olingo > Issue Type: New Feature > Components: odata2-jpa >Affects Versions: V2 2.0.2 >Reporter: Björn Wagner > > The XML configuration of the JPAEDMMappingModel should also support the > exclusion of relationships or automatically hide relationships to excluded > entities. According to the schema, its only possible at the moment to exclude > attributes or complete entities. The problem is that in case an entity is > excluded, the relation from other entities to the excluded entity still shows > up in the oData meta model. > Some oData Client libraries fail to validate the data model for this reason. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-491) Query formed has all attributes of JPA entity instead of the selected attributes provided by $select system query option
[ https://issues.apache.org/jira/browse/OLINGO-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-491: --- Assignee: (was: Chandan V.A) > Query formed has all attributes of JPA entity instead of the selected > attributes provided by $select system query option > > > Key: OLINGO-491 > URL: https://issues.apache.org/jira/browse/OLINGO-491 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.1, V2 2.0.2 >Reporter: dhaval gupta > > Query formed has all attributes of JPA entity instead of the selected > attributes provided by $select system query option. > For ex : > Suppose we have entity Issue in which there are 20 attributes. Now I select 2 > attributes out of those 20 by $select=assetCode, IdIsin but the query that is > executed by JPA is having all the 20 attributes in the query . > Thanks > Dhaval -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[ https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-527: --- Assignee: (was: Chandan V.A) > Is there any possible ay to reduce build response time of JPA query > > > Key: OLINGO-527 > URL: https://issues.apache.org/jira/browse/OLINGO-527 > Project: Olingo > Issue Type: Question > Components: odata2-core, odata2-jpa >Reporter: Karuna Joshi > > We have a very large data base and we are exposing the data using olingo > restful web service. when I compare, time taken to execute the same query via > jdbc connection and time taken by olingo, there is a significant difference. > Time taken by Olingo is very large. > Time taken to process JPA query + Time taken to build response is the total > time taken by olingo. > We try to tune the JPA queries using Query hints, but still build response > time is also very large. > I have a question : > Is there any way we can reduce the time taken to build the response ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-490) Olingo v2 JPA does not work with hibernate envers.
[ https://issues.apache.org/jira/browse/OLINGO-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-490: --- Assignee: (was: Chandan V.A) > Olingo v2 JPA does not work with hibernate envers. > -- > > Key: OLINGO-490 > URL: https://issues.apache.org/jira/browse/OLINGO-490 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.0 >Reporter: Fadhly > > Class cast exception when using JPA/Hibernate with Hibernate envers @Audited > annotation. The current source did not make a class instance check hence the > error below; > org.hibernate.jpa.internal.metamodel.MapMember cannot be cast to > java.lang.reflect.AnnotatedElement -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-181) Medialink support in JPA
[ https://issues.apache.org/jira/browse/OLINGO-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-181: --- Assignee: (was: Chandan V.A) > Medialink support in JPA > > > Key: OLINGO-181 > URL: https://issues.apache.org/jira/browse/OLINGO-181 > Project: Olingo > Issue Type: New Feature > Components: odata2-jpa >Affects Versions: V2 1.2.0, V2 2.0.2 >Reporter: Ashutosh Singh > > There is no support for medialink in JPA. How can we achieve it? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-188) Added Supported Features sections in OData JPA Documentation
[ https://issues.apache.org/jira/browse/OLINGO-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A resolved OLINGO-188. Resolution: Won't Fix > Added Supported Features sections in OData JPA Documentation > > > Key: OLINGO-188 > URL: https://issues.apache.org/jira/browse/OLINGO-188 > Project: Olingo > Issue Type: Improvement > Components: odata2-documentation >Affects Versions: V2 1.2.0 >Reporter: Chandan V.A >Assignee: Chandan V.A > > Enhance the OData 2 JPA Documentation page to include supported features > sections. > Regards > Chandan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-768) POC: odata-jpa-core Exception Handling
[ https://issues.apache.org/jira/browse/OLINGO-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-768: --- Assignee: (was: Chandan V.A) > POC: odata-jpa-core Exception Handling > -- > > Key: OLINGO-768 > URL: https://issues.apache.org/jira/browse/OLINGO-768 > Project: Olingo > Issue Type: Sub-task > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-619) POC: Module odata-jpa-api
[ https://issues.apache.org/jira/browse/OLINGO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-619: --- Assignee: (was: Chandan V.A) > POC: Module odata-jpa-api > - > > Key: OLINGO-619 > URL: https://issues.apache.org/jira/browse/OLINGO-619 > Project: Olingo > Issue Type: Sub-task > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A > Fix For: (JPA) V4 4.0.0-beta-01 > > > Proposal - > The module odata-jpa-api shall contain > 1) ODataJPAServlet for handling OData request and response in the context of > JPA processor > 2) ODataJPAEdmProvider for producing OData V4 complaint metadata from JPA > Entity Model > 3) ODataJPAProcessor a root processor for handing OData V4 complaint requests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-618) POC: odata-jpa-ref-persistence and odata-jpa-ref-web
[ https://issues.apache.org/jira/browse/OLINGO-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-618: --- Assignee: (was: Chandan V.A) > POC: odata-jpa-ref-persistence and odata-jpa-ref-web > > > Key: OLINGO-618 > URL: https://issues.apache.org/jira/browse/OLINGO-618 > Project: Olingo > Issue Type: Sub-task > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A > > Create a JPA Model for the reference scenario. > The model shall be based on Sales Order Processing as done in OData JPA > Processor V2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-285) POC: Support for HQL in OData JPA Processor Library
[ https://issues.apache.org/jira/browse/OLINGO-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15245618#comment-15245618 ] Chandan V.A commented on OLINGO-285: Currently no plans for this PoC > POC: Support for HQL in OData JPA Processor Library > --- > > Key: OLINGO-285 > URL: https://issues.apache.org/jira/browse/OLINGO-285 > Project: Olingo > Issue Type: New Feature > Components: odata2-jpa >Reporter: Chandan V.A >Priority: Trivial > > Evaluate and Support HQL in OData JPA processor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-549) POC: ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-549: --- Assignee: (was: Chandan V.A) > POC: ODataV4 JPA Processor > -- > > Key: OLINGO-549 > URL: https://issues.apache.org/jira/browse/OLINGO-549 > Project: Olingo > Issue Type: New Feature > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A > > A proof of Concept for transforming JPA models into OData V4 compliant EDM > models and supporting OData V4 protocol compliant operations into JPA 2.0/2.1 > specific operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-240) Filter by datetime is not working
[
https://issues.apache.org/jira/browse/OLINGO-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A resolved OLINGO-240.
Resolution: Won't Fix
This issue is specific to hibernate and currently there is no specific handling
in Olingo JPA processor for hibernate. hence closing this ticket.
> Filter by datetime is not working
> -
>
> Key: OLINGO-240
> URL: https://issues.apache.org/jira/browse/OLINGO-240
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 1.2.0
>Reporter: Selvaratnam Ruckman Colins
>Assignee: Chandan V.A
>
> I apply the filter URI for search by datetime as mentioned below,
> /StockMarketData.svc/Tests?$filter=TradingDate eq
> datetime'2009-12-26T21:23:38'
> But it gives me following an error
> =
> http://schemas.microsoft.com/ado/2007/08/dataservices/metadata;>
>
>
> "OData - JPA Runtime: JPA query syntax is not correct"
>
>
> Also i got more information after download the source code and debug
> through,Please take took at the error message below
> org.apache.olingo.odata2.jpa.processor.api.exception.ODataJPARuntimeException:
> "OData - JPA Runtime: JPA query syntax is not correct"
> java.lang.IllegalArgumentException: org.hibernate.QueryException: unexpected
> char: '{' [SELECT E1 FROM au.com.righttime.unity.odata.service.model.Test E1
> WHERE E1.tradingDate = {ts '2009-12-26 21:23:38.000'}]
> Error occurred at ODataRequestHandler.handle
> odataResponse =
> dispatcher.dispatch(method, uriInfo, request.getBody(),
> request.getContentType(), acceptContentType
> .toContentTypeString());
> I used JPA+HIbernate+MySql to export my JPA model and i used following
> annotation to map the date
> @Temporal(TemporalType.TIMESTAMP)
> private Calendar passwordCreatedDate;
> I tried all scenarios like Date...but does not work at all.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OLINGO-882) Olingo closes EntityManager which is managed by the application server
[
https://issues.apache.org/jira/browse/OLINGO-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235148#comment-15235148
]
Chandan V.A commented on OLINGO-882:
Hi Manuel,
To support JTA based transactions the interface
org.apache.olingo.odata2.jpa.processor.api.ODataJPATransaction has to be
implemented by applications and registered as a callback in the Serivce factory
(similar to error callback registration).
If application specific implementation is found by JPA processor library then
the library will not attempt to commit/rollback the transaction ensuring that
the entity manager is not closed leaving that decision to applications. I hope
this solves your use case.
Thanks
Kind Regards
Chandan
> Olingo closes EntityManager which is managed by the application server
> --
>
> Key: OLINGO-882
> URL: https://issues.apache.org/jira/browse/OLINGO-882
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.6
> Environment: Java 1.8, wildfly 8
>Reporter: Manuel Blechschmidt
>Assignee: Michael Bolz
>
> Like I already mentioned in ONLINGO-754 the EntityManager is closed by
> Olingo. This creates a problem if the EntityManager is managed by an
> application server.
> We now decomposed our application and are consuming olingo through a
> transitive dependency. Therefore our dirty hack by "overwritten" classes by
> putting them in our own codebase does not work anymore.
> The problem is here:
> {code:title=https://github.com/apache/olingo-odata2/blob/2.0.6/odata2-jpa-processor/jpa-api/src/main/java/org/apache/olingo/odata2/jpa/processor/api/ODataJPAProcessor.java}
> https://github.com/apache/olingo-odata2/blob/2.0.6/odata2-jpa-processor/jpa-api/src/main/java/org/apache/olingo/odata2/jpa/processor/api/ODataJPAProcessor.java
> {code}
> I will implement my own ODataJPAProcessor to workaround
> {code}
> JBAS011424: Container managed entity manager can only be closed by the
> container (auto-cleared at tx/invocation end and closed when owning component
> is closed.)"},"innererror":"Stacktrace : java.lang.IllegalStateException:
> JBAS011424: Container managed entity manager can only be closed by the
> container (auto-cleared at tx/invocation end and closed when owning component
> is closed.)\n\tat
> org.jboss.as.jpa.container.TransactionScopedEntityManager.close(TransactionScopedEntityManager.java:105)\n\tat
>
> org.apache.olingo.odata2.jpa.processor.api.ODataJPAProcessor.close(ODataJPAProcessor.java:88)\n\tat
>
> de.pcagrar.cloud.rest.odata.filter.FilteringJpaProcessor.executeBatch(FilteringJpaProcessor.java:376)\n\tat
> org.apache.olingo.odata2.core.Dispatcher.dispatch(Dispatcher.java:190)\n\tat
> org.apache.olingo.odata2.core.ODataRequestHandler.handle(ODataRequestHandler.java:130)\n\tat
>
> org.apache.olingo.odata2.core.rest.ODataSubLocator.handle(ODataSubLocator.java:164)\n\tat
>
> org.apache.olingo.odata2.core.rest.ODataSubLocator.handlePost(ODataSubLocator.java:100)\n\tat
>
> de.pcagrar.cloud.rest.odata.ODataRootLocator.handleRequest(ODataRootLocator.java:93)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:498)\n\tat
> org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)\n\tat
>
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)\n\tat
>
> org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)\n\tat
>
> org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)\n\tat
>
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)\n\tat
>
> org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)\n\tat
>
> org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82)\n\tat
>
> org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93)\n\tat
>
> org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)\n\tat
>
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)\n\tat
>
> org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)\n\tat
>
> org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)\n\tat
>
>
[jira] [Commented] (OLINGO-895) Support for @VirtualAccess
[ https://issues.apache.org/jira/browse/OLINGO-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177135#comment-15177135 ] Chandan V.A commented on OLINGO-895: HI Nagendra, I have few comments 1) It is better to create overloaded methods in JPAEntity.java because we dont know how applications use these classess. 2) I dont see any where the Mapping information about virtual access being set? Regards Chandan > Support for @VirtualAccess > -- > > Key: OLINGO-895 > URL: https://issues.apache.org/jira/browse/OLINGO-895 > Project: Olingo > Issue Type: Improvement > Components: odata2-jpa >Reporter: Nagendra >Priority: Critical > Fix For: V2 2.0.7, V2 2.1.0 > > Attachments: org.apache.olingo.odata2.jpa.processor.api.patch, > org.apache.olingo.odata2.jpa.processor.core.patch > > > JPA entities annotated with @VirtualAccess do not have explicit > setters/getters for each attributes rather an generic get(propertyName), > set(value,propertyName). > This allows for dynamic extensibility at runtime, like dynamic mapping of new > columns to existing entities or even dynamic mapping of new tables/views. > For example: > EclipseLink provides dynamic mapping of a DB table/view as explained in the > wiki below > https://wiki.eclipse.org/EclipseLink/Examples/JPA/Dynamic#Dynamic_Configuration_using_API > Design details : http://wiki.eclipse.org/EclipseLink/Development/Dynamic > In cloud world this provides lot of flexibility as each tenant can have their > own extensions of the data model which needs to be exposed via OData APIs and > with this feature one can build a generic code which can handle these tenant > specific extensions. > But currently Olingo JPA processor expects the JPA Entity POJO to have named > setters and getters only. > This needs to be enhanced to support the generic get(propertyName) and > set(propertyName, value) type of POJOs thus enabling the framework consumer > to tap into the dynamic JPA extensibility. > A basic support for this would go a long way, as currently without meddling > with the JPA processor code it would not be possible to support this feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OLINGO-829) Olingo JPA chokes on filter expression
[ https://issues.apache.org/jira/browse/OLINGO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A reassigned OLINGO-829: -- Assignee: Chandan V.A > Olingo JPA chokes on filter expression > -- > > Key: OLINGO-829 > URL: https://issues.apache.org/jira/browse/OLINGO-829 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.6 > Environment: EclipseLink JPA provider >Reporter: Richard Birenheide >Assignee: Chandan V.A > > Olingo JPA chokes on the following filter expression: > $filter=startswith(ABAPReference,%27TEST%27)%20and%20(ABAPReferenceType%20eq%20%27DataElement%27) > with > > class > org.apache.olingo.odata2.jpa.processor.api.exception.ODataJPARuntimeException > : "org.apache.olingo.odata2.jpa.processor.core.ODataExpressionParser: "OData > - JPA Runtime: OData Expression parser - Operator EQ or NE missing". " > > whereas the following > $filter=(ABAPReferenceType%20eq%20%27DataElement%27)%20and%20startswith(ABAPReference,%27TEST%27) > works fine. Just the order of the 'and' expression parts is reversed. > Unfortunately we use a frontend library which generates the expression > automatically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OLINGO-770) JPA OneToMany not able to create entity
[
https://issues.apache.org/jira/browse/OLINGO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A closed OLINGO-770.
--
Resolution: Fixed
Assuming the issue to be fixed. If not please reopen the ticket.
> JPA OneToMany not able to create entity
> ---
>
> Key: OLINGO-770
> URL: https://issues.apache.org/jira/browse/OLINGO-770
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.4
>Reporter: Miguel
>Assignee: Chandan V.A
>
> I have 2 entities OrderHeader and OrderItem,, the relation between then is
> One To Many... with bi-directional
> In the OrderHeader
> @OneToMany(mappedBy="OrderHeader")
> private List orderItems;
> In the OrderItem
> @ManyToOne(fetch=FetchType.LAZY)
> @JoinColumn(name="ORDER_ID", nullable=false)
> private OrderHeader orderHeader;
> When the following is called
> ODataEntry entry = template.requestBody("olingo2://create/OrderHeaders",
> body, ODataEntry.class);
> There is a exception thrown
> Could not match segment: 'OrderHeaders(4004280407L)/OrderItemDetails'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (OLINGO-828) Navigation properties maintained in mapping xml get number suffixes
[ https://issues.apache.org/jira/browse/OLINGO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A reassigned OLINGO-828: -- Assignee: Chandan V.A > Navigation properties maintained in mapping xml get number suffixes > --- > > Key: OLINGO-828 > URL: https://issues.apache.org/jira/browse/OLINGO-828 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.6 >Reporter: Richard Birenheide >Assignee: Chandan V.A > Attachments: globalFieldEdmMapping.xml > > > I have multiple outgoing navigations to the SAME entity. In this case, when > overriding the generated names in the mapping xml, the navigation property > names get number suffixes nevertheless. See eg. attached mapping file where I > maintained relationship names for entity GlobalField. the realtionships to > approverDetail, responsibleUserDetail and lastChangedByUserDetail navigate > all to the same entity, GlobalUser. The final EDM then has Navigation > Properties: > ToGlobalFieldApprover > ToGlobalFieldResponsibleUser1 > ToLastChangedByUser2 > Note that neither the order in the mapping file nor the order in the JPA > entity determines which navigation property gets which suffix. Therefore its > some kind of a gamble whether this remains stable between different > deployments of the war file (it might depend on hashcodes, which is > inherently not guaranteed to be the same between deployments). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OLINGO-736) JPAEntity does not update null values
[
https://issues.apache.org/jira/browse/OLINGO-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A reassigned OLINGO-736:
--
Assignee: Chandan V.A
> JPAEntity does not update null values
> -
>
> Key: OLINGO-736
> URL: https://issues.apache.org/jira/browse/OLINGO-736
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.4
> Environment: Windows 7 64bit, Google Chrome 43.0.2357.134, JDK
> 1.8.0_51
>Reporter: Reinhard Fuchs
>Assignee: Chandan V.A
>Priority: Minor
>
> In "JPAEntity.setProperty" there is an condition regarding null values ("if
> (entityPropertyValue != null) ". This condition prevents database simple type
> values being updateted with null value. According the OData Specification in
> Point 3.3 (http://www.odata.org/documentation/odata-version-2-0/operations/)
> this should work.
> Please complete this condition with an else:
> else {
> method.invoke(entity, entityPropertyValue);
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OLINGO-828) Navigation properties maintained in mapping xml get number suffixes
[ https://issues.apache.org/jira/browse/OLINGO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15029450#comment-15029450 ] Chandan V.A commented on OLINGO-828: Hi Richard, Issue is fixed with commit - http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/c6631df2. However you can also set defaultNaming (in ODataJPAContext) to false so that names maintained on JPA Entity Model is considered and JPA Processor does not generate any names. Thanks Kind Regards Chandan > Navigation properties maintained in mapping xml get number suffixes > --- > > Key: OLINGO-828 > URL: https://issues.apache.org/jira/browse/OLINGO-828 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.6 >Reporter: Richard Birenheide >Assignee: Chandan V.A > Fix For: V2 2.0.6 > > Attachments: globalFieldEdmMapping.xml > > > I have multiple outgoing navigations to the SAME entity. In this case, when > overriding the generated names in the mapping xml, the navigation property > names get number suffixes nevertheless. See eg. attached mapping file where I > maintained relationship names for entity GlobalField. the realtionships to > approverDetail, responsibleUserDetail and lastChangedByUserDetail navigate > all to the same entity, GlobalUser. The final EDM then has Navigation > Properties: > ToGlobalFieldApprover > ToGlobalFieldResponsibleUser1 > ToLastChangedByUser2 > Note that neither the order in the mapping file nor the order in the JPA > entity determines which navigation property gets which suffix. Therefore its > some kind of a gamble whether this remains stable between different > deployments of the war file (it might depend on hashcodes, which is > inherently not guaranteed to be the same between deployments). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OLINGO-828) Navigation properties maintained in mapping xml get number suffixes
[ https://issues.apache.org/jira/browse/OLINGO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A closed OLINGO-828. -- Resolution: Fixed Fix Version/s: V2 2.0.6 > Navigation properties maintained in mapping xml get number suffixes > --- > > Key: OLINGO-828 > URL: https://issues.apache.org/jira/browse/OLINGO-828 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.6 >Reporter: Richard Birenheide >Assignee: Chandan V.A > Fix For: V2 2.0.6 > > Attachments: globalFieldEdmMapping.xml > > > I have multiple outgoing navigations to the SAME entity. In this case, when > overriding the generated names in the mapping xml, the navigation property > names get number suffixes nevertheless. See eg. attached mapping file where I > maintained relationship names for entity GlobalField. the realtionships to > approverDetail, responsibleUserDetail and lastChangedByUserDetail navigate > all to the same entity, GlobalUser. The final EDM then has Navigation > Properties: > ToGlobalFieldApprover > ToGlobalFieldResponsibleUser1 > ToLastChangedByUser2 > Note that neither the order in the mapping file nor the order in the JPA > entity determines which navigation property gets which suffix. Therefore its > some kind of a gamble whether this remains stable between different > deployments of the war file (it might depend on hashcodes, which is > inherently not guaranteed to be the same between deployments). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-766) JPA Processor linkage issue
[
https://issues.apache.org/jira/browse/OLINGO-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A resolved OLINGO-766.
Resolution: Fixed
Fix Version/s: V2 2.0.6
Hello Ashutosh,
The issue is fixed with commit -
http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/d56247a1
Thanks
Kind Regards
Chandan
> JPA Processor linkage issue
> ---
>
> Key: OLINGO-766
> URL: https://issues.apache.org/jira/browse/OLINGO-766
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Reporter: Ashutosh Singh
>Assignee: Chandan V.A
> Fix For: V2 2.0.6
>
>
> I am using Olingo JPA processor and facing an issue.
> We have APIProxy as a main entity which has ConditionalFlow as entity within
> APIProxyEndPoint entity. I have linked a step(Policy1) entity to a
> conditionalFlow (Resource1) entity but did not link any step to other
> conditionalFlow (Resource2) entity.
> But JPA processor is creating the linkage of Policy1 to Resource2 as well
> which should not happen.{APIPortalManagementServiceProcessor}
> Request :
> {
> "conditionalFlows": [
> {
> "name": "Resource1",
> "conditions": "(proxy.pathsuffix MatchesPath \"/Resource1\" OR
> proxy.pathsuffix MatchesPath \"/Resource1/**\" OR proxy.pathsuffix
> MatchesPath \"/Resource1(**\")AND(request.verb = \"DELETE\" OR request.verb =
> \"POST\" OR request.verb = \"PUT\" OR request.verb = \"GET\")",
> "readOnly": true,
> "sequence": 1,
> "request": {
> "steps": [
> {
> "condition": "",
> "policy_name": "Policy1",
> "sequence": 1
> }
> ]
> }
> },
> {
> "name": "Resource2",
> "conditions": "(proxy.pathsuffix MatchesPath \"/Resource2\" OR
> proxy.pathsuffix MatchesPath \"/Resource2/**\" OR proxy.pathsuffix
> MatchesPath \"/Resource2(**\")AND(request.verb = \"DELETE\" OR request.verb =
> \"POST\" OR request.verb = \"PUT\" OR request.verb = \"GET\")",
> "readOnly": true,
> "sequence": 2
> }
> ]
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OLINGO-754) MemoryLeak when using Olingo in Wildfly
[
https://issues.apache.org/jira/browse/OLINGO-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14909084#comment-14909084
]
Chandan V.A commented on OLINGO-754:
Hi Manuel,
The threadlocal variable can be removed by calling the static method
ODataJPAContext.unsetContextInThreadLocal. This should avoid memory leaks and
prevent reuse of same odata context.
[~chrisam]
Is there a way core library can provide a callback to Service Factory at the
end of every call for clean up operations. So that applications can cleanup the
resources.
Regards
Chandan
> MemoryLeak when using Olingo in Wildfly
> ---
>
> Key: OLINGO-754
> URL: https://issues.apache.org/jira/browse/OLINGO-754
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.4
> Environment: java 8, wildfly 8.2, Linux
>Reporter: Manuel Blechschmidt
>
> The following code produces a memory leak in an application server:
> {code:title=org.apache.olingo.odata2.jpa.processor.core.ODataJPAContextImpl}
> @Override
> public void setODataContext(final ODataContext ctx) {
> odataContext = ctx;
> // This produces a memory leak on wildfly
> setContextInThreadLocal(odataContext);
> }
> {code}
> I removed the setContextInThreadLocal and it worked afterwards. I searched
> the whole code how this variable is normaly removed but was not able to find
> the clean way to solve this problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OLINGO-783) Support setting EntityManager into ODataJPAContext
Chandan V.A created OLINGO-783: -- Summary: Support setting EntityManager into ODataJPAContext Key: OLINGO-783 URL: https://issues.apache.org/jira/browse/OLINGO-783 Project: Olingo Issue Type: New Feature Components: odata2-jpa Affects Versions: V2 2.0.5 Reporter: Chandan V.A Assignee: Chandan V.A Priority: Minor Fix For: V2 2.0.5 It shall be possible to set EntityManager into ODataJPAContext. Reference Issue - https://issues.apache.org/jira/browse/OLINGO-580 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OLINGO-783) Support setting EntityManager into ODataJPAContext
[ https://issues.apache.org/jira/browse/OLINGO-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14907648#comment-14907648 ] Chandan V.A edited comment on OLINGO-783 at 9/25/15 6:10 AM: - Fixed with http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/27834c14 [~xenevreu] was (Author: chandan.v.a): Fixed with http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/27834c14 > Support setting EntityManager into ODataJPAContext > -- > > Key: OLINGO-783 > URL: https://issues.apache.org/jira/browse/OLINGO-783 > Project: Olingo > Issue Type: New Feature > Components: odata2-jpa >Affects Versions: V2 2.0.5 >Reporter: Chandan V.A >Assignee: Chandan V.A >Priority: Minor > Fix For: V2 2.0.5 > > > It shall be possible to set EntityManager into ODataJPAContext. > Reference Issue - https://issues.apache.org/jira/browse/OLINGO-580 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-783) Support setting EntityManager into ODataJPAContext
[ https://issues.apache.org/jira/browse/OLINGO-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A resolved OLINGO-783. Resolution: Fixed Fixed with http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/27834c14 > Support setting EntityManager into ODataJPAContext > -- > > Key: OLINGO-783 > URL: https://issues.apache.org/jira/browse/OLINGO-783 > Project: Olingo > Issue Type: New Feature > Components: odata2-jpa >Affects Versions: V2 2.0.5 >Reporter: Chandan V.A >Assignee: Chandan V.A >Priority: Minor > Fix For: V2 2.0.5 > > > It shall be possible to set EntityManager into ODataJPAContext. > Reference Issue - https://issues.apache.org/jira/browse/OLINGO-580 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-770) JPA OneToMany not able to create entity
[
https://issues.apache.org/jira/browse/OLINGO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742107#comment-14742107
]
Chandan V.A commented on OLINGO-770:
Hello Miguel,
Can you please attach the Atom XML that is getting passed to Server.
I suspect the content of the Atom XML. The error "Cannot match segment" will
come provided the link tags are not correctly passed to the JPA processor.
Example: JPA processor uses contents of link tag to link two different
entities. For this the link tag should look as shown below
()
rel=http://schemas.microsoft.com/ado/2007/08/dataservices/related/ >
However if the atom xml contains links tags as shown below
()/
rel=http://schemas.microsoft.com/ado/2007/08/dataservices/related/ >
then JPA processor will throw an error because this link information cannot be
used for linking two entities as per OData specification. I guess this link is
getting generated by your client code and added to the Atom XML. Try removing
this link tag from Atom XML and the request should go through without any
exception.
The link
()/
rel=http://schemas.microsoft.com/ado/2007/08/dataservices/related/ > is needed only if you are trying to execute a deep insert.
An inline entry/feed can be passed under such link tag.
I hope this clarifies your query.
Regards
Chandan
> JPA OneToMany not able to create entity
> ---
>
> Key: OLINGO-770
> URL: https://issues.apache.org/jira/browse/OLINGO-770
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.4
>Reporter: Miguel
>Assignee: Chandan V.A
>
> I have 2 entities OrderHeader and OrderItem,, the relation between then is
> One To Many... with bi-directional
> In the OrderHeader
> @OneToMany(mappedBy="OrderHeader")
> private List orderItems;
> In the OrderItem
> @ManyToOne(fetch=FetchType.LAZY)
> @JoinColumn(name="ORDER_ID", nullable=false)
> private OrderHeader orderHeader;
> When the following is called
> ODataEntry entry = template.requestBody("olingo2://create/OrderHeaders",
> body, ODataEntry.class);
> There is a exception thrown
> Could not match segment: 'OrderHeaders(4004280407L)/OrderItemDetails'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OLINGO-770) JPA OneToMany not able to create entity
[
https://issues.apache.org/jira/browse/OLINGO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14738542#comment-14738542
]
Chandan V.A commented on OLINGO-770:
Hi Miguel.
Can you share the request payload.
Regards
Chandan
> JPA OneToMany not able to create entity
> ---
>
> Key: OLINGO-770
> URL: https://issues.apache.org/jira/browse/OLINGO-770
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.4
>Reporter: Miguel
>Assignee: Chandan V.A
>
> I have 2 entities OrderHeader and OrderItem,, the relation between then is
> One To Many... with bi-directional
> In the OrderHeader
> @OneToMany(mappedBy="OrderHeader")
> private List orderItems;
> In the OrderItem
> @ManyToOne(fetch=FetchType.LAZY)
> @JoinColumn(name="ORDER_ID", nullable=false)
> private OrderHeader orderHeader;
> When the following is called
> ODataEntry entry = template.requestBody("olingo2://create/OrderHeaders",
> body, ODataEntry.class);
> There is a exception thrown
> Could not match segment: 'OrderHeaders(4004280407L)/OrderItemDetails'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (OLINGO-770) JPA OneToMany not able to create entity
[
https://issues.apache.org/jira/browse/OLINGO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A reassigned OLINGO-770:
--
Assignee: Chandan V.A
> JPA OneToMany not able to create entity
> ---
>
> Key: OLINGO-770
> URL: https://issues.apache.org/jira/browse/OLINGO-770
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.4
>Reporter: Miguel
>Assignee: Chandan V.A
>
> I have 2 entities OrderHeader and OrderItem,, the relation between then is
> One To Many... with bi-directional
> In the OrderHeader
> @OneToMany(mappedBy="OrderHeader")
> private List orderItems;
> In the OrderItem
> @ManyToOne(fetch=FetchType.LAZY)
> @JoinColumn(name="ORDER_ID", nullable=false)
> private OrderHeader orderHeader;
> When the following is called
> ODataEntry entry = template.requestBody("olingo2://create/OrderHeaders",
> body, ODataEntry.class);
> There is a exception thrown
> Could not match segment: 'OrderHeaders(4004280407L)/OrderItemDetails'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OLINGO-754) MemoryLeak when using Olingo in Wildfly
[
https://issues.apache.org/jira/browse/OLINGO-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732286#comment-14732286
]
Chandan V.A commented on OLINGO-754:
Hi Manuel,
It is needed in case applications likes to access the Odata context. For
example if JPA Entity Listeners would like to access the Odata jpa context then
it can use it from thread local context.
Secondly can you please tell is the memory leak due to not closing Entity
Manager? There is fix available in 2.0.5-SNAPSHOT for not closing entity
manager.
Thanks
Kind regards
Chandan
> MemoryLeak when using Olingo in Wildfly
> ---
>
> Key: OLINGO-754
> URL: https://issues.apache.org/jira/browse/OLINGO-754
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.4
> Environment: java 8, wildfly 8.2, Linux
>Reporter: Manuel Blechschmidt
>
> The following code produces a memory leak in an application server:
> {code:title=org.apache.olingo.odata2.jpa.processor.core.ODataJPAContextImpl}
> @Override
> public void setODataContext(final ODataContext ctx) {
> odataContext = ctx;
> // This produces a memory leak on wildfly
> setContextInThreadLocal(odataContext);
> }
> {code}
> I removed the setContextInThreadLocal and it worked afterwards. I searched
> the whole code how this variable is normaly removed but was not able to find
> the clean way to solve this problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OLINGO-619) POC: Module odata-jpa-api
[ https://issues.apache.org/jira/browse/OLINGO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14708315#comment-14708315 ] Chandan V.A edited comment on OLINGO-619 at 9/6/15 2:59 PM: Initial version on OData Servlet Implementation - http://git-wip-us.apache.org/repos/asf/olingo-odata4/commit/e3a20bb9 http://git-wip-us.apache.org/repos/asf/olingo-odata4/commit/7edc5efa was (Author: chandan.v.a): Initial version on OData Servlet Implementation - http://git-wip-us.apache.org/repos/asf/olingo-odata4/commit/e3a20bb9 > POC: Module odata-jpa-api > - > > Key: OLINGO-619 > URL: https://issues.apache.org/jira/browse/OLINGO-619 > Project: Olingo > Issue Type: Sub-task > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A >Assignee: Chandan V.A > Fix For: (JPA) V4 4.0.0-beta-01 > > > Proposal - > The module odata-jpa-api shall contain > 1) ODataJPAServlet for handling OData request and response in the context of > JPA processor > 2) ODataJPAEdmProvider for producing OData V4 complaint metadata from JPA > Entity Model > 3) ODataJPAProcessor a root processor for handing OData V4 complaint requests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OLINGO-768) POC: odata-jpa-core Exception Handling
[ https://issues.apache.org/jira/browse/OLINGO-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A reassigned OLINGO-768: -- Assignee: Chandan V.A > POC: odata-jpa-core Exception Handling > -- > > Key: OLINGO-768 > URL: https://issues.apache.org/jira/browse/OLINGO-768 > Project: Olingo > Issue Type: Sub-task > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A >Assignee: Chandan V.A > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-618) POC: odata-jpa-ref-persistence and odata-jpa-ref-web
[ https://issues.apache.org/jira/browse/OLINGO-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732413#comment-14732413 ] Chandan V.A commented on OLINGO-618: http://git-wip-us.apache.org/repos/asf/olingo-odata4/commit/0b6eedbe > POC: odata-jpa-ref-persistence and odata-jpa-ref-web > > > Key: OLINGO-618 > URL: https://issues.apache.org/jira/browse/OLINGO-618 > Project: Olingo > Issue Type: Sub-task > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A >Assignee: Chandan V.A > > Create a JPA Model for the reference scenario. > The model shall be based on Sales Order Processing as done in OData JPA > Processor V2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-768) POC: odata-jpa-core Exception Handling
[ https://issues.apache.org/jira/browse/OLINGO-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732412#comment-14732412 ] Chandan V.A commented on OLINGO-768: http://git-wip-us.apache.org/repos/asf/olingo-odata4/commit/b1d625dd > POC: odata-jpa-core Exception Handling > -- > > Key: OLINGO-768 > URL: https://issues.apache.org/jira/browse/OLINGO-768 > Project: Olingo > Issue Type: Sub-task > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A >Assignee: Chandan V.A > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OLINGO-765) POC: odata-jpa-core
[ https://issues.apache.org/jira/browse/OLINGO-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14708316#comment-14708316 ] Chandan V.A edited comment on OLINGO-765 at 9/6/15 3:04 PM: http://git-wip-us.apache.org/repos/asf/olingo-odata4/commit/503acb0c http://git-wip-us.apache.org/repos/asf/olingo-odata4/commit/f17dda08 was (Author: chandan.v.a): http://git-wip-us.apache.org/repos/asf/olingo-odata4/commit/503acb0c > POC: odata-jpa-core > --- > > Key: OLINGO-765 > URL: https://issues.apache.org/jira/browse/OLINGO-765 > Project: Olingo > Issue Type: Sub-task > Components: odata4-JPA >Affects Versions: (Java) V4 4.0.0-beta-01 >Reporter: Chandan V.A >Assignee: Chandan V.A > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-768) POC: odata-jpa-core Exception Handling
[
https://issues.apache.org/jira/browse/OLINGO-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14721408#comment-14721408
]
Chandan V.A commented on OLINGO-768:
h4.+Exception Class+
# Abstract {{org.apache.olingo.jpa.api.exception.ODataJPAException}} extending
{{org.apache.olingo.server.api.ODataTranslatedException}}. This exception class
is thrown by all interface and class types defined in odata-jpa-api.
\\
h4.+Specialized Exception Classes+
# {{org.apache.olingo.jpa.api.exception.core.ODataJPAModelException}} extending
abstract ODataJPAException - ODataJPAModelException is thrown while
transforming or accessing the JPA Model into EDM.
# {{org.apache.olingo.jpa.core.exception.ODataJPARuntimeException}} extending
abstract ODataJPAException - ODataJPARuntimeException is thrown while handling
request and response of OData calls.
h4.+Message Bundles+
{{/src/main/resources}} in odata-jpa-core contains two message properties
- {{odata-jpa-rt-exception-i18n.properties}}
- {{odata-jpa-model-exception-i18n.properties}}
POC: odata-jpa-core Exception Handling
--
Key: OLINGO-768
URL: https://issues.apache.org/jira/browse/OLINGO-768
Project: Olingo
Issue Type: Sub-task
Components: odata4-JPA
Affects Versions: (JPA) V4 4.0.0-beta-01
Reporter: Chandan V.A
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OLINGO-765) POC: odata-jpa-core
[ https://issues.apache.org/jira/browse/OLINGO-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-765: --- Issue Type: Task (was: New Feature) POC: odata-jpa-core --- Key: OLINGO-765 URL: https://issues.apache.org/jira/browse/OLINGO-765 Project: Olingo Issue Type: Task Components: odata4-JPA Affects Versions: (Java) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-765) POC: odata-jpa-core
[ https://issues.apache.org/jira/browse/OLINGO-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-765: --- Issue Type: Sub-task (was: Task) Parent: OLINGO-549 POC: odata-jpa-core --- Key: OLINGO-765 URL: https://issues.apache.org/jira/browse/OLINGO-765 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Affects Versions: (Java) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OLINGO-768) POC: odata-jpa-core Exception Handling
Chandan V.A created OLINGO-768: -- Summary: POC: odata-jpa-core Exception Handling Key: OLINGO-768 URL: https://issues.apache.org/jira/browse/OLINGO-768 Project: Olingo Issue Type: Sub-task Affects Versions: (JPA) V4 4.0.0-beta-01 Reporter: Chandan V.A -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-765) POC: odata-jpa-core
[ https://issues.apache.org/jira/browse/OLINGO-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-765: --- Issue Type: New Feature (was: Sub-task) Parent: (was: OLINGO-549) POC: odata-jpa-core --- Key: OLINGO-765 URL: https://issues.apache.org/jira/browse/OLINGO-765 Project: Olingo Issue Type: New Feature Components: odata4-JPA Affects Versions: (Java) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OLINGO-765) POC: odata-jpa-ore
Chandan V.A created OLINGO-765: -- Summary: POC: odata-jpa-ore Key: OLINGO-765 URL: https://issues.apache.org/jira/browse/OLINGO-765 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Affects Versions: (Java) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-619) POC: Module odata-jpa-api
[ https://issues.apache.org/jira/browse/OLINGO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708315#comment-14708315 ] Chandan V.A commented on OLINGO-619: Initial version on OData Servlet Implementation - http://git-wip-us.apache.org/repos/asf/olingo-odata4/commit/e3a20bb9 POC: Module odata-jpa-api - Key: OLINGO-619 URL: https://issues.apache.org/jira/browse/OLINGO-619 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Affects Versions: (JPA) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A Fix For: (JPA) V4 4.0.0-beta-01 Proposal - The module odata-jpa-api shall contain 1) ODataJPAServlet for handling OData request and response in the context of JPA processor 2) ODataJPAEdmProvider for producing OData V4 complaint metadata from JPA Entity Model 3) ODataJPAProcessor a root processor for handing OData V4 complaint requests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-765) POC: odata-jpa-core
[ https://issues.apache.org/jira/browse/OLINGO-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708316#comment-14708316 ] Chandan V.A commented on OLINGO-765: http://git-wip-us.apache.org/repos/asf/olingo-odata4/commit/503acb0c POC: odata-jpa-core --- Key: OLINGO-765 URL: https://issues.apache.org/jira/browse/OLINGO-765 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Affects Versions: (Java) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OLINGO-764) JPA - DeltaToken not getting generated
[ https://issues.apache.org/jira/browse/OLINGO-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A closed OLINGO-764. -- JPA - DeltaToken not getting generated --- Key: OLINGO-764 URL: https://issues.apache.org/jira/browse/OLINGO-764 Project: Olingo Issue Type: Bug Components: odata2-jpa Reporter: Chandan V.A Assignee: Chandan V.A Fix For: V2 2.0.5 Delta Token is not generated when getQuery method of ODataJPATombstoneListener is implemented. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OLINGO-764) JPA - DeltaToken not getting generated
Chandan V.A created OLINGO-764: -- Summary: JPA - DeltaToken not getting generated Key: OLINGO-764 URL: https://issues.apache.org/jira/browse/OLINGO-764 Project: Olingo Issue Type: Bug Components: odata2-jpa Reporter: Chandan V.A Assignee: Chandan V.A Delta Token is not generated when getQuery method of ODataJPATombstoneListener is implemented. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-764) JPA - DeltaToken not getting generated
[ https://issues.apache.org/jira/browse/OLINGO-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A resolved OLINGO-764. Resolution: Fixed Fix Version/s: V2 2.0.5 Issue is fixed with commit http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/14d97bf8 JPA - DeltaToken not getting generated --- Key: OLINGO-764 URL: https://issues.apache.org/jira/browse/OLINGO-764 Project: Olingo Issue Type: Bug Components: odata2-jpa Reporter: Chandan V.A Assignee: Chandan V.A Fix For: V2 2.0.5 Delta Token is not generated when getQuery method of ODataJPATombstoneListener is implemented. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-744) Bug in Function Imports: nullable parameters not supported
[
https://issues.apache.org/jira/browse/OLINGO-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A resolved OLINGO-744.
Resolution: Fixed
Fix Version/s: V2 2.0.5
Hi,
The issue is fixed with commit -
http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/c0cdf8b6
Regards
Chandan
Bug in Function Imports: nullable parameters not supported
--
Key: OLINGO-744
URL: https://issues.apache.org/jira/browse/OLINGO-744
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.4
Reporter: Andreas Pfenninger
Assignee: Chandan V.A
Fix For: V2 2.0.5
The OLingo framework seems not to allow optional parameters, e.g. for the
following function:
{code:xml}
FunctionImport Name=Function ReturnType=Collection(PU.Foo)
EntitySet=Foos m:HttpMethod=GET
Parameter Name=param1 Type=Edm.String Nullable=true
Parameter Name=param2 Type=Edm.Int64
/FunctionImport
{code}
Annotation: {code:java}
@EdmFunctionImportParameter(name = param1, facets = @EdmFacets(nullable =
true))
{code}
Even though parameter param1 has the attribute Nullable=true, OLingo
throws a NullPointerException if that parameter is not passed in the query:
{code}test.svc/Function?param2=3{code}
The desired behavior is a function with optional query parameter param1.
Root cause is a bug in JPAFunctionContext.java:
- line 97: arguments array in method getAruguments initialized with wrong
size
- line 119: Missing null check in method convertArguement
It would be very much appreciated if you could fix the bug in a future
release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (OLINGO-744) Bug in Function Imports: nullable parameters not supported
[
https://issues.apache.org/jira/browse/OLINGO-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A reassigned OLINGO-744:
--
Assignee: Chandan V.A
Bug in Function Imports: nullable parameters not supported
--
Key: OLINGO-744
URL: https://issues.apache.org/jira/browse/OLINGO-744
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.4
Reporter: Andreas Pfenninger
Assignee: Chandan V.A
The OLingo framework seems not to allow optional parameters, e.g. for the
following function:
{code:xml}
FunctionImport Name=Function ReturnType=Collection(PU.Foo)
EntitySet=Foos m:HttpMethod=GET
Parameter Name=param1 Type=Edm.String Nullable=true
Parameter Name=param2 Type=Edm.Int64
/FunctionImport
{code}
Annotation: {code:java}
@EdmFunctionImportParameter(name = param1, facets = @EdmFacets(nullable =
true))
{code}
Even though parameter param1 has the attribute Nullable=true, OLingo
throws a NullPointerException if that parameter is not passed in the query:
{code}test.svc/Function?param2=3{code}
The desired behavior is a function with optional query parameter param1.
Root cause is a bug in JPAFunctionContext.java:
- line 97: arguments array in method getAruguments initialized with wrong
size
- line 119: Missing null check in method convertArguement
It would be very much appreciated if you could fix the bug in a future
release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (OLINGO-740) Association does not get created when there are multiple relationships between 2 tables
[
https://issues.apache.org/jira/browse/OLINGO-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A reassigned OLINGO-740:
--
Assignee: Chandan V.A
Association does not get created when there are multiple relationships
between 2 tables
---
Key: OLINGO-740
URL: https://issues.apache.org/jira/browse/OLINGO-740
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.5
Reporter: arathi m
Assignee: Chandan V.A
I have 2 DB tables with multiple associations between them
Table A (id, name, tableb_id)
Table B (id, name tablea_id)
First, an association gets correctly created for tableA with the name
TableA_TableB. While creating an association for TableB, the code searches
for an association named TableA_TableB instead of searching/creating
TableB_TableA association. The faulty code is at
org.apache.olingo.odata2.jpa.processor.core.access.model.JPAEdmNameBuilder.build()
if (end1Name.equals(end2Name)) {
associationName = end1Name + UNDERSCORE + end2Name;
associationName =
associationName + UNDERSCORE +
multiplicityToString(association.getEnd1().getMultiplicity()) + UNDERSCORE
+ multiplicityToString(association.getEnd2().getMultiplicity())
+ Integer.toString(count);
} else {
if (end1Name.compareToIgnoreCase(end2Name) 0) {
associationName = end2Name + UNDERSCORE + end1Name;
} else {
associationName = end1Name + UNDERSCORE + end2Name;
}
associationName = end1Name + UNDERSCORE + end2Name;
if (count = 1) {
associationName = associationName + Integer.toString(count - 1);
}
The fix is to create associationName = end1Name+UNDERSCORE+end2Name
instead of arranging the names in ascending order.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OLINGO-740) Association does not get created when there are multiple relationships between 2 tables
[
https://issues.apache.org/jira/browse/OLINGO-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642311#comment-14642311
]
Chandan V.A commented on OLINGO-740:
Hi Arathi,
From the issue description I infer following
1) You have a two JPA entities with bi-directional relationship
2) For the above JPA definition, there is only one association created with end
types as TableA and Table B in EDM.
3) I believe in EDM and OData entity for TableA is created with a navifation
property bound with association as TABLEA_TABLEB. Similarly in OData entity for
TableB a navigation property is created bound with association as
TABLEA_TABLEB. Here both the navigations use the same association type but with
different roles.
If so then it is an expected behavior.
Regards
Chandan
Association does not get created when there are multiple relationships
between 2 tables
---
Key: OLINGO-740
URL: https://issues.apache.org/jira/browse/OLINGO-740
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.5
Reporter: arathi m
I have 2 DB tables with multiple associations between them
Table A (id, name, tableb_id)
Table B (id, name tablea_id)
First, an association gets correctly created for tableA with the name
TableA_TableB. While creating an association for TableB, the code searches
for an association named TableA_TableB instead of searching/creating
TableB_TableA association. The faulty code is at
org.apache.olingo.odata2.jpa.processor.core.access.model.JPAEdmNameBuilder.build()
if (end1Name.equals(end2Name)) {
associationName = end1Name + UNDERSCORE + end2Name;
associationName =
associationName + UNDERSCORE +
multiplicityToString(association.getEnd1().getMultiplicity()) + UNDERSCORE
+ multiplicityToString(association.getEnd2().getMultiplicity())
+ Integer.toString(count);
} else {
if (end1Name.compareToIgnoreCase(end2Name) 0) {
associationName = end2Name + UNDERSCORE + end1Name;
} else {
associationName = end1Name + UNDERSCORE + end2Name;
}
associationName = end1Name + UNDERSCORE + end2Name;
if (count = 1) {
associationName = associationName + Integer.toString(count - 1);
}
The fix is to create associationName = end1Name+UNDERSCORE+end2Name
instead of arranging the names in ascending order.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OLINGO-720) ODataJPATombstoneEntityListener does not support count and GetEntity
[ https://issues.apache.org/jira/browse/OLINGO-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623821#comment-14623821 ] Chandan V.A commented on OLINGO-720: At times it is required to build custom query objects for OData's GetEntitySet, GetEntity, GetEntityCount, GetEntitySetCount, GetEntity before Delete and Update request. Currently there is no provision for applications to build custom query objects. In order to build custom query object applications can extend 1) org.apache.olingo.odata2.jpa.processor.api.ODataJPAQueryExtensionEntityListener class and implement the necessary methods in the class. If a method is not overriden by the inheriting class then JPA processor builds the JPA query using default logic. 2) Register the class as JPA entity listener with the JPA entity for which custom query needs to be built. 3) If the extended class supports OData Tombstone feature then return true for the method call isTombstoneSupported() else just return false. Applications wishing to just support OData Tombstone (delta query) feature can extend org.apache.olingo.odata2.jpa.processor.api.ODataJPATombstoneEntityListener. However applications wishing to support custom JPA query and also would like to support OData Tombstone feature can extend org.apache.olingo.odata2.jpa.processor.api.ODataJPAQueryExtensionEntityListener and return true for the method call isTombstoneSupported() as the class org.apache.olingo.odata2.jpa.processor.api.ODataJPAQueryExtensionEntityListener extends org.apache.olingo.odata2.jpa.processor.api.ODataJPATombstoneEntityListener. Please Note:- A JPA entity can be registered with an entity listener that either extends ODataJPAQueryExtensionEntityListener or ODataJPATombstoneEntityListener. If a JPA entity is registered with two different entity listeners with one extending ODataJPATombstoneEntityListener and the other ODataJPAQueryExtensionEntityListener will not work as expected. Thanks Kind Regards Chandan ODataJPATombstoneEntityListener does not support count and GetEntity Key: OLINGO-720 URL: https://issues.apache.org/jira/browse/OLINGO-720 Project: Olingo Issue Type: Bug Components: odata2-jpa Affects Versions: V2 2.0.4 Reporter: Christian Wilhelm Assignee: Chandan V.A Hello, The ODataJPATombstoneEntityListener which is originally reuqired for the DeltaQuerySuppoort is not listening for OData count operation and the GetEntity operation. I am (mis-)using this listener concept for injecting a security layer - therefore the two operations mentioned above should be included in the ODataJPATombstoneEntityListener concept. Is it possible to add this function? Best regards, Christian -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-721) Removing links between the entities throws exception
[
https://issues.apache.org/jira/browse/OLINGO-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616135#comment-14616135
]
Chandan V.A commented on OLINGO-721:
The fix is part of 2.0.5-SNAPSHOT
Regards
Chandan
Removing links between the entities throws exception
Key: OLINGO-721
URL: https://issues.apache.org/jira/browse/OLINGO-721
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.4
Reporter: Madhuri Muthyalu
Assignee: Chandan V.A
Fix For: V2 2.0.5
Consider 2 entities A and B, there is a bidirectional association between
these entities(A to B and B to A).
Created an association between these entities via $links refer the below URI
root-url/B(5001L)/$links/ADetails with the request payload as
{
uri:A(4901L)
}
and the association gets created able to retrieve this data via $expand
Now tried to remove this association via $links with the HTTP DELETE request
refer to the following URI
root-url/A(4901L)/$links/BDetails(5001L)
Get an exception Object: null is not a known Entity type.
here is the excerpt stack trace
stacktrace: [
{
class:
org.eclipse.persistence.internal.jpa.EntityManagerImpl,
method: contains,
line: 1077
},
{
class:
org.apache.olingo.odata2.jpa.processor.core.access.data.JPALink,
method: save,
line: 164
},
{
class:
org.apache.olingo.odata2.jpa.processor.core.access.data.JPAProcessorImpl,
method: deleteLink,
line: 525
},
{
class:
org.apache.olingo.odata2.jpa.processor.core.access.data.JPAProcessorImpl,
method: process,
line: 336
},
{
class:
org.apache.olingo.odata2.jpa.processor.core.ODataJPAProcessorDefault,
method: deleteEntityLink,
line: 237
},
{
class: org.apache.olingo.odata2.core.Dispatcher,
method: dispatch,
line: 165
},
{
class:
org.apache.olingo.odata2.core.ODataRequestHandler,
method: handle,
line: 129
},
{
class:
org.apache.olingo.odata2.core.rest.ODataSubLocator,
method: handle,
line: 167
},
{
class:
org.apache.olingo.odata2.core.rest.ODataSubLocator,
method: handleDelete,
line: 78
},
{
class: sun.reflect.NativeMethodAccessorImpl,
method: invoke0,
line: -2
},
{
class: sun.reflect.NativeMethodAccessorImpl,
method: invoke,
line: -1
},
{}.]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OLINGO-546) Cannot create entities with composite key using EmbeddedId annotation
[
https://issues.apache.org/jira/browse/OLINGO-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A resolved OLINGO-546.
Resolution: Cannot Reproduce
Hello Riccardo,
I was not able to reproduce the issue mentioned by you. I hope the issue is
solved.
Regards
Chandan
Cannot create entities with composite key using EmbeddedId annotation
-
Key: OLINGO-546
URL: https://issues.apache.org/jira/browse/OLINGO-546
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.1
Environment: Windows 7, Apache Tomcat 7.0.56
Reporter: Riccardo
Assignee: Chandan V.A
Priority: Critical
Hi,
I've some problems when i create entities with composite key using EmbeddedId
annotation. Below there are the classes causing the issue
{code:title=TestTable.java|borderStyle=solid}
@Entity
@Table(name=TEST_TABLE)
public class TestTable implements Serializable {
private static final long serialVersionUID = 1L;
@EmbeddedId
private TestTablePK id;
@Column(name=COL_GENERIC, length=20)
private String colGeneric;
public TestTable() {
}
public TestTablePK getId() {
return this.id;
}
public void setId(TestTablePK id) {
this.id = id;
}
public String getColGeneric() {
return this.colGeneric;
}
public void setColGeneric(String colGeneric) {
this.colGeneric = colGeneric;
}
}
{code}
{code:title=TestTablePK.java|borderStyle=solid}
@Embeddable
public class TestTablePK implements Serializable {
private static final long serialVersionUID = 1L;
@Column(name=COL_KEY1, unique=true, nullable=false)
private int colKey1;
@Column(name=COL_KEY2, unique=true, nullable=false)
private int colKey2;
public TestTablePK() {
}
public int getColKey1() {
return this.colKey1;
}
public void setColKey1(int colKey1) {
this.colKey1 = colKey1;
}
public int getColKey2() {
return this.colKey2;
}
public void setColKey2(int colKey2) {
this.colKey2 = colKey2;
}
public boolean equals(Object other) {
if (this == other) {
return true;
}
if (!(other instanceof TestTablePK)) {
return false;
}
TestTablePK castOther = (TestTablePK)other;
return
(this.colKey1 == castOther.colKey1)
(this.colKey2 == castOther.colKey2);
}
public int hashCode() {
final int prime = 31;
int hash = 17;
hash = hash * prime + this.colKey1;
hash = hash * prime + this.colKey2;
return hash;
}
}
{code}
When i get the $metadata, the application thrown the following exception
{color:red}
java.lang.NullPointerException
at
org.apache.olingo.odata2.jpa.processor.core.access.model.JPAEdmMappingModelService.searchJPAEmbeddableTypeMapType(JPAEdmMappingModelService.java:196)
at
org.apache.olingo.odata2.jpa.processor.core.access.model.JPAEdmMappingModelService.checkExclusionOfJPAEmbeddableType(JPAEdmMappingModelService.java:238)
at
org.apache.olingo.odata2.jpa.processor.core.model.JPAEdmComplexType$JPAEdmComplexTypeBuilder.isExcluded(JPAEdmComplexType.java:260)
at
org.apache.olingo.odata2.jpa.processor.core.model.JPAEdmComplexType$JPAEdmComplexTypeBuilder.build(JPAEdmComplexType.java:239)
at
org.apache.olingo.odata2.jpa.processor.core.model.JPAEdmSchema$JPAEdmSchemaBuilder.build(JPAEdmSchema.java:116)
at
org.apache.olingo.odata2.jpa.processor.core.model.JPAEdmModel$JPAEdmModelBuilder.build(JPAEdmModel.java:61)
at
org.apache.olingo.odata2.jpa.processor.core.edm.ODataJPAEdmProvider.getSchemas(ODataJPAEdmProvider.java:282)
at
org.apache.olingo.odata2.core.edm.provider.EdmServiceMetadataImplProv.getDataServiceVersion(EdmServiceMetadataImplProv.java:102)
at
org.apache.olingo.odata2.api.processor.ODataSingleProcessor.readMetadata(ODataSingleProcessor.java:378)
at
org.apache.olingo.odata2.core.Dispatcher.dispatch(Dispatcher.java:182)
at
org.apache.olingo.odata2.core.ODataRequestHandler.handle(ODataRequestHandler.java:129)
at
org.apache.olingo.odata2.core.rest.ODataSubLocator.handle(ODataSubLocator.java:167)
at
org.apache.olingo.odata2.core.rest.ODataSubLocator.handleGet(ODataSubLocator.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
[jira] [Assigned] (OLINGO-720) ODataJPATombstoneEntityListener does not support count and GetEntity
[ https://issues.apache.org/jira/browse/OLINGO-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A reassigned OLINGO-720: -- Assignee: Chandan V.A ODataJPATombstoneEntityListener does not support count and GetEntity Key: OLINGO-720 URL: https://issues.apache.org/jira/browse/OLINGO-720 Project: Olingo Issue Type: Bug Components: odata2-jpa Affects Versions: V2 2.0.4 Reporter: Christian Wilhelm Assignee: Chandan V.A Hello, The ODataJPATombstoneEntityListener which is originally reuqired for the DeltaQuerySuppoort is not listening for OData count operation and the GetEntity operation. I am (mis-)using this listener concept for injecting a security layer - therefore the two operations mentioned above should be included in the ODataJPATombstoneEntityListener concept. Is it possible to add this function? Best regards, Christian -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OLINGO-711) Using an Entity in an Embeddable Object
[
https://issues.apache.org/jira/browse/OLINGO-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A reassigned OLINGO-711:
--
Assignee: Chandan V.A
Using an Entity in an Embeddable Object
---
Key: OLINGO-711
URL: https://issues.apache.org/jira/browse/OLINGO-711
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.4
Reporter: Gregory Tutt
Assignee: Chandan V.A
Priority: Critical
When calling the $metadata service, I receive an error which is caused by an
exception raised when generating the model.
I have an Entity that contains an Embeddable object which contains an other
Entity. When calling the $metadata service, I receive an error message.
@Embeddable
public class ControlRecord implements Serializable {
@JoinColumn(name=createdBy)
@ManyToOne
private UserDefinition createdBy;
}
@Entity
public class UserDefinition implements Serializable {
@Id
@GeneratedValue
private Long id;
...
}
@Entity
public class Component implements Serializable {
@Id
@GeneratedValue
private Long id;
@Embedded
private ControlRecord ctrlRecord;
)
The error message is empty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (OLINGO-599) Improvement in error messages.
[ https://issues.apache.org/jira/browse/OLINGO-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A reassigned OLINGO-599: -- Assignee: Chandan V.A Improvement in error messages. -- Key: OLINGO-599 URL: https://issues.apache.org/jira/browse/OLINGO-599 Project: Olingo Issue Type: Improvement Components: odata2-jpa Affects Versions: V2 2.0.2, V2 2.0.3 Environment: Olingo JPA used in Integration Gateway Reporter: Sachin C Assignee: Chandan V.A Original Estimate: 336h Remaining Estimate: 336h Hi, This is regarding the error messages thrown from the Olingo JPA side when there is a failure due a wrong payload or something like that. For now the error messages are all of the form OData JPA METHOD syntax is not correct. Where METHOD can be CREATE,DELETE,UPDATE etc. What we want is a more clear error as to what went wrong such as So and so constraint is violated or any statement which is more specific regarding the cause of the error. Thanks, Sachin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-711) Using an Entity in an Embeddable Object
[
https://issues.apache.org/jira/browse/OLINGO-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14607914#comment-14607914
]
Chandan V.A commented on OLINGO-711:
Hello Gregory,
Having JPA relationships inside embeddable types are not supported. Because
Embeddable types in JPA entity definitions are transformed into Complex Types
in OData model. In your case JPA processor cannot map such definitions to OData
metadata definition.
You could get more detailed errors by executing the HTTP request with
odata-debug=json query parameter.
Thanks
Kind regards
Chandan
Using an Entity in an Embeddable Object
---
Key: OLINGO-711
URL: https://issues.apache.org/jira/browse/OLINGO-711
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.4
Reporter: Gregory Tutt
Assignee: Chandan V.A
Priority: Critical
When calling the $metadata service, I receive an error which is caused by an
exception raised when generating the model.
I have an Entity that contains an Embeddable object which contains an other
Entity. When calling the $metadata service, I receive an error message.
@Embeddable
public class ControlRecord implements Serializable {
@JoinColumn(name=createdBy)
@ManyToOne
private UserDefinition createdBy;
}
@Entity
public class UserDefinition implements Serializable {
@Id
@GeneratedValue
private Long id;
...
}
@Entity
public class Component implements Serializable {
@Id
@GeneratedValue
private Long id;
@Embedded
private ControlRecord ctrlRecord;
)
The error message is empty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OLINGO-711) Using an Entity in an Embeddable Object
[
https://issues.apache.org/jira/browse/OLINGO-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A resolved OLINGO-711.
Resolution: Not A Problem
Using an Entity in an Embeddable Object
---
Key: OLINGO-711
URL: https://issues.apache.org/jira/browse/OLINGO-711
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.4
Reporter: Gregory Tutt
Assignee: Chandan V.A
Priority: Critical
When calling the $metadata service, I receive an error which is caused by an
exception raised when generating the model.
I have an Entity that contains an Embeddable object which contains an other
Entity. When calling the $metadata service, I receive an error message.
@Embeddable
public class ControlRecord implements Serializable {
@JoinColumn(name=createdBy)
@ManyToOne
private UserDefinition createdBy;
}
@Entity
public class UserDefinition implements Serializable {
@Id
@GeneratedValue
private Long id;
...
}
@Entity
public class Component implements Serializable {
@Id
@GeneratedValue
private Long id;
@Embedded
private ControlRecord ctrlRecord;
)
The error message is empty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OLINGO-719) JPA - Complex Type not supported in $orderby expression
[ https://issues.apache.org/jira/browse/OLINGO-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A resolved OLINGO-719. Resolution: Fixed Fix Version/s: V2 2.0.5 Fixed with commit - http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/dd0625e3 JPA - Complex Type not supported in $orderby expression --- Key: OLINGO-719 URL: https://issues.apache.org/jira/browse/OLINGO-719 Project: Olingo Issue Type: Bug Components: odata2-jpa Affects Versions: V2 2.0.4 Reporter: Chandan V.A Assignee: Chandan V.A Fix For: V2 2.0.5 An exception is thrown when complex type is used in $orderby expression -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-714) ClassCastException on expand when multiple times the same entity is referenced
[
https://issues.apache.org/jira/browse/OLINGO-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A resolved OLINGO-714.
Resolution: Fixed
Fix Version/s: V2 2.0.5
Hi,
The issue was with navigation property getting bound to a wrong association.
This happened because the names of association with end types Entity and
OtherEntity and Multiplicity 1:N and N:1 conflicted with each other. This
resulted in the generation of only one association in the end and that was
shared by the navigation properties otherEntities and primaryOtherEntity.
With the fix -
http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/0f08913b now
associations are generated with proper names and hence there shall not be
conflicting names. This will result in navigation properties to bind to correct
association names.
Thanks
Kind regards
Chandan
ClassCastException on expand when multiple times the same entity is referenced
--
Key: OLINGO-714
URL: https://issues.apache.org/jira/browse/OLINGO-714
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.5
Environment: java 8, wildfly-8.2.0, hibernate 4.3.7.Final
Reporter: Manuel Blechschmidt
Assignee: Chandan V.A
Labels: ClassCastException
Fix For: V2 2.0.5
When an entity has multiple relations to another entity and one of these
relations is a unidirectional @ManyToOne relation a class cast exception is
thrown.
e.g.
{code:java}
@Entity
public class Entity {
@Id
private String id;
@ManyToOne(fetch=FetchType.LAZY)
private OtherEntity primaryOtherEntity;
@OneToMany(mappedBy=entity, fetch=FetchType.LAZY)
private ListOtherEntity OtherEntities;
// ... getter and setter
}
@Entity
public class OtherEntity {
@Id
private String id;
@ManyToOne(fetch=FetchType.LAZY)
private Entity entity;
// ... getter and setter
}
{code}
http://localhost:8080/Example.svc/Entity?$expand=OtherEntityDetails%2cOtherEntityDetails1
{code}
16:31:20,579 ERROR [stderr] (default task-26) java.lang.ClassCastException:
com.example.cloud.entities.OtherEntity_$$_jvst6ce_d6 cannot be cast to
java.util.Collection
16:31:20,579 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.jpa.processor.core.callback.JPAExpandCallBack.retrieveFeedResult(JPAExpandCallBack.java:148)
16:31:20,579 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.core.ep.producer.AtomEntryEntityProducer.appendInlineFeed(AtomEntryEntityProducer.java:275)
16:31:20,579 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.core.ep.producer.AtomEntryEntityProducer.appendAtomNavigationLink(AtomEntryEntityProducer.java:241)
16:31:20,579 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.core.ep.producer.AtomEntryEntityProducer.appendAtomNavigationLinks(AtomEntryEntityProducer.java:222)
16:31:20,580 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.core.ep.producer.AtomEntryEntityProducer.append(AtomEntryEntityProducer.java:126)
16:31:20,580 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.core.ep.AtomEntityProvider.writeEntry(AtomEntityProvider.java:174)
16:31:20,580 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.core.ep.ProviderFacadeImpl.writeEntry(ProviderFacadeImpl.java:128)
16:31:20,580 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.api.ep.EntityProvider.writeEntry(EntityProvider.java:576)
16:31:20,580 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.jpa.processor.core.ODataJPAResponseBuilderDefault.build(ODataJPAResponseBuilderDefault.java:167)
16:31:20,580 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.jpa.processor.core.ODataJPAProcessorDefault.readEntity(ODataJPAProcessorDefault.java:82)
16:31:20,580 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.core.Dispatcher.dispatch(Dispatcher.java:87)
16:31:20,580 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.core.ODataRequestHandler.handle(ODataRequestHandler.java:129)
16:31:20,580 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.core.rest.ODataSubLocator.handle(ODataSubLocator.java:167)
16:31:20,581 ERROR [stderr] (default task-26) at
org.apache.olingo.odata2.core.rest.ODataSubLocator.handleGet(ODataSubLocator.java:58)
16:31:20,581 ERROR [stderr] (default task-26) at
sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source)
16:31:20,581 ERROR [stderr] (default task-26) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
16:31:20,581 ERROR [stderr]
[jira] [Updated] (OLINGO-719) JPA - Complex Type not supported in $orderby expression
[ https://issues.apache.org/jira/browse/OLINGO-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-719: --- Affects Version/s: V2 2.0.4 JPA - Complex Type not supported in $orderby expression --- Key: OLINGO-719 URL: https://issues.apache.org/jira/browse/OLINGO-719 Project: Olingo Issue Type: Bug Components: odata2-jpa Affects Versions: V2 2.0.4 Reporter: Chandan V.A An exception is thrown when complex type is used in $orderby expression -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-719) JPA - Complex Type not supported in $orderby expression
[ https://issues.apache.org/jira/browse/OLINGO-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-719: --- Component/s: odata2-jpa JPA - Complex Type not supported in $orderby expression --- Key: OLINGO-719 URL: https://issues.apache.org/jira/browse/OLINGO-719 Project: Olingo Issue Type: Bug Components: odata2-jpa Affects Versions: V2 2.0.4 Reporter: Chandan V.A An exception is thrown when complex type is used in $orderby expression -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OLINGO-719) JPA - Complex Type not supported in $orderby expression
Chandan V.A created OLINGO-719: -- Summary: JPA - Complex Type not supported in $orderby expression Key: OLINGO-719 URL: https://issues.apache.org/jira/browse/OLINGO-719 Project: Olingo Issue Type: Bug Reporter: Chandan V.A An exception is thrown when complex type is used in $orderby expression -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-683) Unable to query an entity using an int id
[
https://issues.apache.org/jira/browse/OLINGO-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A resolved OLINGO-683.
Resolution: Fixed
Fix Version/s: V2 2.0.5
Unable to query an entity using an int id
-
Key: OLINGO-683
URL: https://issues.apache.org/jira/browse/OLINGO-683
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.3
Reporter: arathi m
Assignee: Chandan V.A
Fix For: V2 2.0.5
I have a MySQL table with an int primary key. I exposed my database table
using an Odata service using Olingo-odata2 JPA processor. When I query my
entity set using this URL:
http://host/emplist-web/emplist.svc/Customers(1)
I get Requested Resource not found exception. But the record exists with
id=1.
I debugged code and found that the JPQL generated is Select E1.Customer from
Customers E1 where E1.id=1L. But since my id is an int, the JPQL should be
Select E1.Customer from Customers E1 where E1.id=1.
I further debugged and the error is in evaluateComparingExpression of
org.apache.olingo.odata2.jpa.processor.core.ODataExpressionParser
evaluateComparingExpression method.
This code:
else if
(EdmSimpleTypeKind.Int64.getEdmSimpleTypeInstance().isCompatible(edmSimpleType))
{
uriLiteral = uriLiteral + JPQLStatement.DELIMITER.LONG; //$NON-NLS-1$
}
adds the erroneous JPQL I mentioned earlier. The fix would be to replace
above with this
else
if(EdmSimpleTypeKind.Int32.getEdmSimpleTypeInstance().equals(edmSimpleType))
{
uriLiteral = uriLiteral;
}
else if
(EdmSimpleTypeKind.Int64.getEdmSimpleTypeInstance().isCompatible(edmSimpleType))
{
uriLiteral = uriLiteral + JPQLStatement.DELIMITER.LONG; //$NON-NLS-1$
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OLINGO-670) Olingo JPA Processor EntityManager not closed
[ https://issues.apache.org/jira/browse/OLINGO-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A resolved OLINGO-670. Resolution: Fixed Fix Version/s: V2 2.0.5 Issue is fixed with commit = http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/2e26075a Olingo JPA Processor EntityManager not closed - Key: OLINGO-670 URL: https://issues.apache.org/jira/browse/OLINGO-670 Project: Olingo Issue Type: Bug Components: odata2-jpa Affects Versions: V2 2.0.4 Reporter: Chandan V.A Assignee: Chandan V.A Fix For: V2 2.0.5 The EntityManager instance is not closed and this causes resource leaks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OLINGO-683) Unable to query an entity using an int id
[
https://issues.apache.org/jira/browse/OLINGO-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A reassigned OLINGO-683:
--
Assignee: Chandan V.A
Unable to query an entity using an int id
-
Key: OLINGO-683
URL: https://issues.apache.org/jira/browse/OLINGO-683
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.3
Reporter: arathi m
Assignee: Chandan V.A
I have a MySQL table with an int primary key. I exposed my database table
using an Odata service using Olingo-odata2 JPA processor. When I query my
entity set using this URL:
http://host/emplist-web/emplist.svc/Customers(1)
I get Requested Resource not found exception. But the record exists with
id=1.
I debugged code and found that the JPQL generated is Select E1.Customer from
Customers E1 where E1.id=1L. But since my id is an int, the JPQL should be
Select E1.Customer from Customers E1 where E1.id=1.
I further debugged and the error is in evaluateComparingExpression of
org.apache.olingo.odata2.jpa.processor.core.ODataExpressionParser
evaluateComparingExpression method.
This code:
else if
(EdmSimpleTypeKind.Int64.getEdmSimpleTypeInstance().isCompatible(edmSimpleType))
{
uriLiteral = uriLiteral + JPQLStatement.DELIMITER.LONG; //$NON-NLS-1$
}
adds the erroneous JPQL I mentioned earlier. The fix would be to replace
above with this
else
if(EdmSimpleTypeKind.Int32.getEdmSimpleTypeInstance().equals(edmSimpleType))
{
uriLiteral = uriLiteral;
}
else if
(EdmSimpleTypeKind.Int64.getEdmSimpleTypeInstance().isCompatible(edmSimpleType))
{
uriLiteral = uriLiteral + JPQLStatement.DELIMITER.LONG; //$NON-NLS-1$
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OLINGO-670) Olingo JPA Processor EntityManager not closed
Chandan V.A created OLINGO-670: -- Summary: Olingo JPA Processor EntityManager not closed Key: OLINGO-670 URL: https://issues.apache.org/jira/browse/OLINGO-670 Project: Olingo Issue Type: Bug Components: odata2-jpa Affects Versions: V2 2.0.4 Reporter: Chandan V.A Assignee: Chandan V.A The EntityManager instance is not closed and this causes resource leaks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OLINGO-644) JPA Processor loose order by mutliple sort criteria
[ https://issues.apache.org/jira/browse/OLINGO-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A reassigned OLINGO-644: -- Assignee: Chandan V.A JPA Processor loose order by mutliple sort criteria --- Key: OLINGO-644 URL: https://issues.apache.org/jira/browse/OLINGO-644 Project: Olingo Issue Type: Bug Components: odata2-jpa Affects Versions: V2 2.0.3 Reporter: Christian Wilhelm Assignee: Chandan V.A Hi Colleagues, We want to sort a table regarding 3 different columns. The sort priority is of course important, but it does not work as expected. First Example „Read Raw Materials“: Within the Chrome-Debugger you can see that the GET is called in the right way: On the other hand the SQL Tracing on the Server looks like this: SELECT UUID, ASSIGNEDCR, COMPLETEDCR, MISSING_REQ_DATA, NOT_COMPLIANT_REQS, PRIORITY, RAW_MATERIAL_ID, RAWMATERIAL_NAME, RESPONSIBLE_USER_GROUP_UUID, USED_IN_PRODUCTS FROM MONITORRAWMATERIAL ORDER BY PRIORITY DESC, USED_IN_PRODUCTS DESC, RAWMATERIAL_NAME Order PrioCall from Frontend (GET)SQL Call in JPA 1.RawMaterialName PRIORITY 2.UsedInProducts USED_IN_PRODUCTS 3.PriorityRAWMATERIAL_NAME A Second Example shows the following Order Prio: Summary: Order PrioCall from Frontend (GET)SQL Call in JPA 1.ProductName PRODUCT_NAME 2.InworkCRPRIORITY 3.PriorityINWORKCR Found Debugging Information: Debugging the OData-Source provides following information for us: • In the Class ODataExpressionParser and function parseToJPAOrderByExpression() the (still sorted) orderByExpression is stored in the orderByMap. • In the Class JPQLSelectStatementBuilder and function createJPQLQuery() the hash map is read by iterator (= unsorted). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-644) JPA Processor loose order by mutliple sort criteria
[ https://issues.apache.org/jira/browse/OLINGO-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526277#comment-14526277 ] Chandan V.A commented on OLINGO-644: Hello Christian, The issue is fixed with commit - http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/bd4e7efd. Please check. Thanks Kind Regards Chandan JPA Processor loose order by mutliple sort criteria --- Key: OLINGO-644 URL: https://issues.apache.org/jira/browse/OLINGO-644 Project: Olingo Issue Type: Bug Components: odata2-jpa Affects Versions: V2 2.0.3 Reporter: Christian Wilhelm Assignee: Chandan V.A Fix For: V2 2.0.4 Hi Colleagues, We want to sort a table regarding 3 different columns. The sort priority is of course important, but it does not work as expected. First Example „Read Raw Materials“: Within the Chrome-Debugger you can see that the GET is called in the right way: On the other hand the SQL Tracing on the Server looks like this: SELECT UUID, ASSIGNEDCR, COMPLETEDCR, MISSING_REQ_DATA, NOT_COMPLIANT_REQS, PRIORITY, RAW_MATERIAL_ID, RAWMATERIAL_NAME, RESPONSIBLE_USER_GROUP_UUID, USED_IN_PRODUCTS FROM MONITORRAWMATERIAL ORDER BY PRIORITY DESC, USED_IN_PRODUCTS DESC, RAWMATERIAL_NAME Order PrioCall from Frontend (GET)SQL Call in JPA 1.RawMaterialName PRIORITY 2.UsedInProducts USED_IN_PRODUCTS 3.PriorityRAWMATERIAL_NAME A Second Example shows the following Order Prio: Summary: Order PrioCall from Frontend (GET)SQL Call in JPA 1.ProductName PRODUCT_NAME 2.InworkCRPRIORITY 3.PriorityINWORKCR Found Debugging Information: Debugging the OData-Source provides following information for us: • In the Class ODataExpressionParser and function parseToJPAOrderByExpression() the (still sorted) orderByExpression is stored in the orderByMap. • In the Class JPQLSelectStatementBuilder and function createJPQLQuery() the hash map is read by iterator (= unsorted). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-644) JPA Processor loose order by mutliple sort criteria
[ https://issues.apache.org/jira/browse/OLINGO-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A resolved OLINGO-644. Resolution: Fixed JPA Processor loose order by mutliple sort criteria --- Key: OLINGO-644 URL: https://issues.apache.org/jira/browse/OLINGO-644 Project: Olingo Issue Type: Bug Components: odata2-jpa Affects Versions: V2 2.0.3 Reporter: Christian Wilhelm Assignee: Chandan V.A Hi Colleagues, We want to sort a table regarding 3 different columns. The sort priority is of course important, but it does not work as expected. First Example „Read Raw Materials“: Within the Chrome-Debugger you can see that the GET is called in the right way: On the other hand the SQL Tracing on the Server looks like this: SELECT UUID, ASSIGNEDCR, COMPLETEDCR, MISSING_REQ_DATA, NOT_COMPLIANT_REQS, PRIORITY, RAW_MATERIAL_ID, RAWMATERIAL_NAME, RESPONSIBLE_USER_GROUP_UUID, USED_IN_PRODUCTS FROM MONITORRAWMATERIAL ORDER BY PRIORITY DESC, USED_IN_PRODUCTS DESC, RAWMATERIAL_NAME Order PrioCall from Frontend (GET)SQL Call in JPA 1.RawMaterialName PRIORITY 2.UsedInProducts USED_IN_PRODUCTS 3.PriorityRAWMATERIAL_NAME A Second Example shows the following Order Prio: Summary: Order PrioCall from Frontend (GET)SQL Call in JPA 1.ProductName PRODUCT_NAME 2.InworkCRPRIORITY 3.PriorityINWORKCR Found Debugging Information: Debugging the OData-Source provides following information for us: • In the Class ODataExpressionParser and function parseToJPAOrderByExpression() the (still sorted) orderByExpression is stored in the orderByMap. • In the Class JPQLSelectStatementBuilder and function createJPQLQuery() the hash map is read by iterator (= unsorted). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-647) JPA supprt nested method calls within filter statements
[ https://issues.apache.org/jira/browse/OLINGO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A resolved OLINGO-647. Resolution: Fixed JPA supprt nested method calls within filter statements --- Key: OLINGO-647 URL: https://issues.apache.org/jira/browse/OLINGO-647 Project: Olingo Issue Type: New Feature Components: odata2-jpa Affects Versions: V2 2.0.3 Reporter: Christian Amend Assignee: Chandan V.A Fix For: V2 2.0.4 Support someting like $filter=startswith(substingOf(...), ID) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OLINGO-618) POC: odata-jpa-ref-persistence
Chandan V.A created OLINGO-618: -- Summary: POC: odata-jpa-ref-persistence Key: OLINGO-618 URL: https://issues.apache.org/jira/browse/OLINGO-618 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Affects Versions: (JPA) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A Create a JPA Model for the reference scenario. The model shall be based on Sales Order Processing as done in OData JPA Processor V2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-552) POC: Module Design for ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A resolved OLINGO-552. Resolution: Fixed Fix Version/s: (JPA) V4 4.0.0-beta-01 POC: Module Design for ODataV4 JPA Processor Key: OLINGO-552 URL: https://issues.apache.org/jira/browse/OLINGO-552 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Affects Versions: (JPA) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A Fix For: (JPA) V4 4.0.0-beta-01 Design Java modules for OData V4 JPA Processor as an Extension to the Olingo OData V4 Server component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OLINGO-619) POC: Module odata-jpa-api
Chandan V.A created OLINGO-619: -- Summary: POC: Module odata-jpa-api Key: OLINGO-619 URL: https://issues.apache.org/jira/browse/OLINGO-619 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Affects Versions: (JPA) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A Fix For: (JPA) V4 4.0.0-beta-01 Proposal - The module odata-jpa-api shall contain 1) ODataJPAServlet for handling OData request and response in the context of JPA processor 2) ODataJPAEdmProvider for producing OData V4 complaint metadata from JPA Entity Model 3) ODataJPAProcessor a root processor for handing OData V4 complaint requests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-604) Injected Entity Managers are closed after fetching query results
[
https://issues.apache.org/jira/browse/OLINGO-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A updated OLINGO-604:
---
Component/s: odata2-jpa
Injected Entity Managers are closed after fetching query results
Key: OLINGO-604
URL: https://issues.apache.org/jira/browse/OLINGO-604
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.4
Reporter: Chandan V.A
Assignee: Chandan V.A
Priority: Minor
There is an issue with the way the result list is accessed in JPAProcessor
method: private Object readEntity(final Object uriParserResultView, final
JPQLContextType contextType)
Currently (Olingo 2.03) accesses the Resultlist by following code snippet:
…
query = em.createQuery(selectJPQLStatement.toString());
if (!query.getResultList().isEmpty()) {
selectedObject = query.getResultList().get(0);
…
Because an injected entityprocessor (via proxy) from the Spring Framework, on
the first access to query.getResultList() closes the entitymanager after the
query transaction is done.
Since the object is accessed in a separate call the entitymanager is closed
and therefore we get an error “Attempting to execute an operation on a closed
EntityManager.
The solution is ..
By assigning the ResultList to a List, the issue is solved:
…
query = em.createQuery(selectJPQLStatement.toString());
final List resultList = query.getResultList();
if (!resultList.isEmpty())
{
selectedObject = resultList.get(0);
}
…
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OLINGO-604) Injected Entity Managers are closed after fetching query results
Chandan V.A created OLINGO-604:
--
Summary: Injected Entity Managers are closed after fetching query
results
Key: OLINGO-604
URL: https://issues.apache.org/jira/browse/OLINGO-604
Project: Olingo
Issue Type: Bug
Affects Versions: V2 2.0.4
Reporter: Chandan V.A
Assignee: Chandan V.A
Priority: Minor
There is an issue with the way the result list is accessed in JPAProcessor
method: private Object readEntity(final Object uriParserResultView, final
JPQLContextType contextType)
Currently (Olingo 2.03) accesses the Resultlist by following code snippet:
…
query = em.createQuery(selectJPQLStatement.toString());
if (!query.getResultList().isEmpty()) {
selectedObject = query.getResultList().get(0);
…
Because an injected entityprocessor (via proxy) from the Spring Framework, on
the first access to query.getResultList() closes the entitymanager after the
query transaction is done.
Since the object is accessed in a separate call the entitymanager is closed and
therefore we get an error “Attempting to execute an operation on a closed
EntityManager.
The solution is ..
By assigning the ResultList to a List, the issue is solved:
…
query = em.createQuery(selectJPQLStatement.toString());
final List resultList = query.getResultList();
if (!resultList.isEmpty())
{
selectedObject = resultList.get(0);
}
…
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OLINGO-604) Injected Entity Managers are closed after fetching query results
[
https://issues.apache.org/jira/browse/OLINGO-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A updated OLINGO-604:
---
Fix Version/s: V2 2.0.4
Injected Entity Managers are closed after fetching query results
Key: OLINGO-604
URL: https://issues.apache.org/jira/browse/OLINGO-604
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.4
Reporter: Chandan V.A
Assignee: Chandan V.A
Priority: Minor
Fix For: V2 2.0.4
There is an issue with the way the result list is accessed in JPAProcessor
method: private Object readEntity(final Object uriParserResultView, final
JPQLContextType contextType)
Currently (Olingo 2.03) accesses the Resultlist by following code snippet:
…
query = em.createQuery(selectJPQLStatement.toString());
if (!query.getResultList().isEmpty()) {
selectedObject = query.getResultList().get(0);
…
Because an injected entityprocessor (via proxy) from the Spring Framework, on
the first access to query.getResultList() closes the entitymanager after the
query transaction is done.
Since the object is accessed in a separate call the entitymanager is closed
and therefore we get an error “Attempting to execute an operation on a closed
EntityManager.
The solution is ..
By assigning the ResultList to a List, the issue is solved:
…
query = em.createQuery(selectJPQLStatement.toString());
final List resultList = query.getResultList();
if (!resultList.isEmpty())
{
selectedObject = resultList.get(0);
}
…
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OLINGO-604) Injected Entity Managers are closed after fetching query results
[
https://issues.apache.org/jira/browse/OLINGO-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A resolved OLINGO-604.
Resolution: Fixed
Injected Entity Managers are closed after fetching query results
Key: OLINGO-604
URL: https://issues.apache.org/jira/browse/OLINGO-604
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.4
Reporter: Chandan V.A
Assignee: Chandan V.A
Priority: Minor
There is an issue with the way the result list is accessed in JPAProcessor
method: private Object readEntity(final Object uriParserResultView, final
JPQLContextType contextType)
Currently (Olingo 2.03) accesses the Resultlist by following code snippet:
…
query = em.createQuery(selectJPQLStatement.toString());
if (!query.getResultList().isEmpty()) {
selectedObject = query.getResultList().get(0);
…
Because an injected entityprocessor (via proxy) from the Spring Framework, on
the first access to query.getResultList() closes the entitymanager after the
query transaction is done.
Since the object is accessed in a separate call the entitymanager is closed
and therefore we get an error “Attempting to execute an operation on a closed
EntityManager.
The solution is ..
By assigning the ResultList to a List, the issue is solved:
…
query = em.createQuery(selectJPQLStatement.toString());
final List resultList = query.getResultList();
if (!resultList.isEmpty())
{
selectedObject = resultList.get(0);
}
…
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OLINGO-604) Injected Entity Managers are closed after fetching query results
[
https://issues.apache.org/jira/browse/OLINGO-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381603#comment-14381603
]
Chandan V.A commented on OLINGO-604:
Fixed with -
http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/763755f1
Injected Entity Managers are closed after fetching query results
Key: OLINGO-604
URL: https://issues.apache.org/jira/browse/OLINGO-604
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.4
Reporter: Chandan V.A
Assignee: Chandan V.A
Priority: Minor
Fix For: V2 2.0.4
There is an issue with the way the result list is accessed in JPAProcessor
method: private Object readEntity(final Object uriParserResultView, final
JPQLContextType contextType)
Currently (Olingo 2.03) accesses the Resultlist by following code snippet:
…
query = em.createQuery(selectJPQLStatement.toString());
if (!query.getResultList().isEmpty()) {
selectedObject = query.getResultList().get(0);
…
Because an injected entityprocessor (via proxy) from the Spring Framework, on
the first access to query.getResultList() closes the entitymanager after the
query transaction is done.
Since the object is accessed in a separate call the entitymanager is closed
and therefore we get an error “Attempting to execute an operation on a closed
EntityManager.
The solution is ..
By assigning the ResultList to a List, the issue is solved:
…
query = em.createQuery(selectJPQLStatement.toString());
final List resultList = query.getResultList();
if (!resultList.isEmpty())
{
selectedObject = resultList.get(0);
}
…
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OLINGO-599) Improvement in error messages.
[ https://issues.apache.org/jira/browse/OLINGO-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14371023#comment-14371023 ] Chandan V.A commented on OLINGO-599: Hi Sachin, are you invoking the method setDetailErrors(boolean ) in your service factory with value true. This setting in your service factory will not supress detail errors (this includes the JPQL statement or the JPA provider exception messages) and will show all errors thrown from the library. Regards Chandan Improvement in error messages. -- Key: OLINGO-599 URL: https://issues.apache.org/jira/browse/OLINGO-599 Project: Olingo Issue Type: Improvement Components: odata2-jpa Affects Versions: V2 2.0.2, V2 2.0.3 Environment: Olingo JPA used in Integration Gateway Reporter: Sachin C Fix For: V2 2.0.4 Original Estimate: 336h Remaining Estimate: 336h Hi, This is regarding the error messages thrown from the Olingo JPA side when there is a failure due a wrong payload or something like that. For now the error messages are all of the form OData JPA METHOD syntax is not correct. Where METHOD can be CREATE,DELETE,UPDATE etc. What we want is a more clear error as to what went wrong such as So and so constraint is violated or any statement which is more specific regarding the cause of the error. Thanks, Sachin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-586) Filter substringof causes NullPointerException
[ https://issues.apache.org/jira/browse/OLINGO-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A resolved OLINGO-586. Resolution: Fixed Fix Version/s: V2 2.0.4 Hi, The issue is fixed with the commit - http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/345b33dd Regards Chandan Filter substringof causes NullPointerException -- Key: OLINGO-586 URL: https://issues.apache.org/jira/browse/OLINGO-586 Project: Olingo Issue Type: Bug Components: odata2-jpa Affects Versions: V2 2.0.3 Reporter: Benedikt Lesch Assignee: Chandan V.A Priority: Minor Labels: easyfix Fix For: V2 2.0.4 Original Estimate: 0.5h Remaining Estimate: 0.5h The expression methodFlag.get() == 1 in line 220 of org.apache.olingo.odata2.jpa.processor.core.ODataExpressionParser causes a NullPointerExcpetion. methodFlag.get() is null at this point, the comparison to the int value causes an implicit call of methodFlag.get().intValue which causes the exception. Edit: only occurs when eq true is missing after filter -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-580) Support JTA based transactions in JPA processor
[ https://issues.apache.org/jira/browse/OLINGO-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14358324#comment-14358324 ] Chandan V.A commented on OLINGO-580: Changes part of commit - http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/313bbbab http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/83313c1c Support JTA based transactions in JPA processor --- Key: OLINGO-580 URL: https://issues.apache.org/jira/browse/OLINGO-580 Project: Olingo Issue Type: New Feature Components: odata2-jpa Affects Versions: V2 2.0.3 Reporter: Chandan V.A Assignee: Chandan V.A Fix For: V2 2.0.4 Attachments: OLINGO-580.diff Olingo V2 JPA processor supports RESOURCE_LOCAL based transaction. Enhance the processor to support JTA based transactions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[ https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14338224#comment-14338224 ] Chandan V.A commented on OLINGO-527: Hello Karuna, If you set the page size olingo will generare the next link. Regards Chandan Is there any possible ay to reduce build response time of JPA query Key: OLINGO-527 URL: https://issues.apache.org/jira/browse/OLINGO-527 Project: Olingo Issue Type: Question Components: odata2-core, odata2-jpa Reporter: Karuna Joshi Assignee: Chandan V.A We have a very large data base and we are exposing the data using olingo restful web service. when I compare, time taken to execute the same query via jdbc connection and time taken by olingo, there is a significant difference. Time taken by Olingo is very large. Time taken to process JPA query + Time taken to build response is the total time taken by olingo. We try to tune the JPA queries using Query hints, but still build response time is also very large. I have a question : Is there any way we can reduce the time taken to build the response ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-579) Not able to change attribute names for JPA generated foreign keys
[ https://issues.apache.org/jira/browse/OLINGO-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A resolved OLINGO-579. Resolution: Not a Problem Fix Version/s: V2 2.0.2 Not able to change attribute names for JPA generated foreign keys - Key: OLINGO-579 URL: https://issues.apache.org/jira/browse/OLINGO-579 Project: Olingo Issue Type: Bug Components: odata2-jpa Reporter: Adith Shenoy Assignee: Chandan V.A Fix For: V2 2.0.2 Hi [~chandan.v.a] Not able to change attribute names for JPA generated foreign keys which comes as FK_PROPERTYNAME in the metadata -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-579) Not able to change attribute names for JPA generated foreign keys
[ https://issues.apache.org/jira/browse/OLINGO-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-579: --- Component/s: odata2-jpa Not able to change attribute names for JPA generated foreign keys - Key: OLINGO-579 URL: https://issues.apache.org/jira/browse/OLINGO-579 Project: Olingo Issue Type: Bug Components: odata2-jpa Reporter: Adith Shenoy Assignee: Chandan V.A Hi [~chandan.v.a] Not able to change attribute names for JPA generated foreign keys which comes as FK_PROPERTYNAME in the metadata -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OLINGO-579) Not able to change attribute names for JPA generated foreign keys
[ https://issues.apache.org/jira/browse/OLINGO-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A reassigned OLINGO-579: -- Assignee: Chandan V.A Not able to change attribute names for JPA generated foreign keys - Key: OLINGO-579 URL: https://issues.apache.org/jira/browse/OLINGO-579 Project: Olingo Issue Type: Bug Reporter: Adith Shenoy Assignee: Chandan V.A Hi [~chandan.v.a] Not able to change attribute names for JPA generated foreign keys which comes as FK_PROPERTYNAME in the metadata -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-549) POC: ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14323704#comment-14323704 ] Chandan V.A commented on OLINGO-549: Hello Karuna, JPA extension for OData V4 is planned to be done in a phased manner. Tentative timeline with minimal capability can be seen sometime before May 2015 end. Regards Chandan POC: ODataV4 JPA Processor -- Key: OLINGO-549 URL: https://issues.apache.org/jira/browse/OLINGO-549 Project: Olingo Issue Type: New Feature Components: odata4-JPA Affects Versions: (JPA) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A A proof of Concept for transforming JPA models into OData V4 compliant EDM models and supporting OData V4 protocol compliant operations into JPA 2.0/2.1 specific operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[ https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A reassigned OLINGO-527: -- Assignee: Chandan V.A Is there any possible ay to reduce build response time of JPA query Key: OLINGO-527 URL: https://issues.apache.org/jira/browse/OLINGO-527 Project: Olingo Issue Type: Question Components: odata2-core, odata2-jpa Reporter: Karuna Joshi Assignee: Chandan V.A We have a very large data base and we are exposing the data using olingo restful web service. when I compare, time taken to execute the same query via jdbc connection and time taken by olingo, there is a significant difference. Time taken by Olingo is very large. Time taken to process JPA query + Time taken to build response is the total time taken by olingo. We try to tune the JPA queries using Query hints, but still build response time is also very large. I have a question : Is there any way we can reduce the time taken to build the response ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[ https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-527: --- Component/s: odata2-jpa odata2-core Is there any possible ay to reduce build response time of JPA query Key: OLINGO-527 URL: https://issues.apache.org/jira/browse/OLINGO-527 Project: Olingo Issue Type: Question Components: odata2-core, odata2-jpa Reporter: Karuna Joshi Assignee: Chandan V.A We have a very large data base and we are exposing the data using olingo restful web service. when I compare, time taken to execute the same query via jdbc connection and time taken by olingo, there is a significant difference. Time taken by Olingo is very large. Time taken to process JPA query + Time taken to build response is the total time taken by olingo. We try to tune the JPA queries using Query hints, but still build response time is also very large. I have a question : Is there any way we can reduce the time taken to build the response ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[ https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14323770#comment-14323770 ] Chandan V.A commented on OLINGO-527: Hello Karuna, Did you try with JSON payload format. JSON payload is lighter and compact. Please check whether you face significant performance issue with JSON format as well. Regards Chandan Is there any possible ay to reduce build response time of JPA query Key: OLINGO-527 URL: https://issues.apache.org/jira/browse/OLINGO-527 Project: Olingo Issue Type: Question Reporter: Karuna Joshi We have a very large data base and we are exposing the data using olingo restful web service. when I compare, time taken to execute the same query via jdbc connection and time taken by olingo, there is a significant difference. Time taken by Olingo is very large. Time taken to process JPA query + Time taken to build response is the total time taken by olingo. We try to tune the JPA queries using Query hints, but still build response time is also very large. I have a question : Is there any way we can reduce the time taken to build the response ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-378) PUT operation on navigation link
[
https://issues.apache.org/jira/browse/OLINGO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A updated OLINGO-378:
---
Assignee: Christian Amend (was: Chandan V.A)
PUT operation on navigation link
Key: OLINGO-378
URL: https://issues.apache.org/jira/browse/OLINGO-378
Project: Olingo
Issue Type: New Feature
Components: odata2-jpa
Affects Versions: V2 2.0.0
Reporter: Chitresh Chauhan
Assignee: Christian Amend
Priority: Minor
Hi,
1. do a read operation on a sales order item for a sales order header
and use it as the request body for update operation. Make the required
changes in the request body.
2. Do a PUT operation with the request body as created above
Describe the problem
Sent PUT to update the following child entity as requested:
https://localhost:8083/gateway/odata/SAP/ESPMSERVICE;v=1/SalesOrderHeade
rs('18')/SalesOrderItemDetails(ItemNumber=1801,SalesOrderId='18')
Expected Result:
The sales order line item shall get updated under the sales order
header. User shall get the http response code as 204.
Instead returned the following error:
400 BAD REQUEST
error
xmlns=http://schemas.microsoft.com/ado/2007/08/dataservices/metadata;
code /
message xml:lang=en-USThe request is not supported by the
processor./message
/error .
Is it possible to get this supported.
Thanks.
BR,
Chitresh
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OLINGO-378) PUT operation on navigation link
[
https://issues.apache.org/jira/browse/OLINGO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14323779#comment-14323779
]
Chandan V.A commented on OLINGO-378:
Hello Christian,
The org.apache.olingo.odata2.core.Dispatcher at Line 151 throws this error,
when we try to do an HTTP PUT operation on 1..N navigation property.
Can you please check.
Thanks
Kind regards
Chandan
PUT operation on navigation link
Key: OLINGO-378
URL: https://issues.apache.org/jira/browse/OLINGO-378
Project: Olingo
Issue Type: New Feature
Components: odata2-jpa
Affects Versions: V2 2.0.0
Reporter: Chitresh Chauhan
Assignee: Christian Amend
Priority: Minor
Hi,
1. do a read operation on a sales order item for a sales order header
and use it as the request body for update operation. Make the required
changes in the request body.
2. Do a PUT operation with the request body as created above
Describe the problem
Sent PUT to update the following child entity as requested:
https://localhost:8083/gateway/odata/SAP/ESPMSERVICE;v=1/SalesOrderHeade
rs('18')/SalesOrderItemDetails(ItemNumber=1801,SalesOrderId='18')
Expected Result:
The sales order line item shall get updated under the sales order
header. User shall get the http response code as 204.
Instead returned the following error:
400 BAD REQUEST
error
xmlns=http://schemas.microsoft.com/ado/2007/08/dataservices/metadata;
code /
message xml:lang=en-USThe request is not supported by the
processor./message
/error .
Is it possible to get this supported.
Thanks.
BR,
Chitresh
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OLINGO-550) POC: Create Feature Branch for ODataV4 - JPA Processor
Chandan V.A created OLINGO-550: -- Summary: POC: Create Feature Branch for ODataV4 - JPA Processor Key: OLINGO-550 URL: https://issues.apache.org/jira/browse/OLINGO-550 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Reporter: Chandan V.A Assignee: Chandan V.A -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OLINGO-549) POC: ODataV4 JPA Processor
Chandan V.A created OLINGO-549: -- Summary: POC: ODataV4 JPA Processor Key: OLINGO-549 URL: https://issues.apache.org/jira/browse/OLINGO-549 Project: Olingo Issue Type: New Feature Components: odata4-JPA Reporter: Chandan V.A Assignee: Chandan V.A A proof of Concept for transforming JPA models into OData V4 compliant EDM models and supporting OData V4 protocol compliant operations into JPA 2.0/2.1 specific operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OLINGO-549) POC: ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A updated OLINGO-549: --- Affects Version/s: (JPA) V4 4.0.0-beta-01 POC: ODataV4 JPA Processor -- Key: OLINGO-549 URL: https://issues.apache.org/jira/browse/OLINGO-549 Project: Olingo Issue Type: New Feature Components: odata4-JPA Affects Versions: (JPA) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A A proof of Concept for transforming JPA models into OData V4 compliant EDM models and supporting OData V4 protocol compliant operations into JPA 2.0/2.1 specific operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OLINGO-550) POC: Create Feature Branch for ODataV4 - JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301372#comment-14301372 ] Chandan V.A edited comment on OLINGO-550 at 2/2/15 3:19 PM: Remote Branch - https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=shortlog;h=refs/heads/OLINGO-549-ODataV4-JPA created for tracking ODataV4 - JPA Processor Development. The branch shall be merged with master branch once a stable version is reached. was (Author: chandan.v.a): Remote Branch - refs/heads/OLINGO-549-ODataV4-JPA created for tracking ODataV4 - JPA Processor Development. The branch shall be merged with master branch once a stable version is reached. POC: Create Feature Branch for ODataV4 - JPA Processor -- Key: OLINGO-550 URL: https://issues.apache.org/jira/browse/OLINGO-550 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Reporter: Chandan V.A Assignee: Chandan V.A -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OLINGO-552) POC: Module Design for ODataV4 JPA Processor
Chandan V.A created OLINGO-552: -- Summary: POC: Module Design for ODataV4 JPA Processor Key: OLINGO-552 URL: https://issues.apache.org/jira/browse/OLINGO-552 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Affects Versions: (JPA) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A Design Java modules for OData V4 JPA Processor as an Extension to the Olingo OData V4 Server component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-550) POC: Create Feature Branch for ODataV4 - JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301372#comment-14301372 ] Chandan V.A commented on OLINGO-550: Remote Branch - refs/heads/OLINGO-549-ODataV4-JPA created for tracking ODataV4 - JPA Processor Development. The branch shall be merged with master branch once a stable version is reached. POC: Create Feature Branch for ODataV4 - JPA Processor -- Key: OLINGO-550 URL: https://issues.apache.org/jira/browse/OLINGO-550 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Reporter: Chandan V.A Assignee: Chandan V.A -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OLINGO-550) POC: Create Feature Branch for ODataV4 - JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A closed OLINGO-550. -- POC: Create Feature Branch for ODataV4 - JPA Processor -- Key: OLINGO-550 URL: https://issues.apache.org/jira/browse/OLINGO-550 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Reporter: Chandan V.A Assignee: Chandan V.A Fix For: (JPA) V4 4.0.0-beta-01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OLINGO-550) POC: Create Feature Branch for ODataV4 - JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan V.A resolved OLINGO-550. Resolution: Fixed Fix Version/s: (JPA) V4 4.0.0-beta-01 POC: Create Feature Branch for ODataV4 - JPA Processor -- Key: OLINGO-550 URL: https://issues.apache.org/jira/browse/OLINGO-550 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Reporter: Chandan V.A Assignee: Chandan V.A Fix For: (JPA) V4 4.0.0-beta-01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-552) POC: Module Design for ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301601#comment-14301601 ] Chandan V.A commented on OLINGO-552: Hi Ramesh, It is just a start to come up with a initial version of OData V4 JPA processor. Once it matures to be released as an independent module we can discuss and bring in a new sub-project notion like the one we have for java script and also can discuss on having a separate release cycles for processor. However the initial module proposal for OData V4.0 at - https://wiki.apache.org/Olingo/Olingo%20Module%20Proposal had JPA processor as an extension module to OData V4. This is the very reason why the modules are proposed to be structured like extension. Secondly, there is a need for an API module because 1) we can go ahead with implementing different JPA cores if needed to support JPA provider specific use cases. 2) The API project also will provide interfaces + abstract implementation which applications can implement or extend to suit their use cases - Example - JPQL Processing, Delta Token Handling, Error Call Backs, JPA Extensions and so on. Regards Chandan Thanks Kind regards Chandan POC: Module Design for ODataV4 JPA Processor Key: OLINGO-552 URL: https://issues.apache.org/jira/browse/OLINGO-552 Project: Olingo Issue Type: Sub-task Components: odata4-JPA Affects Versions: (JPA) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A Design Java modules for OData V4 JPA Processor as an Extension to the Olingo OData V4 Server component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
