[jira] [Created] (OLINGO-1215) Download page must not link to dist.apache.org

2017-12-11 Thread Sebb (JIRA)
Sebb created OLINGO-1215:


 Summary: Download page must not link to dist.apache.org
 Key: OLINGO-1215
 URL: https://issues.apache.org/jira/browse/OLINGO-1215
 Project: Olingo
  Issue Type: Bug
Reporter: Sebb


The download page currently links to https://dist.apache.org/ for the hashes 
and sigs.

However that host is only intended as a staging area for use by developers.

Please can you change the links to use the ASF webserver instead?

i.e.. change
https://dist.apache.org/repos/dist/release/...
to
https://www.apache.org/dist/...
wherever it appears.

Also the download page must have a (https) link to the KEYS file:

https://www.apache.org/dist/olingo/KEYS

Thanks

BTW, the page uses the word 'productive' (1) several times.
That should be 'production'.

[1] https://www.merriam-webster.com/dictionary/productive



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[ANNOUNCE] Apache Olingo 2.0.10 has been released

2017-12-11 Thread Christian Amend
Hello,

Apache Olingo 2.0.10 has been released.

This is a patch release of Apache Olingo which includes Bugfixes and
Improvements for client and server use cases.

This release is available for download:
http://olingo.apache.org/download.html

Apache Olingo is a Java library which enables developers to implement OData
producers and OData consumers.

The Open Data Protocol (OData, http://odata.org) is a Web protocol for
querying and updating data that provides a way to unlock your data and free
it from silos that exist in applications today. OData does this by applying
and building upon Web technologies such as HTTP, Atom Publishing Protocol
(AtomPub) and JSON to provide access to information from a variety of
applications, services, and stores.

Best Regards, Michael

Release Notes - Olingo - Version 2.0.10
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314520=12341072

Bug
[OLINGO-996] - ODataJPA Extension creates illegal Entity Container Name
[OLINGO-1108] - Edm.Decimal not supported in OData Create requests (POST)
[OLINGO-1146] - CLONE - Cannot Filter on Navigation Property
Improvement
[OLINGO-1192] - Parameterizing JPA Queries
New Feature
[OLINGO-605] - Olingo should support custom types e.g. Geometry by using
XmlAdapter from JaxB


[jira] [Updated] (OLINGO-1214) Nullable Facet is not properly handled on complex types

2017-12-11 Thread JIRA

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

Artem Böhme updated OLINGO-1214:

Description: 
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 

  was:
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 


> 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
>
> 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
(v6.4.14#64029)


[jira] [Created] (OLINGO-1214) Nullable Facet is not properly handled on complex types

2017-12-11 Thread JIRA
Artem Böhme created OLINGO-1214:
---

 Summary: 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


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
(v6.4.14#64029)