You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@olingo.apache.org by Murali Sai Rama Krishna V <mu...@nalashaa.com> on 2014/09/05 15:03:59 UTC
Apache Olingo Producer Application Run as standalone.
Hi Team,
We are planning to use Olingo for hosting OData service.
We want to run OData service as standalone but not via Webapplication Server such as Tomcat.
Could you please suggest a solution where we can run or Odata service as standalone by creating a jar file and run via JVM.
Thanks & Regards,
Murali.
===============
Re: Apache Olingo Producer Application Run as standalone.
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi Murali,
On 11.09.2014, at 12:37, Murali Sai Rama Krishna V <mu...@nalashaa.com> wrote:
> Hi Michael,
> I have some queries:
> 1) When we are using EntityProvider’s write method for displaying Entity Information for the $filter query, “is it mandatory to provide EdmEntitySet to writeFeed or we can bypass this by any chance?
Yes, for the EntityProvider "write/read" methods the EDM information (e.g. EdmEntitySet) is mandatory because the given data is validated against the EDM.
> 2) Could you please confirm Olingo OData Framework caches all the metadata information (EntityType, EntitySets, ComplexTypes etc) internally once the service is started ?
Yes, for the case that you use the "ODataServiceFactory.createODataSingleProcessorService(...)" method to create a "ODataService" the metadata information will be cached there.
If you create/implement your own "ODataService" there is no metadata cached by the Olingo library.
Kind regards,
Michael
>
>
> Thanks & Regards,
> Murali.
> ===============
RE: Apache Olingo Producer Application Run as standalone.
Posted by Murali Sai Rama Krishna V <mu...@nalashaa.com>.
Hi Michael,
I have some queries:
1) When we are using EntityProvider's write method for displaying Entity Information for the $filter query, "is it mandatory to provide EdmEntitySet to writeFeed or we can bypass this by any chance?
2) Could you please confirm Olingo OData Framework caches all the metadata information (EntityType, EntitySets, ComplexTypes etc) internally once the service is started ?
Thanks & Regards,
Murali.
===============
From: Bolz, Michael [mailto:michael.bolz@sap.com]
Sent: Thursday, September 11, 2014 9:18 AM
To: user@olingo.apache.org
Subject: Re: Apache Olingo Producer Application Run as standalone.
Hi Pankaj,
No problem and for us it is always nice to see that Olingo is used and hopefully liked ;o)
Kind regards,
Michael
From: Pankaj Arora <pa...@jitterbit.com>>
Reply-To: "user@olingo.apache.org<ma...@olingo.apache.org>" <us...@olingo.apache.org>>
Date: Mittwoch, 10. September 2014 20:13
To: "user@olingo.apache.org<ma...@olingo.apache.org>" <us...@olingo.apache.org>>
Subject: RE: Apache Olingo Producer Application Run as standalone.
Thanks Michael. This really helped and we are going this way.
Pankaj
From: Bolz, Michael [mailto:michael.bolz@sap.com]
Sent: Tuesday, September 09, 2014 8:44 PM
To: user@olingo.apache.org<ma...@olingo.apache.org>
Subject: Re: Apache Olingo Producer Application Run as standalone.
Hi Pankaj,
On 09.09.2014, at 21:31, Pankaj Arora <pa...@jitterbit.com>> wrote:
Hi Michael,
Thanks for helping us. Just to clarify, will it be enough to use read/write methods of EntityProvider.
As I understand your use case to just convert our data into and from OData XML format, yes it will be enough.
As I understand from tutorials, when the service is handled by service, it must be doing many more steps before calling read/write methods.
This steps are mainly content negotiation and routing to the correct read/write (based on called url), which you don't need if you just want to convert known data.
Can you please help us by sharing some details on what will be sequence of classes we might end up using/implementing to use the converter part per our use case?
It will even help to have a checklist of classes/interfaces that might be involved so while we dig in the code we have some guidance.
As mentioned you need the "EntityProvider" for the read/write and an implementation of the "EdmProvider" for definition of your Data Model (see: http://olingo.apache.org/doc/tutorials/basicread.html#implement-the-entity-data-model-provider).
Think this should be the necessary parts for our use case.
Kind regards,
Michael
Pankaj
From: Bolz, Michael [mailto:michael.bolz@sap.com]
Sent: Tuesday, September 09, 2014 4:58 AM
To: user@olingo.apache.org<ma...@olingo.apache.org>
Cc: peter.lawrence@inova8.com<ma...@inova8.com>; Ilya Pupko
Subject: Re: Apache Olingo Producer Application Run as standalone.
Hi Murali,
if you only want to convert data payload from and into OData format (ATOM/XML) you can use the "EntityProvider" "read/write" methods.
Those converts data (specified via an EDM) from a Java Map into OData XML.
Or the other way OData XML into a Java Map.
Kind regards,
Michael
On 09 Sep 2014, at 08:39, Murali Sai Rama Krishna V <mu...@nalashaa.com>> wrote:
Hi,
Our use case for using Olingo is to use it as a "converter" to change the OData compliant data to internal XML and vice versa. Couple of questions which might help us review our architecture :
* Is that the right way to use your library or any other Odata library? Or does Odata compliance/handling for data should be done at API service layer?
* If Olingo can help us do conversion on payload extracted by our API layer, can we use some internal OData parts of Olingo library to just convert the data payload?
Murali.
=======
From: Peter Lawrence [mailto:peter.lawrence@inova8.com]
Sent: Monday, September 08, 2014 11:18 PM
To: user@olingo.apache.org<ma...@olingo.apache.org>
Cc: Ilya Pupko
Subject: Re: Apache Olingo Producer Application Run as standalone.
Would the service resolution help: http://olingo.apache.org/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html
I have used this to support multiple OData endpoints with different versions from the same service.
Of course I could also be creating greater confusion.
Peter J. Lawrence
inova8
Providing answers for users' information questions
Mobile: +1 330 631 3772 | Phone: +1 330 342 0582 | Skype: PeterJLawrence
Email: peter.lawrence@inova8.com<ma...@inova8.com> | Web: www.inova8.com<http://www.inova8.com/>
LinkedIn: http://www.linkedin.com/in/peterjohnlawrence
On Mon, Sep 8, 2014 at 1:34 PM, Ramesh Reddy <ra...@redhat.com>> wrote:
Murali,
web.xml is what bootstaps in your web application and provides the context for your service. This lets you define the servlet where you can initialize and manage your ODataService.
What is your expectation on dynamically creating it? There are options, but you still need to start with static web.xml at minimum.
Ramesh..
----- Original Message -----
> Hi Ramesh / Michael,
>
> Thanks a lot for your responses.
>
> I have a one more question:
>
> In web.xml we are configuring the ODataService. Could you please let me know
> whether we can create a service dynamically without configuring in web.xml?
> Such as dynamically hosting the Odata service ?
>
> Could you please let me know your thoughts.
>
>
> Thanks & Regards,
> Murali.
> =================
>
> -----Original Message-----
> From: Mi Bo [mailto:mibo.asap@gmail.com<ma...@gmail.com>] On Behalf Of mibo
> Sent: Friday, September 05, 2014 9:38 PM
> To: user@olingo.apache.org<ma...@olingo.apache.org>
> Cc: Ilya Pupko
> Subject: Re: Apache Olingo Producer Application Run as standalone.
>
> Hi Murali,
>
> as Ramesh already mentioned, you need some service to provide the HTTP
> capabilities.
> As example in our sample archetype for Java annotations (see:
> http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html) we
> use also a Jetty to run the OData service.
> It could be a good starting point to create a sample project with this
> archetype and call "mvn" to run it on a local Jetty instance to see how it
> works.
>
> Kind regards,
> Michael
>
> Am 05.09.2014 um 15:55 schrieb Ramesh Reddy <ra...@redhat.com>>:
>
> > If you are not going to use Server such as Tomcat, then you need think
> > about embedding some web server to provide the HTTP query capabilities. I
> > have used Jetty for testing previously.
> >
> > Ramesh..
> >
> > Hi Team,
> >
> > We are planning to use Olingo for hosting OData service.
> >
> > We want to run OData service as standalone but not via Webapplication
> > Server such as Tomcat.
> >
> > Could you please suggest a solution where we can run or Odata service as
> > standalone by creating a jar file and run via JVM.
> >
> >
> > Thanks & Regards,
> > Murali.
> > ===============
>
>
Re: Apache Olingo Producer Application Run as standalone.
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi Pankaj,
No problem and for us it is always nice to see that Olingo is used and
hopefully liked ;o)
Kind regards,
Michael
From: Pankaj Arora <pa...@jitterbit.com>
Reply-To: "user@olingo.apache.org" <us...@olingo.apache.org>
Date: Mittwoch, 10. September 2014 20:13
To: "user@olingo.apache.org" <us...@olingo.apache.org>
Subject: RE: Apache Olingo Producer Application Run as standalone.
Thanks Michael. This really helped and we are going this way.
Pankaj
From: Bolz, Michael [mailto:michael.bolz@sap.com]
Sent: Tuesday, September 09, 2014 8:44 PM
To: user@olingo.apache.org
Subject: Re: Apache Olingo Producer Application Run as standalone.
Hi Pankaj,
On 09.09.2014, at 21:31, Pankaj Arora <pa...@jitterbit.com> wrote:
Hi Michael,
Thanks for helping us. Just to clarify, will it be enough to use read/write
methods of EntityProvider.
As I understand your use case to just convert our data into and from OData
XML format, yes it will be enough.
As I understand from tutorials, when the service is handled by service, it
must be doing many more steps before calling read/write methods.
This steps are mainly content negotiation and routing to the correct
read/write (based on called url), which you don't need if you just want to
convert known data.
Can you please help us by sharing some details on what will be sequence of
classes we might end up using/implementing to use the converter part per our
use case?
> It will even help to have a checklist of classes/interfaces that might be
> involved so while we dig in the code we have some guidance.
As mentioned you need the "EntityProvider" for the read/write and an
implementation of the "EdmProvider" for definition of your Data Model (see:
http://olingo.apache.org/doc/tutorials/basicread.html#implement-the-entity-d
ata-model-provider).
Think this should be the necessary parts for our use case.
Kind regards,
Michael
Pankaj
From: Bolz, Michael [mailto:michael.bolz@sap.com]
Sent: Tuesday, September 09, 2014 4:58 AM
To: user@olingo.apache.org
Cc: peter.lawrence@inova8.com; Ilya Pupko
Subject: Re: Apache Olingo Producer Application Run as standalone.
Hi Murali,
if you only want to convert data payload from and into OData format
(ATOM/XML) you can use the ³EntityProvider² ³read/write² methods.
Those converts data (specified via an EDM) from a Java Map into OData XML.
Or the other way OData XML into a Java Map.
Kind regards,
Michael
On 09 Sep 2014, at 08:39, Murali Sai Rama Krishna V <murali.v@nalashaa.com
<ma...@nalashaa.com> > wrote:
Hi,
Our use case for using Olingo is to use it as a "converter" to change the
OData compliant data to internal XML and vice versa. Couple of questions
which might help us review our architecture :
· Is that the right way to use your library or any other Odata
library? Or does Odata compliance/handling for data should be done at API
service layer?
· If Olingo can help us do conversion on payload extracted by our
API layer, can we use some internal OData parts of Olingo library to just
convert the data payload?
Murali.
=======
From: Peter Lawrence [mailto:peter.lawrence@inova8.com
<ma...@inova8.com> ]
Sent: Monday, September 08, 2014 11:18 PM
To: user@olingo.apache.org <ma...@olingo.apache.org>
Cc: Ilya Pupko
Subject: Re: Apache Olingo Producer Application Run as standalone.
Would the service resolution help:
http://olingo.apache.org/doc/tutorials/Olingo_Tutorial_Advanced_Service_Reso
lution.html
<http://olingo.apache.org/doc/tutorials/Olingo_Tutorial_Advanced_Service_Res
olution.html>
I have used this to support multiple OData endpoints with different versions
from the same service.
Of course I could also be creating greater confusion.
Peter J. Lawrence
inova8
Providing answers for users' information questions
Mobile: +1 330 631 3772 | Phone: +1 330 342 0582 | Skype: PeterJLawrence
Email: peter.lawrence@inova8.com <ma...@inova8.com> | Web:
www.inova8.com <http://www.inova8.com/>
LinkedIn: http://www.linkedin.com/in/peterjohnlawrence
<http://www.linkedin.com/in/peterjohnlawrence>
On Mon, Sep 8, 2014 at 1:34 PM, Ramesh Reddy <rareddy@redhat.com
<ma...@redhat.com> > wrote:
Murali,
web.xml is what bootstaps in your web application and provides the context
for your service. This lets you define the servlet where you can initialize
and manage your ODataService.
What is your expectation on dynamically creating it? There are options, but
you still need to start with static web.xml at minimum.
Ramesh..
----- Original Message -----
> Hi Ramesh / Michael,
>
> Thanks a lot for your responses.
>
> I have a one more question:
>
> In web.xml we are configuring the ODataService. Could you please let me know
> whether we can create a service dynamically without configuring in web.xml?
> Such as dynamically hosting the Odata service ?
>
> Could you please let me know your thoughts.
>
>
> Thanks & Regards,
> Murali.
> =================
>
> -----Original Message-----
> From: Mi Bo [mailto:mibo.asap@gmail.com <ma...@gmail.com> ] On
Behalf Of mibo
> Sent: Friday, September 05, 2014 9:38 PM
> To: user@olingo.apache.org <ma...@olingo.apache.org>
> Cc: Ilya Pupko
> Subject: Re: Apache Olingo Producer Application Run as standalone.
>
> Hi Murali,
>
> as Ramesh already mentioned, you need some service to provide the HTTP
> capabilities.
> As example in our sample archetype for Java annotations (see:
> http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html
<http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html> ) we
> use also a Jetty to run the OData service.
> It could be a good starting point to create a sample project with this
> archetype and call "mvn" to run it on a local Jetty instance to see how it
> works.
>
> Kind regards,
> Michael
>
> Am 05.09.2014 um 15:55 schrieb Ramesh Reddy <rareddy@redhat.com
<ma...@redhat.com> >:
>
> > If you are not going to use Server such as Tomcat, then you need think
> > about embedding some web server to provide the HTTP query capabilities. I
> > have used Jetty for testing previously.
> >
> > Ramesh..
> >
> > Hi Team,
> >
> > We are planning to use Olingo for hosting OData service.
> >
> > We want to run OData service as standalone but not via Webapplication
> > Server such as Tomcat.
> >
> > Could you please suggest a solution where we can run or Odata service as
> > standalone by creating a jar file and run via JVM.
> >
> >
> > Thanks & Regards,
> > Murali.
> > ===============
>
>
RE: Apache Olingo Producer Application Run as standalone.
Posted by Pankaj Arora <pa...@jitterbit.com>.
Thanks Michael. This really helped and we are going this way.
Pankaj
From: Bolz, Michael [mailto:michael.bolz@sap.com]
Sent: Tuesday, September 09, 2014 8:44 PM
To: user@olingo.apache.org
Subject: Re: Apache Olingo Producer Application Run as standalone.
Hi Pankaj,
On 09.09.2014, at 21:31, Pankaj Arora <pa...@jitterbit.com> wrote:
Hi Michael,
Thanks for helping us. Just to clarify, will it be enough to use read/write
methods of EntityProvider.
As I understand your use case to just convert our data into and from OData
XML format, yes it will be enough.
As I understand from tutorials, when the service is handled by service, it
must be doing many more steps before calling read/write methods.
This steps are mainly content negotiation and routing to the correct
read/write (based on called url), which you don't need if you just want to
convert known data.
Can you please help us by sharing some details on what will be sequence of
classes we might end up using/implementing to use the converter part per our
use case?
It will even help to have a checklist of classes/interfaces that might be
involved so while we dig in the code we have some guidance.
As mentioned you need the "EntityProvider" for the read/write and an
implementation of the "EdmProvider" for definition of your Data Model (see:
http://olingo.apache.org/doc/tutorials/basicread.html#implement-the-entity-d
ata-model-provider).
Think this should be the necessary parts for our use case.
Kind regards,
Michael
Pankaj
From: Bolz, Michael [mailto:michael.bolz@sap.com]
Sent: Tuesday, September 09, 2014 4:58 AM
To: user@olingo.apache.org
Cc: peter.lawrence@inova8.com; Ilya Pupko
Subject: Re: Apache Olingo Producer Application Run as standalone.
Hi Murali,
if you only want to convert data payload from and into OData format
(ATOM/XML) you can use the "EntityProvider" "read/write" methods.
Those converts data (specified via an EDM) from a Java Map into OData XML.
Or the other way OData XML into a Java Map.
Kind regards,
Michael
On 09 Sep 2014, at 08:39, Murali Sai Rama Krishna V <
<ma...@nalashaa.com> murali.v@nalashaa.com> wrote:
Hi,
Our use case for using Olingo is to use it as a "converter" to change the
OData compliant data to internal XML and vice versa. Couple of questions
which might help us review our architecture :
. Is that the right way to use your library or any other Odata
library? Or does Odata compliance/handling for data should be done at API
service layer?
. If Olingo can help us do conversion on payload extracted by our
API layer, can we use some internal OData parts of Olingo library to just
convert the data payload?
Murali.
=======
From: Peter Lawrence [ <ma...@inova8.com>
mailto:peter.lawrence@inova8.com]
Sent: Monday, September 08, 2014 11:18 PM
To: <ma...@olingo.apache.org> user@olingo.apache.org
Cc: Ilya Pupko
Subject: Re: Apache Olingo Producer Application Run as standalone.
Would the service resolution help:
<http://olingo.apache.org/doc/tutorials/Olingo_Tutorial_Advanced_Service_Res
olution.html>
http://olingo.apache.org/doc/tutorials/Olingo_Tutorial_Advanced_Service_Reso
lution.html
I have used this to support multiple OData endpoints with different versions
from the same service.
Of course I could also be creating greater confusion.
Peter J. Lawrence
inova8
Providing answers for users' information questions
Mobile: +1 330 631 3772 | Phone: +1 330 342 0582 | Skype: PeterJLawrence
Email: <ma...@inova8.com> peter.lawrence@inova8.com | Web:
<http://www.inova8.com/> www.inova8.com
LinkedIn: <http://www.linkedin.com/in/peterjohnlawrence>
http://www.linkedin.com/in/peterjohnlawrence
On Mon, Sep 8, 2014 at 1:34 PM, Ramesh Reddy < <ma...@redhat.com>
rareddy@redhat.com> wrote:
Murali,
web.xml is what bootstaps in your web application and provides the context
for your service. This lets you define the servlet where you can initialize
and manage your ODataService.
What is your expectation on dynamically creating it? There are options, but
you still need to start with static web.xml at minimum.
Ramesh..
----- Original Message -----
> Hi Ramesh / Michael,
>
> Thanks a lot for your responses.
>
> I have a one more question:
>
> In web.xml we are configuring the ODataService. Could you please let me
know
> whether we can create a service dynamically without configuring in
web.xml?
> Such as dynamically hosting the Odata service ?
>
> Could you please let me know your thoughts.
>
>
> Thanks & Regards,
> Murali.
> =================
>
> -----Original Message-----
> From: Mi Bo [mailto: <ma...@gmail.com> mibo.asap@gmail.com] On
Behalf Of mibo
> Sent: Friday, September 05, 2014 9:38 PM
> To: <ma...@olingo.apache.org> user@olingo.apache.org
> Cc: Ilya Pupko
> Subject: Re: Apache Olingo Producer Application Run as standalone.
>
> Hi Murali,
>
> as Ramesh already mentioned, you need some service to provide the HTTP
> capabilities.
> As example in our sample archetype for Java annotations (see:
>
<http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html>
http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html) we
> use also a Jetty to run the OData service.
> It could be a good starting point to create a sample project with this
> archetype and call "mvn" to run it on a local Jetty instance to see how it
> works.
>
> Kind regards,
> Michael
>
> Am 05.09.2014 um 15:55 schrieb Ramesh Reddy < <ma...@redhat.com>
rareddy@redhat.com>:
>
> > If you are not going to use Server such as Tomcat, then you need think
> > about embedding some web server to provide the HTTP query capabilities.
I
> > have used Jetty for testing previously.
> >
> > Ramesh..
> >
> > Hi Team,
> >
> > We are planning to use Olingo for hosting OData service.
> >
> > We want to run OData service as standalone but not via Webapplication
> > Server such as Tomcat.
> >
> > Could you please suggest a solution where we can run or Odata service as
> > standalone by creating a jar file and run via JVM.
> >
> >
> > Thanks & Regards,
> > Murali.
> > ===============
>
>
Re: Apache Olingo Producer Application Run as standalone.
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi Pankaj,
On 09.09.2014, at 21:31, Pankaj Arora <pa...@jitterbit.com> wrote:
> Hi Michael,
> Thanks for helping us. Just to clarify, will it be enough to use read/write methods of EntityProvider.
As I understand your use case to just convert our data into and from OData XML format, yes it will be enough.
> As I understand from tutorials, when the service is handled by service, it must be doing many more steps before calling read/write methods.
This steps are mainly content negotiation and routing to the correct read/write (based on called url), which you don't need if you just want to convert known data.
> Can you please help us by sharing some details on what will be sequence of classes we might end up using/implementing to use the converter part per our use case?
> It will even help to have a checklist of classes/interfaces that might be involved so while we dig in the code we have some guidance.
As mentioned you need the "EntityProvider" for the read/write and an implementation of the "EdmProvider" for definition of your Data Model (see: http://olingo.apache.org/doc/tutorials/basicread.html#implement-the-entity-data-model-provider).
Think this should be the necessary parts for our use case.
Kind regards,
Michael
>
> Pankaj
>
>
> From: Bolz, Michael [mailto:michael.bolz@sap.com]
> Sent: Tuesday, September 09, 2014 4:58 AM
> To: user@olingo.apache.org
> Cc: peter.lawrence@inova8.com; Ilya Pupko
> Subject: Re: Apache Olingo Producer Application Run as standalone.
>
> Hi Murali,
>
> if you only want to convert data payload from and into OData format (ATOM/XML) you can use the “EntityProvider” “read/write” methods.
> Those converts data (specified via an EDM) from a Java Map into OData XML.
> Or the other way OData XML into a Java Map.
>
> Kind regards,
> Michael
>
> On 09 Sep 2014, at 08:39, Murali Sai Rama Krishna V <mu...@nalashaa.com> wrote:
>
>
> Hi,
> Our use case for using Olingo is to use it as a "converter" to change the OData compliant data to internal XML and vice versa. Couple of questions which might help us review our architecture :
> · Is that the right way to use your library or any other Odata library? Or does Odata compliance/handling for data should be done at API service layer?
> · If Olingo can help us do conversion on payload extracted by our API layer, can we use some internal OData parts of Olingo library to just convert the data payload?
>
> Murali.
> =======
>
>
> From: Peter Lawrence [mailto:peter.lawrence@inova8.com]
> Sent: Monday, September 08, 2014 11:18 PM
> To: user@olingo.apache.org
> Cc: Ilya Pupko
> Subject: Re: Apache Olingo Producer Application Run as standalone.
>
> Would the service resolution help: http://olingo.apache.org/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html
>
> I have used this to support multiple OData endpoints with different versions from the same service.
>
> Of course I could also be creating greater confusion.
>
> Peter J. Lawrence
> inova8
> Providing answers for users' information questions
> Mobile: +1 330 631 3772 | Phone: +1 330 342 0582 | Skype: PeterJLawrence
> Email: peter.lawrence@inova8.com | Web: www.inova8.com
> LinkedIn: http://www.linkedin.com/in/peterjohnlawrence
>
> On Mon, Sep 8, 2014 at 1:34 PM, Ramesh Reddy <ra...@redhat.com> wrote:
> Murali,
>
> web.xml is what bootstaps in your web application and provides the context for your service. This lets you define the servlet where you can initialize and manage your ODataService.
>
> What is your expectation on dynamically creating it? There are options, but you still need to start with static web.xml at minimum.
>
> Ramesh..
>
> ----- Original Message -----
> > Hi Ramesh / Michael,
> >
> > Thanks a lot for your responses.
> >
> > I have a one more question:
> >
> > In web.xml we are configuring the ODataService. Could you please let me know
> > whether we can create a service dynamically without configuring in web.xml?
> > Such as dynamically hosting the Odata service ?
> >
> > Could you please let me know your thoughts.
> >
> >
> > Thanks & Regards,
> > Murali.
> > =================
> >
> > -----Original Message-----
> > From: Mi Bo [mailto:mibo.asap@gmail.com] On Behalf Of mibo
> > Sent: Friday, September 05, 2014 9:38 PM
> > To: user@olingo.apache.org
> > Cc: Ilya Pupko
> > Subject: Re: Apache Olingo Producer Application Run as standalone.
> >
> > Hi Murali,
> >
> > as Ramesh already mentioned, you need some service to provide the HTTP
> > capabilities.
> > As example in our sample archetype for Java annotations (see:
> > http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html) we
> > use also a Jetty to run the OData service.
> > It could be a good starting point to create a sample project with this
> > archetype and call "mvn" to run it on a local Jetty instance to see how it
> > works.
> >
> > Kind regards,
> > Michael
> >
> > Am 05.09.2014 um 15:55 schrieb Ramesh Reddy <ra...@redhat.com>:
> >
> > > If you are not going to use Server such as Tomcat, then you need think
> > > about embedding some web server to provide the HTTP query capabilities. I
> > > have used Jetty for testing previously.
> > >
> > > Ramesh..
> > >
> > > Hi Team,
> > >
> > > We are planning to use Olingo for hosting OData service.
> > >
> > > We want to run OData service as standalone but not via Webapplication
> > > Server such as Tomcat.
> > >
> > > Could you please suggest a solution where we can run or Odata service as
> > > standalone by creating a jar file and run via JVM.
> > >
> > >
> > > Thanks & Regards,
> > > Murali.
> > > ===============
> >
> >
RE: Apache Olingo Producer Application Run as standalone.
Posted by Pankaj Arora <pa...@jitterbit.com>.
Hi Michael,
Thanks for helping us. Just to clarify, will it be enough to use read/write
methods of EntityProvider. As I understand from tutorials, when the service
is handled by service, it must be doing many more steps before calling
read/write methods. Can you please help us by sharing some details on what
will be sequence of classes we might end up using/implementing to use the
converter part per our use case? It will even help to have a checklist of
classes/interfaces that might be involved so while we dig in the code we
have some guidance.
Pankaj
From: Bolz, Michael [mailto:michael.bolz@sap.com]
Sent: Tuesday, September 09, 2014 4:58 AM
To: user@olingo.apache.org
Cc: peter.lawrence@inova8.com; Ilya Pupko
Subject: Re: Apache Olingo Producer Application Run as standalone.
Hi Murali,
if you only want to convert data payload from and into OData format
(ATOM/XML) you can use the "EntityProvider" "read/write" methods.
Those converts data (specified via an EDM) from a Java Map into OData XML.
Or the other way OData XML into a Java Map.
Kind regards,
Michael
On 09 Sep 2014, at 08:39, Murali Sai Rama Krishna V <mu...@nalashaa.com>
wrote:
Hi,
Our use case for using Olingo is to use it as a "converter" to change the
OData compliant data to internal XML and vice versa. Couple of questions
which might help us review our architecture :
. Is that the right way to use your library or any other Odata
library? Or does Odata compliance/handling for data should be done at API
service layer?
. If Olingo can help us do conversion on payload extracted by our
API layer, can we use some internal OData parts of Olingo library to just
convert the data payload?
Murali.
=======
From: Peter Lawrence [mailto:peter.lawrence@inova8.com]
Sent: Monday, September 08, 2014 11:18 PM
To: user@olingo.apache.org
Cc: Ilya Pupko
Subject: Re: Apache Olingo Producer Application Run as standalone.
Would the service resolution help:
<http://olingo.apache.org/doc/tutorials/Olingo_Tutorial_Advanced_Service_Res
olution.html>
http://olingo.apache.org/doc/tutorials/Olingo_Tutorial_Advanced_Service_Reso
lution.html
I have used this to support multiple OData endpoints with different versions
from the same service.
Of course I could also be creating greater confusion.
Peter J. Lawrence
inova8
Providing answers for users' information questions
Mobile: +1 330 631 3772 | Phone: +1 330 342 0582 | Skype: PeterJLawrence
Email: <ma...@inova8.com> peter.lawrence@inova8.com | Web:
<http://www.inova8.com/> www.inova8.com
LinkedIn: <http://www.linkedin.com/in/peterjohnlawrence>
http://www.linkedin.com/in/peterjohnlawrence
On Mon, Sep 8, 2014 at 1:34 PM, Ramesh Reddy < <ma...@redhat.com>
rareddy@redhat.com> wrote:
Murali,
web.xml is what bootstaps in your web application and provides the context
for your service. This lets you define the servlet where you can initialize
and manage your ODataService.
What is your expectation on dynamically creating it? There are options, but
you still need to start with static web.xml at minimum.
Ramesh..
----- Original Message -----
> Hi Ramesh / Michael,
>
> Thanks a lot for your responses.
>
> I have a one more question:
>
> In web.xml we are configuring the ODataService. Could you please let me
know
> whether we can create a service dynamically without configuring in
web.xml?
> Such as dynamically hosting the Odata service ?
>
> Could you please let me know your thoughts.
>
>
> Thanks & Regards,
> Murali.
> =================
>
> -----Original Message-----
> From: Mi Bo [mailto: <ma...@gmail.com> mibo.asap@gmail.com] On
Behalf Of mibo
> Sent: Friday, September 05, 2014 9:38 PM
> To: <ma...@olingo.apache.org> user@olingo.apache.org
> Cc: Ilya Pupko
> Subject: Re: Apache Olingo Producer Application Run as standalone.
>
> Hi Murali,
>
> as Ramesh already mentioned, you need some service to provide the HTTP
> capabilities.
> As example in our sample archetype for Java annotations (see:
>
<http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html>
http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html) we
> use also a Jetty to run the OData service.
> It could be a good starting point to create a sample project with this
> archetype and call "mvn" to run it on a local Jetty instance to see how it
> works.
>
> Kind regards,
> Michael
>
> Am 05.09.2014 um 15:55 schrieb Ramesh Reddy < <ma...@redhat.com>
rareddy@redhat.com>:
>
> > If you are not going to use Server such as Tomcat, then you need think
> > about embedding some web server to provide the HTTP query capabilities.
I
> > have used Jetty for testing previously.
> >
> > Ramesh..
> >
> > Hi Team,
> >
> > We are planning to use Olingo for hosting OData service.
> >
> > We want to run OData service as standalone but not via Webapplication
> > Server such as Tomcat.
> >
> > Could you please suggest a solution where we can run or Odata service as
> > standalone by creating a jar file and run via JVM.
> >
> >
> > Thanks & Regards,
> > Murali.
> > ===============
>
>
Re: Apache Olingo Producer Application Run as standalone.
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi Murali,
if you only want to convert data payload from and into OData format (ATOM/XML) you can use the “EntityProvider” “read/write” methods.
Those converts data (specified via an EDM) from a Java Map into OData XML.
Or the other way OData XML into a Java Map.
Kind regards,
Michael
On 09 Sep 2014, at 08:39, Murali Sai Rama Krishna V <mu...@nalashaa.com> wrote:
> Hi,
> Our use case for using Olingo is to use it as a "converter" to change the OData compliant data to internal XML and vice versa. Couple of questions which might help us review our architecture :
> · Is that the right way to use your library or any other Odata library? Or does Odata compliance/handling for data should be done at API service layer?
> · If Olingo can help us do conversion on payload extracted by our API layer, can we use some internal OData parts of Olingo library to just convert the data payload?
>
> Murali.
> =======
>
>
> From: Peter Lawrence [mailto:peter.lawrence@inova8.com]
> Sent: Monday, September 08, 2014 11:18 PM
> To: user@olingo.apache.org
> Cc: Ilya Pupko
> Subject: Re: Apache Olingo Producer Application Run as standalone.
>
> Would the service resolution help: http://olingo.apache.org/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html
>
> I have used this to support multiple OData endpoints with different versions from the same service.
>
> Of course I could also be creating greater confusion.
>
> Peter J. Lawrence
> inova8
> Providing answers for users' information questions
> Mobile: +1 330 631 3772 | Phone: +1 330 342 0582 | Skype: PeterJLawrence
> Email: peter.lawrence@inova8.com | Web: www.inova8.com
> LinkedIn: http://www.linkedin.com/in/peterjohnlawrence
>
> On Mon, Sep 8, 2014 at 1:34 PM, Ramesh Reddy <ra...@redhat.com> wrote:
> Murali,
>
> web.xml is what bootstaps in your web application and provides the context for your service. This lets you define the servlet where you can initialize and manage your ODataService.
>
> What is your expectation on dynamically creating it? There are options, but you still need to start with static web.xml at minimum.
>
> Ramesh..
>
> ----- Original Message -----
> > Hi Ramesh / Michael,
> >
> > Thanks a lot for your responses.
> >
> > I have a one more question:
> >
> > In web.xml we are configuring the ODataService. Could you please let me know
> > whether we can create a service dynamically without configuring in web.xml?
> > Such as dynamically hosting the Odata service ?
> >
> > Could you please let me know your thoughts.
> >
> >
> > Thanks & Regards,
> > Murali.
> > =================
> >
> > -----Original Message-----
> > From: Mi Bo [mailto:mibo.asap@gmail.com] On Behalf Of mibo
> > Sent: Friday, September 05, 2014 9:38 PM
> > To: user@olingo.apache.org
> > Cc: Ilya Pupko
> > Subject: Re: Apache Olingo Producer Application Run as standalone.
> >
> > Hi Murali,
> >
> > as Ramesh already mentioned, you need some service to provide the HTTP
> > capabilities.
> > As example in our sample archetype for Java annotations (see:
> > http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html) we
> > use also a Jetty to run the OData service.
> > It could be a good starting point to create a sample project with this
> > archetype and call "mvn" to run it on a local Jetty instance to see how it
> > works.
> >
> > Kind regards,
> > Michael
> >
> > Am 05.09.2014 um 15:55 schrieb Ramesh Reddy <ra...@redhat.com>:
> >
> > > If you are not going to use Server such as Tomcat, then you need think
> > > about embedding some web server to provide the HTTP query capabilities. I
> > > have used Jetty for testing previously.
> > >
> > > Ramesh..
> > >
> > > Hi Team,
> > >
> > > We are planning to use Olingo for hosting OData service.
> > >
> > > We want to run OData service as standalone but not via Webapplication
> > > Server such as Tomcat.
> > >
> > > Could you please suggest a solution where we can run or Odata service as
> > > standalone by creating a jar file and run via JVM.
> > >
> > >
> > > Thanks & Regards,
> > > Murali.
> > > ===============
> >
> >
RE: Apache Olingo Producer Application Run as standalone.
Posted by Murali Sai Rama Krishna V <mu...@nalashaa.com>.
Hi,
Our use case for using Olingo is to use it as a "converter" to change the OData compliant data to internal XML and vice versa. Couple of questions which might help us review our architecture :
· Is that the right way to use your library or any other Odata library? Or does Odata compliance/handling for data should be done at API service layer?
· If Olingo can help us do conversion on payload extracted by our API layer, can we use some internal OData parts of Olingo library to just convert the data payload?
Murali.
=======
From: Peter Lawrence [mailto:peter.lawrence@inova8.com]
Sent: Monday, September 08, 2014 11:18 PM
To: user@olingo.apache.org
Cc: Ilya Pupko
Subject: Re: Apache Olingo Producer Application Run as standalone.
Would the service resolution help: http://olingo.apache.org/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html
I have used this to support multiple OData endpoints with different versions from the same service.
Of course I could also be creating greater confusion.
Peter J. Lawrence
inova8
Providing answers for users' information questions
Mobile: +1 330 631 3772 | Phone: +1 330 342 0582 | Skype: PeterJLawrence
Email: peter.lawrence@inova8.com<ma...@inova8.com> | Web: www.inova8.com<http://www.inova8.com>
LinkedIn: http://www.linkedin.com/in/peterjohnlawrence
On Mon, Sep 8, 2014 at 1:34 PM, Ramesh Reddy <ra...@redhat.com>> wrote:
Murali,
web.xml is what bootstaps in your web application and provides the context for your service. This lets you define the servlet where you can initialize and manage your ODataService.
What is your expectation on dynamically creating it? There are options, but you still need to start with static web.xml at minimum.
Ramesh..
----- Original Message -----
> Hi Ramesh / Michael,
>
> Thanks a lot for your responses.
>
> I have a one more question:
>
> In web.xml we are configuring the ODataService. Could you please let me know
> whether we can create a service dynamically without configuring in web.xml?
> Such as dynamically hosting the Odata service ?
>
> Could you please let me know your thoughts.
>
>
> Thanks & Regards,
> Murali.
> =================
>
> -----Original Message-----
> From: Mi Bo [mailto:mibo.asap@gmail.com<ma...@gmail.com>] On Behalf Of mibo
> Sent: Friday, September 05, 2014 9:38 PM
> To: user@olingo.apache.org<ma...@olingo.apache.org>
> Cc: Ilya Pupko
> Subject: Re: Apache Olingo Producer Application Run as standalone.
>
> Hi Murali,
>
> as Ramesh already mentioned, you need some service to provide the HTTP
> capabilities.
> As example in our sample archetype for Java annotations (see:
> http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html) we
> use also a Jetty to run the OData service.
> It could be a good starting point to create a sample project with this
> archetype and call "mvn" to run it on a local Jetty instance to see how it
> works.
>
> Kind regards,
> Michael
>
> Am 05.09.2014 um 15:55 schrieb Ramesh Reddy <ra...@redhat.com>>:
>
> > If you are not going to use Server such as Tomcat, then you need think
> > about embedding some web server to provide the HTTP query capabilities. I
> > have used Jetty for testing previously.
> >
> > Ramesh..
> >
> > Hi Team,
> >
> > We are planning to use Olingo for hosting OData service.
> >
> > We want to run OData service as standalone but not via Webapplication
> > Server such as Tomcat.
> >
> > Could you please suggest a solution where we can run or Odata service as
> > standalone by creating a jar file and run via JVM.
> >
> >
> > Thanks & Regards,
> > Murali.
> > ===============
>
>
Re: Apache Olingo Producer Application Run as standalone.
Posted by Peter Lawrence <pe...@inova8.com>.
Would the service resolution help:
http://olingo.apache.org/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html
I have used this to support multiple OData endpoints with different
versions from the same service.
Of course I could also be creating greater confusion.
*Peter J. Lawrence*
*inova8*
*Providing answers for users' information questions*
*Mobile:* +1 330 631 3772 | *Phone:* +1 330 342 0582 | *Skype:*
PeterJLawrence
*Email:* peter.lawrence@inova8.com | *Web:* www.inova8.com
*LinkedIn: **http://www.linkedin.com/in/peterjohnlawrence
<http://www.linkedin.com/in/peterjohnlawrence>*
On Mon, Sep 8, 2014 at 1:34 PM, Ramesh Reddy <ra...@redhat.com> wrote:
> Murali,
>
> web.xml is what bootstaps in your web application and provides the context
> for your service. This lets you define the servlet where you can initialize
> and manage your ODataService.
>
> What is your expectation on dynamically creating it? There are options,
> but you still need to start with static web.xml at minimum.
>
> Ramesh..
>
> ----- Original Message -----
> > Hi Ramesh / Michael,
> >
> > Thanks a lot for your responses.
> >
> > I have a one more question:
> >
> > In web.xml we are configuring the ODataService. Could you please let me
> know
> > whether we can create a service dynamically without configuring in
> web.xml?
> > Such as dynamically hosting the Odata service ?
> >
> > Could you please let me know your thoughts.
> >
> >
> > Thanks & Regards,
> > Murali.
> > =================
> >
> > -----Original Message-----
> > From: Mi Bo [mailto:mibo.asap@gmail.com] On Behalf Of mibo
> > Sent: Friday, September 05, 2014 9:38 PM
> > To: user@olingo.apache.org
> > Cc: Ilya Pupko
> > Subject: Re: Apache Olingo Producer Application Run as standalone.
> >
> > Hi Murali,
> >
> > as Ramesh already mentioned, you need some service to provide the HTTP
> > capabilities.
> > As example in our sample archetype for Java annotations (see:
> > http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html)
> we
> > use also a Jetty to run the OData service.
> > It could be a good starting point to create a sample project with this
> > archetype and call "mvn" to run it on a local Jetty instance to see how
> it
> > works.
> >
> > Kind regards,
> > Michael
> >
> > Am 05.09.2014 um 15:55 schrieb Ramesh Reddy <ra...@redhat.com>:
> >
> > > If you are not going to use Server such as Tomcat, then you need think
> > > about embedding some web server to provide the HTTP query
> capabilities. I
> > > have used Jetty for testing previously.
> > >
> > > Ramesh..
> > >
> > > Hi Team,
> > >
> > > We are planning to use Olingo for hosting OData service.
> > >
> > > We want to run OData service as standalone but not via Webapplication
> > > Server such as Tomcat.
> > >
> > > Could you please suggest a solution where we can run or Odata service
> as
> > > standalone by creating a jar file and run via JVM.
> > >
> > >
> > > Thanks & Regards,
> > > Murali.
> > > ===============
> >
> >
>
Re: Apache Olingo Producer Application Run as standalone.
Posted by Ramesh Reddy <ra...@redhat.com>.
Murali,
web.xml is what bootstaps in your web application and provides the context for your service. This lets you define the servlet where you can initialize and manage your ODataService.
What is your expectation on dynamically creating it? There are options, but you still need to start with static web.xml at minimum.
Ramesh..
----- Original Message -----
> Hi Ramesh / Michael,
>
> Thanks a lot for your responses.
>
> I have a one more question:
>
> In web.xml we are configuring the ODataService. Could you please let me know
> whether we can create a service dynamically without configuring in web.xml?
> Such as dynamically hosting the Odata service ?
>
> Could you please let me know your thoughts.
>
>
> Thanks & Regards,
> Murali.
> =================
>
> -----Original Message-----
> From: Mi Bo [mailto:mibo.asap@gmail.com] On Behalf Of mibo
> Sent: Friday, September 05, 2014 9:38 PM
> To: user@olingo.apache.org
> Cc: Ilya Pupko
> Subject: Re: Apache Olingo Producer Application Run as standalone.
>
> Hi Murali,
>
> as Ramesh already mentioned, you need some service to provide the HTTP
> capabilities.
> As example in our sample archetype for Java annotations (see:
> http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html) we
> use also a Jetty to run the OData service.
> It could be a good starting point to create a sample project with this
> archetype and call "mvn" to run it on a local Jetty instance to see how it
> works.
>
> Kind regards,
> Michael
>
> Am 05.09.2014 um 15:55 schrieb Ramesh Reddy <ra...@redhat.com>:
>
> > If you are not going to use Server such as Tomcat, then you need think
> > about embedding some web server to provide the HTTP query capabilities. I
> > have used Jetty for testing previously.
> >
> > Ramesh..
> >
> > Hi Team,
> >
> > We are planning to use Olingo for hosting OData service.
> >
> > We want to run OData service as standalone but not via Webapplication
> > Server such as Tomcat.
> >
> > Could you please suggest a solution where we can run or Odata service as
> > standalone by creating a jar file and run via JVM.
> >
> >
> > Thanks & Regards,
> > Murali.
> > ===============
>
>
Re: Apache Olingo Producer Application Run as standalone.
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi Murali,
I currently know no java framework which provide HTTP capabilities for such a use case.
To realize such a dynamical service I think you have to implement / handle the HTTP request by yourself and then forwards it to the "ODataRequestHandler" as "ODataRequest".
Kind regards,
Michael
On 08.09.2014, at 16:53, Murali Sai Rama Krishna V <mu...@nalashaa.com> wrote:
> Hi Ramesh / Michael,
>
> Thanks a lot for your responses.
>
> I have a one more question:
>
> In web.xml we are configuring the ODataService. Could you please let me know whether we can create a service dynamically without configuring in web.xml?
> Such as dynamically hosting the Odata service ?
>
> Could you please let me know your thoughts.
>
>
> Thanks & Regards,
> Murali.
> =================
>
> -----Original Message-----
> From: Mi Bo [mailto:mibo.asap@gmail.com] On Behalf Of mibo
> Sent: Friday, September 05, 2014 9:38 PM
> To: user@olingo.apache.org
> Cc: Ilya Pupko
> Subject: Re: Apache Olingo Producer Application Run as standalone.
>
> Hi Murali,
>
> as Ramesh already mentioned, you need some service to provide the HTTP capabilities.
> As example in our sample archetype for Java annotations (see: http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html) we use also a Jetty to run the OData service.
> It could be a good starting point to create a sample project with this archetype and call "mvn" to run it on a local Jetty instance to see how it works.
>
> Kind regards,
> Michael
>
> Am 05.09.2014 um 15:55 schrieb Ramesh Reddy <ra...@redhat.com>:
>
>> If you are not going to use Server such as Tomcat, then you need think about embedding some web server to provide the HTTP query capabilities. I have used Jetty for testing previously.
>>
>> Ramesh..
>>
>> Hi Team,
>>
>> We are planning to use Olingo for hosting OData service.
>>
>> We want to run OData service as standalone but not via Webapplication Server such as Tomcat.
>>
>> Could you please suggest a solution where we can run or Odata service as standalone by creating a jar file and run via JVM.
>>
>>
>> Thanks & Regards,
>> Murali.
>> ===============
>
RE: Apache Olingo Producer Application Run as standalone.
Posted by Murali Sai Rama Krishna V <mu...@nalashaa.com>.
Hi Ramesh / Michael,
Thanks a lot for your responses.
I have a one more question:
In web.xml we are configuring the ODataService. Could you please let me know whether we can create a service dynamically without configuring in web.xml?
Such as dynamically hosting the Odata service ?
Could you please let me know your thoughts.
Thanks & Regards,
Murali.
=================
-----Original Message-----
From: Mi Bo [mailto:mibo.asap@gmail.com] On Behalf Of mibo
Sent: Friday, September 05, 2014 9:38 PM
To: user@olingo.apache.org
Cc: Ilya Pupko
Subject: Re: Apache Olingo Producer Application Run as standalone.
Hi Murali,
as Ramesh already mentioned, you need some service to provide the HTTP capabilities.
As example in our sample archetype for Java annotations (see: http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html) we use also a Jetty to run the OData service.
It could be a good starting point to create a sample project with this archetype and call "mvn" to run it on a local Jetty instance to see how it works.
Kind regards,
Michael
Am 05.09.2014 um 15:55 schrieb Ramesh Reddy <ra...@redhat.com>:
> If you are not going to use Server such as Tomcat, then you need think about embedding some web server to provide the HTTP query capabilities. I have used Jetty for testing previously.
>
> Ramesh..
>
> Hi Team,
>
> We are planning to use Olingo for hosting OData service.
>
> We want to run OData service as standalone but not via Webapplication Server such as Tomcat.
>
> Could you please suggest a solution where we can run or Odata service as standalone by creating a jar file and run via JVM.
>
>
> Thanks & Regards,
> Murali.
> ===============
Re: Apache Olingo Producer Application Run as standalone.
Posted by mibo <mi...@apache.org>.
Hi Murali,
as Ramesh already mentioned, you need some service to provide the HTTP capabilities.
As example in our sample archetype for Java annotations (see: http://olingo.apache.org/doc/tutorials/AnnotationProcessorExtension.html) we use also a Jetty to run the OData service.
It could be a good starting point to create a sample project with this archetype and call "mvn" to run it on a local Jetty instance to see how it works.
Kind regards,
Michael
Am 05.09.2014 um 15:55 schrieb Ramesh Reddy <ra...@redhat.com>:
> If you are not going to use Server such as Tomcat, then you need think about embedding some web server to provide the HTTP query capabilities. I have used Jetty for testing previously.
>
> Ramesh..
>
> Hi Team,
>
> We are planning to use Olingo for hosting OData service.
>
> We want to run OData service as standalone but not via Webapplication Server such as Tomcat.
>
> Could you please suggest a solution where we can run or Odata service as standalone by creating a jar file and run via JVM.
>
>
> Thanks & Regards,
> Murali.
> ===============
Re: Apache Olingo Producer Application Run as standalone.
Posted by Ramesh Reddy <ra...@redhat.com>.
If you are not going to use Server such as Tomcat, then you need think about embedding some web server to provide the HTTP query capabilities. I have used Jetty for testing previously.
Ramesh..
----- Original Message -----
> Hi Team,
> We are planning to use Olingo for hosting OData service.
> We want to run OData service as standalone but not via Webapplication Server
> such as Tomcat.
> Could you please suggest a solution where we can run or Odata service as
> standalone by creating a jar file and run via JVM.
> Thanks & Regards,
> Murali.
> ===============