You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Klevenz, Stephan" <st...@sap.com> on 2013/08/23 10:04:28 UTC
distributions
Hi,
To get a first release we have to think about distributions which we can put onto a download page.
Basically I do see this kinds of distributions:
1. OData Lib (api + core + dependencies)
2. OData Lib + JPA Processor (jpa api + jpa core + annotations + more dependencies)
About the dependencies:
I suggest not to bundle a specific Apache CXF version. The project uses a specific CXF version (currently 2.7.5) only for testing and the lib should work also with other versions. Potentially any JAX-RS implementation should work.
WDYT?
Regards,
Stephan
RE: distributions
Posted by "Huesken, Jens" <je...@sap.com>.
Hi,
+1 for [1] and [2], too.
Also I like the idea of distributing the reference scenarios ([3] and[4]) They could serve as kind of template for developers. As consequence it will definitely be additional effort to produce and distribute.
+1 for [A] and [B].
Any other opinions?
Best regards,
Jens
-----Original Message-----
From: V.A, Chandan [mailto:chandan.v.a@sap.com]
Sent: Sonntag, 25. August 2013 07:19
To: dev@olingo.incubator.apache.org
Subject: RE: distributions
Hi,
+1 for [1] and [2].
Can we also distribute
3. Reference scenario for OData Lib
4. Reference scenario for OData JPA Lib
The reference scenario could use a specific version of dependency for example CXF, Eclipse Link 2.5.0 in case of JPA.
Secondly
Should we also consider separate distributions in the download page for
A. JARs with no source code
B. JARs + source code + java docs as one bundle
In case developers don't have experience with git, then they can directly download the source code from the download page as .zip format.
Thanks,
Kind Regards
Chandan VA
-----Original Message-----
From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
Sent: Friday, August 23, 2013 1:34 PM
To: dev@olingo.incubator.apache.org
Subject: distributions
Hi,
To get a first release we have to think about distributions which we can put onto a download page.
Basically I do see this kinds of distributions:
1. OData Lib (api + core + dependencies)
2. OData Lib + JPA Processor (jpa api + jpa core + annotations + more dependencies)
About the dependencies:
I suggest not to bundle a specific Apache CXF version. The project uses a specific CXF version (currently 2.7.5) only for testing and the lib should work also with other versions. Potentially any JAX-RS implementation should work.
WDYT?
Regards,
Stephan
RE: distributions
Posted by "Huesken, Jens" <je...@sap.com>.
I also think that a second data model makes sense to show different use cases
--Jens
-----Original Message-----
From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
Sent: Donnerstag, 29. August 2013 13:36
To: dev@olingo.incubator.apache.org
Subject: Re: distributions
+1 for 3
Another data model for JPA will maybe useful to get ideas about different
OData use cases.
-- Stephan
On 28.08.13 09:17, "V.A, Chandan" <ch...@sap.com> wrote:
>Hi,
>Just a thought. Do we need a common data model for the reference
>scenarios of OData Lib and JPA Lib; so it gives a common understanding of
>the data model for the developers using both the library. I mean only a
>common data model and not a common reference scenario implementation.
>
>1) Is this Ok?
>2) if 1) is Ok then I can create a new reference scenario for JPA based
>on the existing OData Lib reference scenario. Employee - Manager - City -
>Room - Team - Location - Photo - Building.
>3) if 1) is not Ok then I can push the existing reference scenario for
>JPA into git. Sales Order - Sales Order Item - Notes - Materials - Store
>- Storage Location. The existing reference scenario covers many concepts
>from JPA 2.0 specification.
>
>Thanks,
>Kind Regards
>Chandan VA
>
>-----Original Message-----
>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>Sent: Tuesday, August 27, 2013 7:42 PM
>To: dev@olingo.incubator.apache.org
>Subject: Re: distributions
>
>Cool ideas. I am working currently on a distribution module. Do we have
>code for a JPA based reference scenario?
>
>Greetings,
>Stephan
>
>
>On 25.08.13 07:18, "V.A, Chandan" <ch...@sap.com> wrote:
>
>>Hi,
>>
>>+1 for [1] and [2].
>>
>>Can we also distribute
>>3. Reference scenario for OData Lib
>>4. Reference scenario for OData JPA Lib
>>
>>The reference scenario could use a specific version of dependency for
>>example CXF, Eclipse Link 2.5.0 in case of JPA.
>>
>>Secondly
>>Should we also consider separate distributions in the download page for
>>A. JARs with no source code
>>B. JARs + source code + java docs as one bundle
>>
>>In case developers don't have experience with git, then they can directly
>>download the source code from the download page as .zip format.
>>
>>
>>Thanks,
>>Kind Regards
>>Chandan VA
>>
>>-----Original Message-----
>>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>>Sent: Friday, August 23, 2013 1:34 PM
>>To: dev@olingo.incubator.apache.org
>>Subject: distributions
>>
>>Hi,
>>
>>To get a first release we have to think about distributions which we can
>>put onto a download page.
>>
>>Basically I do see this kinds of distributions:
>>
>> 1. OData Lib (api + core + dependencies)
>> 2. OData Lib + JPA Processor (jpa api + jpa core + annotations + more
>>dependencies)
>>
>>About the dependencies:
>>
>>I suggest not to bundle a specific Apache CXF version. The project uses a
>>specific CXF version (currently 2.7.5) only for testing and the lib
>>should work also with other versions. Potentially any JAX-RS
>>implementation should work.
>>
>>WDYT?
>>
>>Regards,
>>Stephan
>
Re: distributions
Posted by "Klevenz, Stephan" <st...@sap.com>.
+1 for 3
Another data model for JPA will maybe useful to get ideas about different
OData use cases.
-- Stephan
On 28.08.13 09:17, "V.A, Chandan" <ch...@sap.com> wrote:
>Hi,
>Just a thought. Do we need a common data model for the reference
>scenarios of OData Lib and JPA Lib; so it gives a common understanding of
>the data model for the developers using both the library. I mean only a
>common data model and not a common reference scenario implementation.
>
>1) Is this Ok?
>2) if 1) is Ok then I can create a new reference scenario for JPA based
>on the existing OData Lib reference scenario. Employee - Manager - City -
>Room - Team - Location - Photo - Building.
>3) if 1) is not Ok then I can push the existing reference scenario for
>JPA into git. Sales Order - Sales Order Item - Notes - Materials - Store
>- Storage Location. The existing reference scenario covers many concepts
>from JPA 2.0 specification.
>
>Thanks,
>Kind Regards
>Chandan VA
>
>-----Original Message-----
>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>Sent: Tuesday, August 27, 2013 7:42 PM
>To: dev@olingo.incubator.apache.org
>Subject: Re: distributions
>
>Cool ideas. I am working currently on a distribution module. Do we have
>code for a JPA based reference scenario?
>
>Greetings,
>Stephan
>
>
>On 25.08.13 07:18, "V.A, Chandan" <ch...@sap.com> wrote:
>
>>Hi,
>>
>>+1 for [1] and [2].
>>
>>Can we also distribute
>>3. Reference scenario for OData Lib
>>4. Reference scenario for OData JPA Lib
>>
>>The reference scenario could use a specific version of dependency for
>>example CXF, Eclipse Link 2.5.0 in case of JPA.
>>
>>Secondly
>>Should we also consider separate distributions in the download page for
>>A. JARs with no source code
>>B. JARs + source code + java docs as one bundle
>>
>>In case developers don't have experience with git, then they can directly
>>download the source code from the download page as .zip format.
>>
>>
>>Thanks,
>>Kind Regards
>>Chandan VA
>>
>>-----Original Message-----
>>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>>Sent: Friday, August 23, 2013 1:34 PM
>>To: dev@olingo.incubator.apache.org
>>Subject: distributions
>>
>>Hi,
>>
>>To get a first release we have to think about distributions which we can
>>put onto a download page.
>>
>>Basically I do see this kinds of distributions:
>>
>> 1. OData Lib (api + core + dependencies)
>> 2. OData Lib + JPA Processor (jpa api + jpa core + annotations + more
>>dependencies)
>>
>>About the dependencies:
>>
>>I suggest not to bundle a specific Apache CXF version. The project uses a
>>specific CXF version (currently 2.7.5) only for testing and the lib
>>should work also with other versions. Potentially any JAX-RS
>>implementation should work.
>>
>>WDYT?
>>
>>Regards,
>>Stephan
>
RE: distributions
Posted by "V.A, Chandan" <ch...@sap.com>.
Hi,
Just a thought. Do we need a common data model for the reference scenarios of OData Lib and JPA Lib; so it gives a common understanding of the data model for the developers using both the library. I mean only a common data model and not a common reference scenario implementation.
1) Is this Ok?
2) if 1) is Ok then I can create a new reference scenario for JPA based on the existing OData Lib reference scenario. Employee - Manager - City - Room - Team - Location - Photo - Building.
3) if 1) is not Ok then I can push the existing reference scenario for JPA into git. Sales Order - Sales Order Item - Notes - Materials - Store - Storage Location. The existing reference scenario covers many concepts from JPA 2.0 specification.
Thanks,
Kind Regards
Chandan VA
-----Original Message-----
From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
Sent: Tuesday, August 27, 2013 7:42 PM
To: dev@olingo.incubator.apache.org
Subject: Re: distributions
Cool ideas. I am working currently on a distribution module. Do we have
code for a JPA based reference scenario?
Greetings,
Stephan
On 25.08.13 07:18, "V.A, Chandan" <ch...@sap.com> wrote:
>Hi,
>
>+1 for [1] and [2].
>
>Can we also distribute
>3. Reference scenario for OData Lib
>4. Reference scenario for OData JPA Lib
>
>The reference scenario could use a specific version of dependency for
>example CXF, Eclipse Link 2.5.0 in case of JPA.
>
>Secondly
>Should we also consider separate distributions in the download page for
>A. JARs with no source code
>B. JARs + source code + java docs as one bundle
>
>In case developers don't have experience with git, then they can directly
>download the source code from the download page as .zip format.
>
>
>Thanks,
>Kind Regards
>Chandan VA
>
>-----Original Message-----
>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>Sent: Friday, August 23, 2013 1:34 PM
>To: dev@olingo.incubator.apache.org
>Subject: distributions
>
>Hi,
>
>To get a first release we have to think about distributions which we can
>put onto a download page.
>
>Basically I do see this kinds of distributions:
>
> 1. OData Lib (api + core + dependencies)
> 2. OData Lib + JPA Processor (jpa api + jpa core + annotations + more
>dependencies)
>
>About the dependencies:
>
>I suggest not to bundle a specific Apache CXF version. The project uses a
>specific CXF version (currently 2.7.5) only for testing and the lib
>should work also with other versions. Potentially any JAX-RS
>implementation should work.
>
>WDYT?
>
>Regards,
>Stephan
RE: distributions
Posted by "Amend, Christian" <ch...@sap.com>.
Hi,
>From me it is also a +1 for 1., 2., A and B.
I also think we should have fixed dependencies for the reference scenarios. They should work without having to configure much to make it easier for new developers to understand how to develop an OData service.
Best Regards,
Christian
-----Original Message-----
From: V.A, Chandan [mailto:chandan.v.a@sap.com]
Sent: Sonntag, 25. August 2013 07:19
To: dev@olingo.incubator.apache.org
Subject: RE: distributions
Hi,
+1 for [1] and [2].
Can we also distribute
3. Reference scenario for OData Lib
4. Reference scenario for OData JPA Lib
The reference scenario could use a specific version of dependency for example CXF, Eclipse Link 2.5.0 in case of JPA.
Secondly
Should we also consider separate distributions in the download page for
A. JARs with no source code
B. JARs + source code + java docs as one bundle
In case developers don't have experience with git, then they can directly download the source code from the download page as .zip format.
Thanks,
Kind Regards
Chandan VA
-----Original Message-----
From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
Sent: Friday, August 23, 2013 1:34 PM
To: dev@olingo.incubator.apache.org
Subject: distributions
Hi,
To get a first release we have to think about distributions which we can put onto a download page.
Basically I do see this kinds of distributions:
1. OData Lib (api + core + dependencies)
2. OData Lib + JPA Processor (jpa api + jpa core + annotations + more dependencies)
About the dependencies:
I suggest not to bundle a specific Apache CXF version. The project uses a specific CXF version (currently 2.7.5) only for testing and the lib should work also with other versions. Potentially any JAX-RS implementation should work.
WDYT?
Regards,
Stephan
Re: distributions
Posted by "Klevenz, Stephan" <st...@sap.com>.
Cool ideas. I am working currently on a distribution module. Do we have
code for a JPA based reference scenario?
Greetings,
Stephan
On 25.08.13 07:18, "V.A, Chandan" <ch...@sap.com> wrote:
>Hi,
>
>+1 for [1] and [2].
>
>Can we also distribute
>3. Reference scenario for OData Lib
>4. Reference scenario for OData JPA Lib
>
>The reference scenario could use a specific version of dependency for
>example CXF, Eclipse Link 2.5.0 in case of JPA.
>
>Secondly
>Should we also consider separate distributions in the download page for
>A. JARs with no source code
>B. JARs + source code + java docs as one bundle
>
>In case developers don't have experience with git, then they can directly
>download the source code from the download page as .zip format.
>
>
>Thanks,
>Kind Regards
>Chandan VA
>
>-----Original Message-----
>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>Sent: Friday, August 23, 2013 1:34 PM
>To: dev@olingo.incubator.apache.org
>Subject: distributions
>
>Hi,
>
>To get a first release we have to think about distributions which we can
>put onto a download page.
>
>Basically I do see this kinds of distributions:
>
> 1. OData Lib (api + core + dependencies)
> 2. OData Lib + JPA Processor (jpa api + jpa core + annotations + more
>dependencies)
>
>About the dependencies:
>
>I suggest not to bundle a specific Apache CXF version. The project uses a
>specific CXF version (currently 2.7.5) only for testing and the lib
>should work also with other versions. Potentially any JAX-RS
>implementation should work.
>
>WDYT?
>
>Regards,
>Stephan
RE: distributions
Posted by "V.A, Chandan" <ch...@sap.com>.
Hi,
+1 for [1] and [2].
Can we also distribute
3. Reference scenario for OData Lib
4. Reference scenario for OData JPA Lib
The reference scenario could use a specific version of dependency for example CXF, Eclipse Link 2.5.0 in case of JPA.
Secondly
Should we also consider separate distributions in the download page for
A. JARs with no source code
B. JARs + source code + java docs as one bundle
In case developers don't have experience with git, then they can directly download the source code from the download page as .zip format.
Thanks,
Kind Regards
Chandan VA
-----Original Message-----
From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
Sent: Friday, August 23, 2013 1:34 PM
To: dev@olingo.incubator.apache.org
Subject: distributions
Hi,
To get a first release we have to think about distributions which we can put onto a download page.
Basically I do see this kinds of distributions:
1. OData Lib (api + core + dependencies)
2. OData Lib + JPA Processor (jpa api + jpa core + annotations + more dependencies)
About the dependencies:
I suggest not to bundle a specific Apache CXF version. The project uses a specific CXF version (currently 2.7.5) only for testing and the lib should work also with other versions. Potentially any JAX-RS implementation should work.
WDYT?
Regards,
Stephan