You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@olingo.apache.org by "anu238 ." <an...@gmail.com> on 2016/01/29 20:51:41 UTC
Timeline for ODataV4 JPA Processor
Hi All,
Can you please tell by when ODATA4 JPA processor will be available?
Thanks,
Anurag
Re: Timeline for ODataV4 JPA Processor
Posted by "anu238 ." <an...@gmail.com>.
Thanks Michael for your kind response and info.
Best Regards,
Anurag
On Fri, Jan 29, 2016 at 12:20 PM, mibo <mi...@apache.org> wrote:
> Hi Anurag,
>
> Because that such features like a JPA extension are not in the main scope
> of Olingo
> we actual do not have a timeline for providing this.
> However the Olingo community is always open for contributions ;o)
> So if you want to start with developing a JPA processor/extension
> framework on top
> this would be welcome and I think you would find other community members
> which can support you.
>
> Best Regards,
> Michael
>
>
>
>
> On Jan 29, 2016, at 8:51 PM, anu238 . <an...@gmail.com> wrote:
>
> Hi All,
> Can you please tell by when ODATA4 JPA processor will be available?
> Thanks,
> Anurag
>
>
Re: Timeline for ODataV4 JPA Processor
Posted by Ramesh Reddy <ra...@redhat.com>.
Guys,
I created a "organization" and created a repo for "jpa-extensions" on GitHub here https://github.com/olingo-extensions
Let me know who wants to lead this project, then I will give them admin rights to the repository to start making the contributions (send me your github id). I also been thinking of writing a maven archtype for creating Olingo Service development, I will use this to create another repository under the same organization. Hopefully we can all put the code at one place rather than scattering all over the web.
Ramesh..
----- Original Message -----
> Hi Christian,
> Thanks for your email and good ideas on how we can work on it. I have also
> reached out to Richard for how we can take this forward.
> Thanks,
> Anurag
> P.S If anyone else is interested in joining this contribution please let us
> know.
> On Wed, Feb 3, 2016 at 7:20 AM, Amend, Christian < christian.amend@sap.com >
> wrote:
> > Hi Anurag and Richard,
>
> > it is awesome you want to contribute J
>
> > One way is to check out the current repository and start by developing on a
> > separate branch. There you could start with a first POC on how to implement
> > this.
>
> > Another way would be to create a fresh GitHub repository where you have
> > full
> > committing rights. There you could start with an implementation independent
> > from the Apache Process. Once you have a first POC you could contribute
> > this
> > to Olingo if you like. Once this contribution is done I don`t think the
> > community would mind to give you access to the Olingo git repos to let you
> > keep developing here.
>
> > One main concern with Olingo V2 was that the JPA processor could not be
> > released independently as it was part of the core maven project. With V4 we
> > could make this better by having a separate maven project for the JPA part.
> > This way you would not be blocked by the core library release cycle. You
> > could still use the Olingo core library to prevent code duplication.
>
> > The contribution can be done in many ways but I think it would be best if
> > you
> > have some code that you can attach to a JIRA issue which can then be
> > applied
> > to the Olingo git repository. Depending on how big the contribution is we
> > could also ask the Apache Infrastructure to give us a new git repo for the
> > JPA part.
>
> > Discussions can be either held here on the user list or on our dev list if
> > you have some architectural or code questions. I am looking forward to a
> > growing Olingo community J
>
> > Best Regards,
>
> > Christian
>
> > From: anu238 . [mailto: anurag.gujral@gmail.com ]
>
> > Sent: Dienstag, 2. Februar 2016 20:49
>
> > To: user@olingo.apache.org
>
> > Subject: Re: Timeline for ODataV4 JPA Processor
>
> > Hi Richard,
>
> > We are trying to use Olingo 4.0 but not having a JPA is making it difficult
> > to use. Our company is agreeing to join the initiative to contribute to JPA
> > for Olingo 4.0 . Please guide how to proceed in this matter.
>
> > Thanks & Regards,
>
> > Anurag
>
> > On Sat, Jan 30, 2016 at 1:08 AM, Birenheide, Richard <
> > richard.birenheide@sap.com > wrote:
>
> > > Hi Michael,
> >
>
> > > if anyhow possible, this should be reconsidered. Not having a JPA
> > > processor
> > > is the main obstacle for me not to switch to 4.0 although it has features
> > > I’d need badly (filters on navigation properties). A JPA processor
> > > (ideally
> > > with better interception possibilities on changing entities as in 2.0)
> > > would
> > > be a great contribution to developer productivity. If you need support
> > > I’d
> > > gladly arrange a meeting, I know several other potential stakeholders as
> > > well.
> >
>
> > > Kind Regards
> >
>
> > > Richard
> >
>
> > > From: mibo [mailto: mibo@apache.org ]
> >
>
> > > Sent: Freitag, 29. Januar 2016 21:21
> >
>
> > > To: user@olingo.apache.org
> >
>
> > > Subject: Re: Timeline for ODataV4 JPA Processor
> >
>
> > > Hi Anurag,
> >
>
> > > Because that such features like a JPA extension are not in the main scope
> > > of
> > > Olingo
> >
>
> > > we actual do not have a timeline for providing this.
> >
>
> > > However the Olingo community is always open for contributions ;o)
> >
>
> > > So if you want to start with developing a JPA processor/extension
> > > framework
> > > on top
> >
>
> > > this would be welcome and I think you would find other community members
> > > which can support you.
> >
>
> > > Best Regards,
> >
>
> > > Michael
> >
>
> > > > On Jan 29, 2016, at 8:51 PM, anu238 . < anurag.gujral@gmail.com >
> > > > wrote:
> > >
> >
>
> > > > Hi All,
> > >
> >
>
> > > > Can you please tell by when ODATA4 JPA processor will be available?
> > >
> >
>
> > > > Thanks,
> > >
> >
>
> > > > Anurag
> > >
> >
>
Re: Timeline for ODataV4 JPA Processor
Posted by "anu238 ." <an...@gmail.com>.
Hi Christian,
Thanks for your email and good ideas on how we can work on it. I have also
reached out to Richard for how we can take this forward.
Thanks,
Anurag
P.S If anyone else is interested in joining this contribution please let us
know.
On Wed, Feb 3, 2016 at 7:20 AM, Amend, Christian <ch...@sap.com>
wrote:
> Hi Anurag and Richard,
>
>
>
> it is awesome you want to contribute J
>
> One way is to check out the current repository and start by developing on
> a separate branch. There you could start with a first POC on how to
> implement this.
> Another way would be to create a fresh GitHub repository where you have
> full committing rights. There you could start with an implementation
> independent from the Apache Process. Once you have a first POC you could
> contribute this to Olingo if you like. Once this contribution is done I
> don`t think the community would mind to give you access to the Olingo git
> repos to let you keep developing here.
>
> One main concern with Olingo V2 was that the JPA processor could not be
> released independently as it was part of the core maven project. With V4 we
> could make this better by having a separate maven project for the JPA part.
> This way you would not be blocked by the core library release cycle. You
> could still use the Olingo core library to prevent code duplication.
>
> The contribution can be done in many ways but I think it would be best if
> you have some code that you can attach to a JIRA issue which can then be
> applied to the Olingo git repository. Depending on how big the contribution
> is we could also ask the Apache Infrastructure to give us a new git repo
> for the JPA part.
>
>
>
> Discussions can be either held here on the user list or on our dev list if
> you have some architectural or code questions. I am looking forward to a
> growing Olingo community J
>
>
>
> Best Regards,
>
> Christian
>
>
>
> *From:* anu238 . [mailto:anurag.gujral@gmail.com]
> *Sent:* Dienstag, 2. Februar 2016 20:49
>
> *To:* user@olingo.apache.org
> *Subject:* Re: Timeline for ODataV4 JPA Processor
>
>
>
> Hi Richard,
>
> We are trying to use Olingo 4.0 but not having a JPA is making it
> difficult to use. Our company is agreeing to join the initiative to
> contribute to JPA for Olingo 4.0 . Please guide how to proceed in this
> matter.
>
> Thanks & Regards,
>
> Anurag
>
>
>
> On Sat, Jan 30, 2016 at 1:08 AM, Birenheide, Richard <
> richard.birenheide@sap.com> wrote:
>
> Hi Michael,
>
>
>
> if anyhow possible, this should be reconsidered. Not having a JPA
> processor is the main obstacle for me not to switch to 4.0 although it has
> features I’d need badly (filters on navigation properties). A JPA processor
> (ideally with better interception possibilities on changing entities as in
> 2.0) would be a great contribution to developer productivity. If you need
> support I’d gladly arrange a meeting, I know several other potential
> stakeholders as well.
>
>
>
> Kind Regards
>
> Richard
>
>
>
> *From:* mibo [mailto:mibo@apache.org]
> *Sent:* Freitag, 29. Januar 2016 21:21
> *To:* user@olingo.apache.org
> *Subject:* Re: Timeline for ODataV4 JPA Processor
>
>
>
> Hi Anurag,
>
>
>
> Because that such features like a JPA extension are not in the main scope
> of Olingo
>
> we actual do not have a timeline for providing this.
>
> However the Olingo community is always open for contributions ;o)
>
> So if you want to start with developing a JPA processor/extension
> framework on top
>
> this would be welcome and I think you would find other community members
> which can support you.
>
>
>
> Best Regards,
>
> Michael
>
>
>
>
>
>
>
>
>
> On Jan 29, 2016, at 8:51 PM, anu238 . <an...@gmail.com> wrote:
>
>
>
> Hi All,
>
> Can you please tell by when ODATA4 JPA processor will be available?
>
> Thanks,
>
> Anurag
>
>
>
RE: Timeline for ODataV4 JPA Processor
Posted by "Amend, Christian" <ch...@sap.com>.
Hi Anurag and Richard,
it is awesome you want to contribute ☺
One way is to check out the current repository and start by developing on a separate branch. There you could start with a first POC on how to implement this.
Another way would be to create a fresh GitHub repository where you have full committing rights. There you could start with an implementation independent from the Apache Process. Once you have a first POC you could contribute this to Olingo if you like. Once this contribution is done I don`t think the community would mind to give you access to the Olingo git repos to let you keep developing here.
One main concern with Olingo V2 was that the JPA processor could not be released independently as it was part of the core maven project. With V4 we could make this better by having a separate maven project for the JPA part. This way you would not be blocked by the core library release cycle. You could still use the Olingo core library to prevent code duplication.
The contribution can be done in many ways but I think it would be best if you have some code that you can attach to a JIRA issue which can then be applied to the Olingo git repository. Depending on how big the contribution is we could also ask the Apache Infrastructure to give us a new git repo for the JPA part.
Discussions can be either held here on the user list or on our dev list if you have some architectural or code questions. I am looking forward to a growing Olingo community ☺
Best Regards,
Christian
From: anu238 . [mailto:anurag.gujral@gmail.com]
Sent: Dienstag, 2. Februar 2016 20:49
To: user@olingo.apache.org
Subject: Re: Timeline for ODataV4 JPA Processor
Hi Richard,
We are trying to use Olingo 4.0 but not having a JPA is making it difficult to use. Our company is agreeing to join the initiative to contribute to JPA for Olingo 4.0 . Please guide how to proceed in this matter.
Thanks & Regards,
Anurag
On Sat, Jan 30, 2016 at 1:08 AM, Birenheide, Richard <ri...@sap.com>> wrote:
Hi Michael,
if anyhow possible, this should be reconsidered. Not having a JPA processor is the main obstacle for me not to switch to 4.0 although it has features I’d need badly (filters on navigation properties). A JPA processor (ideally with better interception possibilities on changing entities as in 2.0) would be a great contribution to developer productivity. If you need support I’d gladly arrange a meeting, I know several other potential stakeholders as well.
Kind Regards
Richard
From: mibo [mailto:mibo@apache.org<ma...@apache.org>]
Sent: Freitag, 29. Januar 2016 21:21
To: user@olingo.apache.org<ma...@olingo.apache.org>
Subject: Re: Timeline for ODataV4 JPA Processor
Hi Anurag,
Because that such features like a JPA extension are not in the main scope of Olingo
we actual do not have a timeline for providing this.
However the Olingo community is always open for contributions ;o)
So if you want to start with developing a JPA processor/extension framework on top
this would be welcome and I think you would find other community members which can support you.
Best Regards,
Michael
On Jan 29, 2016, at 8:51 PM, anu238 . <an...@gmail.com>> wrote:
Hi All,
Can you please tell by when ODATA4 JPA processor will be available?
Thanks,
Anurag
Re: Timeline for ODataV4 JPA Processor
Posted by "anu238 ." <an...@gmail.com>.
Hi Richard,
We are trying to use Olingo 4.0 but not having a JPA is making it difficult
to use. Our company is agreeing to join the initiative to contribute to JPA
for Olingo 4.0 . Please guide how to proceed in this matter.
Thanks & Regards,
Anurag
On Sat, Jan 30, 2016 at 1:08 AM, Birenheide, Richard <
richard.birenheide@sap.com> wrote:
> Hi Michael,
>
>
>
> if anyhow possible, this should be reconsidered. Not having a JPA
> processor is the main obstacle for me not to switch to 4.0 although it has
> features I’d need badly (filters on navigation properties). A JPA processor
> (ideally with better interception possibilities on changing entities as in
> 2.0) would be a great contribution to developer productivity. If you need
> support I’d gladly arrange a meeting, I know several other potential
> stakeholders as well.
>
>
>
> Kind Regards
>
> Richard
>
>
>
> *From:* mibo [mailto:mibo@apache.org]
> *Sent:* Freitag, 29. Januar 2016 21:21
> *To:* user@olingo.apache.org
> *Subject:* Re: Timeline for ODataV4 JPA Processor
>
>
>
> Hi Anurag,
>
>
>
> Because that such features like a JPA extension are not in the main scope
> of Olingo
>
> we actual do not have a timeline for providing this.
>
> However the Olingo community is always open for contributions ;o)
>
> So if you want to start with developing a JPA processor/extension
> framework on top
>
> this would be welcome and I think you would find other community members
> which can support you.
>
>
>
> Best Regards,
>
> Michael
>
>
>
>
>
>
>
>
>
> On Jan 29, 2016, at 8:51 PM, anu238 . <an...@gmail.com> wrote:
>
>
>
> Hi All,
>
> Can you please tell by when ODATA4 JPA processor will be available?
>
> Thanks,
>
> Anurag
>
>
RE: Timeline for ODataV4 JPA Processor
Posted by "Birenheide, Richard" <ri...@sap.com>.
Hi Michael,
if anyhow possible, this should be reconsidered. Not having a JPA processor is the main obstacle for me not to switch to 4.0 although it has features I’d need badly (filters on navigation properties). A JPA processor (ideally with better interception possibilities on changing entities as in 2.0) would be a great contribution to developer productivity. If you need support I’d gladly arrange a meeting, I know several other potential stakeholders as well.
Kind Regards
Richard
From: mibo [mailto:mibo@apache.org]
Sent: Freitag, 29. Januar 2016 21:21
To: user@olingo.apache.org
Subject: Re: Timeline for ODataV4 JPA Processor
Hi Anurag,
Because that such features like a JPA extension are not in the main scope of Olingo
we actual do not have a timeline for providing this.
However the Olingo community is always open for contributions ;o)
So if you want to start with developing a JPA processor/extension framework on top
this would be welcome and I think you would find other community members which can support you.
Best Regards,
Michael
On Jan 29, 2016, at 8:51 PM, anu238 . <an...@gmail.com>> wrote:
Hi All,
Can you please tell by when ODATA4 JPA processor will be available?
Thanks,
Anurag
Re: Timeline for ODataV4 JPA Processor
Posted by mibo <mi...@apache.org>.
Hi Anurag,
Because that such features like a JPA extension are not in the main scope of Olingo
we actual do not have a timeline for providing this.
However the Olingo community is always open for contributions ;o)
So if you want to start with developing a JPA processor/extension framework on top
this would be welcome and I think you would find other community members which can support you.
Best Regards,
Michael
> On Jan 29, 2016, at 8:51 PM, anu238 . <an...@gmail.com> wrote:
>
>
> Hi All,Can you please tell by when ODATA4 JPA processor will be available?
> Thanks,
> Anurag
>