[jira] [Resolved] (OLINGO-1228) JPA Parameterization issue
[ https://issues.apache.org/jira/browse/OLINGO-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana Rai resolved OLINGO-1228. - Resolution: Fixed > JPA Parameterization issue > --- > > Key: OLINGO-1228 > URL: https://issues.apache.org/jira/browse/OLINGO-1228 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Reporter: Archana Rai >Priority: Major > > Put request with two parameters failing for JPA > [http://localhost:8081/RFQ/Appointments(RequestForQuotationGuid='7f260ade-65e0-471a-b2ce-75e1b745bd54',AppointmentId=3)] > With the below exception: > java.lang.IllegalArgumentException:An exception occurred while > creating a query in EntityManager: > Exception Description: Error compiling the query [SELECT E1 FROM Appointment > E1 WHERE E1.requestForQuotationGuid LIKE ?1 ESCAPE '\' AND E1.appointmentId = > ?1], line 1, column 105: invalid multiple use of parameter [1] assuming > different parameter types [java.lang.String] and [java.lang.Integer] > Parameter 1 in SQL is also used for the second value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OLINGO-1228) JPA Parameterization issue
Archana Rai created OLINGO-1228: --- Summary: JPA Parameterization issue Key: OLINGO-1228 URL: https://issues.apache.org/jira/browse/OLINGO-1228 Project: Olingo Issue Type: Bug Components: odata2-jpa Reporter: Archana Rai Put request with two parameters failing for JPA [http://localhost:8081/RFQ/Appointments(RequestForQuotationGuid='7f260ade-65e0-471a-b2ce-75e1b745bd54',AppointmentId=3)] With the below exception: java.lang.IllegalArgumentException:An exception occurred while creating a query in EntityManager: Exception Description: Error compiling the query [SELECT E1 FROM Appointment E1 WHERE E1.requestForQuotationGuid LIKE ?1 ESCAPE '\' AND E1.appointmentId = ?1], line 1, column 105: invalid multiple use of parameter [1] assuming different parameter types [java.lang.String] and [java.lang.Integer] Parameter 1 in SQL is also used for the second value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1227) NoSuchMethodError exception in EdmBinary
[
https://issues.apache.org/jira/browse/OLINGO-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346766#comment-16346766
]
Christian Amend commented on OLINGO-1227:
-
Hi Daniel,
Apache Olingo requires the dependency Apache.commons.codec with version 1.6.
This is specified in the POM. Can you please check if either:
1. The dependency is not part of your classpath
2. The dependency is not part of your war file
3. There is another version of apache commons codec deployed? Maybe a
lower version that does not have the required method.
Best Regards,
Christian
> NoSuchMethodError exception in EdmBinary
>
>
> Key: OLINGO-1227
> URL: https://issues.apache.org/jira/browse/OLINGO-1227
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.10
>Reporter: Daniel Horvath
>Priority: Blocker
>
> Dear Colleagues,
> When we try to read an entity with binary property with Olingo we get the
> following exception:
>
> {code:java}
> Caused by: java.lang.NoSuchMethodError:
> org.apache.commons.codec.binary.Base64.isBase64(Ljava/lang/String;)Z
> at
> org.apache.olingo.odata2.core.edm.EdmBinary.validateLiteral(EdmBinary.java:60)
> at
> org.apache.olingo.odata2.core.edm.EdmBinary.internalValueOfString(EdmBinary.java:91)
> at
> org.apache.olingo.odata2.core.edm.AbstractSimpleType.valueOfString(AbstractSimpleType.java:91)
> at
> org.apache.olingo.odata2.core.ep.consumer.JsonPropertyConsumer.readSimpleProperty(JsonPropertyConsumer.java:236)
> at
> org.apache.olingo.odata2.core.ep.consumer.JsonPropertyConsumer.readPropertyValue(JsonPropertyConsumer.java:169)
> at
> org.apache.olingo.odata2.core.ep.consumer.JsonEntryConsumer.handleName(JsonEntryConsumer.java:172)
> at
> org.apache.olingo.odata2.core.ep.consumer.JsonEntryConsumer.readEntryContent(JsonEntryConsumer.java:130)
> at
> org.apache.olingo.odata2.core.ep.consumer.JsonEntryConsumer.readFeedEntry(JsonEntryConsumer.java:117)
> at
> org.apache.olingo.odata2.core.ep.consumer.JsonFeedConsumer.readArrayContent(JsonFeedConsumer.java:153)
> at
> org.apache.olingo.odata2.core.ep.consumer.JsonFeedConsumer.handleName(JsonFeedConsumer.java:122)
> at
> org.apache.olingo.odata2.core.ep.consumer.JsonFeedConsumer.readFeedContent(JsonFeedConsumer.java:111)
> at
> org.apache.olingo.odata2.core.ep.consumer.JsonFeedConsumer.readFeed(JsonFeedConsumer.java:96)
> at
> org.apache.olingo.odata2.core.ep.consumer.JsonFeedConsumer.readFeedStandalone(JsonFeedConsumer.java:63)
> at
> org.apache.olingo.odata2.core.ep.consumer.JsonEntityConsumer.readDeltaFeed(JsonEntityConsumer.java:95)
> at
> org.apache.olingo.odata2.core.ep.consumer.JsonEntityConsumer.readFeed(JsonEntityConsumer.java:81)
> at
> org.apache.olingo.odata2.core.ep.JsonEntityProvider.readFeed(JsonEntityProvider.java:309)
> at
> org.apache.olingo.odata2.core.ep.ProviderFacadeImpl.readFeed(ProviderFacadeImpl.java:166)
> at
> org.apache.olingo.odata2.api.ep.EntityProvider.readFeed(EntityProvider.java:708)
> {code}
> Best regards,
> Daniel
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OLINGO-1227) NoSuchMethodError exception in EdmBinary
Daniel Horvath created OLINGO-1227:
--
Summary: NoSuchMethodError exception in EdmBinary
Key: OLINGO-1227
URL: https://issues.apache.org/jira/browse/OLINGO-1227
Project: Olingo
Issue Type: Bug
Components: odata2-core
Affects Versions: V2 2.0.10
Reporter: Daniel Horvath
Dear Colleagues,
When we try to read an entity with binary property with Olingo we get the
following exception:
{code:java}
Caused by: java.lang.NoSuchMethodError:
org.apache.commons.codec.binary.Base64.isBase64(Ljava/lang/String;)Z
at
org.apache.olingo.odata2.core.edm.EdmBinary.validateLiteral(EdmBinary.java:60)
at
org.apache.olingo.odata2.core.edm.EdmBinary.internalValueOfString(EdmBinary.java:91)
at
org.apache.olingo.odata2.core.edm.AbstractSimpleType.valueOfString(AbstractSimpleType.java:91)
at
org.apache.olingo.odata2.core.ep.consumer.JsonPropertyConsumer.readSimpleProperty(JsonPropertyConsumer.java:236)
at
org.apache.olingo.odata2.core.ep.consumer.JsonPropertyConsumer.readPropertyValue(JsonPropertyConsumer.java:169)
at
org.apache.olingo.odata2.core.ep.consumer.JsonEntryConsumer.handleName(JsonEntryConsumer.java:172)
at
org.apache.olingo.odata2.core.ep.consumer.JsonEntryConsumer.readEntryContent(JsonEntryConsumer.java:130)
at
org.apache.olingo.odata2.core.ep.consumer.JsonEntryConsumer.readFeedEntry(JsonEntryConsumer.java:117)
at
org.apache.olingo.odata2.core.ep.consumer.JsonFeedConsumer.readArrayContent(JsonFeedConsumer.java:153)
at
org.apache.olingo.odata2.core.ep.consumer.JsonFeedConsumer.handleName(JsonFeedConsumer.java:122)
at
org.apache.olingo.odata2.core.ep.consumer.JsonFeedConsumer.readFeedContent(JsonFeedConsumer.java:111)
at
org.apache.olingo.odata2.core.ep.consumer.JsonFeedConsumer.readFeed(JsonFeedConsumer.java:96)
at
org.apache.olingo.odata2.core.ep.consumer.JsonFeedConsumer.readFeedStandalone(JsonFeedConsumer.java:63)
at
org.apache.olingo.odata2.core.ep.consumer.JsonEntityConsumer.readDeltaFeed(JsonEntityConsumer.java:95)
at
org.apache.olingo.odata2.core.ep.consumer.JsonEntityConsumer.readFeed(JsonEntityConsumer.java:81)
at
org.apache.olingo.odata2.core.ep.JsonEntityProvider.readFeed(JsonEntityProvider.java:309)
at
org.apache.olingo.odata2.core.ep.ProviderFacadeImpl.readFeed(ProviderFacadeImpl.java:166)
at
org.apache.olingo.odata2.api.ep.EntityProvider.readFeed(EntityProvider.java:708)
{code}
Best regards,
Daniel
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OLINGO-1170) Olingo v4 client api does not support custom query options in URIBuilder
[
https://issues.apache.org/jira/browse/OLINGO-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramya resolved OLINGO-1170.
---
Resolution: Fixed
> Olingo v4 client api does not support custom query options in URIBuilder
>
>
> Key: OLINGO-1170
> URL: https://issues.apache.org/jira/browse/OLINGO-1170
> Project: Olingo
> Issue Type: Bug
> Components: odata4-client
>Affects Versions: (Java) V4 4.3.0
>Reporter: Ronny Bremer
>Priority: Major
>
> I am trying to build a URI to access an Olingo based OData 4 service. I can
> add query options just fine, for example
> newURIBuilder(url).addQueryOption("SKIP", "4")
> will result in url?$SKIP=4
> However, if I want to specify a custom query option, it will also add a "$"
> in front of it, for example
> newURIBuilder(url).addQueryOption("LANG", "EN")
> will result in url?$LANG=EN
> This, of course, will result in an ODataClientErrorException: The system
> query option '$LANG' is not defined.
> There doesn't seem to be another method to add custom query options to
> URIBuilder, so I am opening this bug report.
> Yours,
> Ronny
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OLINGO-1214) Nullable Facet is not properly handled on complex types
[
https://issues.apache.org/jira/browse/OLINGO-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346459#comment-16346459
]
Ramya commented on OLINGO-1214:
---
Hi,
I am unable to reproduce this issue.
I have a complex Property Location in Entity A with nullable set to true and
Type is CT
I have a Complex Type CT which has a property City with nullable set to false.
My payload does not have Location but has all other properties of Entity A. The
EntityProviderWriteProperties is set as below
EntityProviderWriteProperties.serviceRoot(URI.create()).build();
The serializer is working fine with this.
Can you give more details so that i can reproduce the issue.
Regards,
Ramya
> Nullable Facet is not properly handled on complex types
> ---
>
> Key: OLINGO-1214
> URL: https://issues.apache.org/jira/browse/OLINGO-1214
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.9
>Reporter: Artem Böhme
>Priority: Major
>
> Hi,
> given complex type B with property 'x' which has the facet Nullable=false
> and
> given the entity A with the reference to complex type B via 'b' and the facet
> Nullable=true on 'b'
> This combination produces the error "The metadata do not allow a null value."
> at
> {{EntityProvider.writeEntry(contentType, targetEntitySet, data,
> EntityProviderWriteProperties.serviceRoot(getContext().getPathInfo().getServiceRoot()).build());}}
> if the data is A and data don't contain the key 'b'.
> If i debug into the code, I can see that the problem is the property 'x'
> which is not nullable, but in the described situation I don't have the 'b' at
> all (which can be nullable).
> I think the lines 76 to 95 in
> {{org.apache.olingo.odata2.core.ep.producer.JsonPropertyEntityProducer}}
> should be reviewed to handle the described case correctly.
> Please let me know, if you need more context info!
> Best regards,
> Artem
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OLINGO-1224) Odata2: entityset name cannot allow to contain dash (-)
[ https://issues.apache.org/jira/browse/OLINGO-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1224. --- Resolution: Fixed > Odata2: entityset name cannot allow to contain dash (-) > --- > > Key: OLINGO-1224 > URL: https://issues.apache.org/jira/browse/OLINGO-1224 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.10 >Reporter: Wendy Wang >Priority: Major > > Hi, > I'm using Olingo V2 to read metadata and getting such error that complains > the entityset name of "Background_Picklist-One" is invalid. The problematic > character is dash "-". > Best Regards, > Wendy -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1224) Odata2: entityset name cannot allow to contain dash (-)
[ https://issues.apache.org/jira/browse/OLINGO-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346413#comment-16346413 ] Ramya commented on OLINGO-1224: --- Hi, The entity set name should match the regular expression as specified in https://msdn.microsoft.com/en-us/library/dd541274.aspx. Here dash or hypen is not supported Regards, Ramya > Odata2: entityset name cannot allow to contain dash (-) > --- > > Key: OLINGO-1224 > URL: https://issues.apache.org/jira/browse/OLINGO-1224 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.10 >Reporter: Wendy Wang >Priority: Major > > Hi, > I'm using Olingo V2 to read metadata and getting such error that complains > the entityset name of "Background_Picklist-One" is invalid. The problematic > character is dash "-". > Best Regards, > Wendy -- This message was sent by Atlassian JIRA (v7.6.3#76005)
