You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Luis Arce <lu...@mc3d.cl> on 2020/01/10 23:43:45 UTC
Please a reviewer for the case IGNITE-12518
Dear community,
I made modifications to the module rest-http.
It works correctly.
Is possible if anybody take my case for the review?
The modifications are:
Support for webpages (test with jsf and primefaces), support for root
context.
Support to JaxWS with RI version.
Support for access to Ignite database with JNDI and basic connection
pooling'
Se despide Atentamente,
*Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
09-57861903
Linkedin:
https://cl.linkedin.com/in/luisalejandroarcemartinez
Re: Please a reviewer for the case IGNITE-12518
Posted by Luis Arce <lu...@mc3d.cl>.
Hi Saikat, Denis,
I'll start to migrate the development to maven for your test.
Best regards,
*Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
09-57861903
Linkedin:
https://cl.linkedin.com/in/luisalejandroarcemartinez
El sáb., 25 ene. 2020 a las 23:24, Saikat Maitra (<sa...@gmail.com>)
escribió:
> Hi, Luis, Denis
>
> We can take up the changes in either Ignite-extensions repo as new
> independent module or as part of ignite repo inside rest-http module but
> since the changes are not in git pull request it is hard for us to review
> and share feedback.
>
> 1. There are jar dependencies shared in the jira ticket[1] but we do not
> accept jar instead we will require the changes in maven pom.xml file.
>
> 2. There are also changes in GridJettyRestHandler and GridJettyRestProtocol
> but there are no corresponding tests for validation. It will be better if
> required tests are added as part of PR.
>
> 3. It is also unclear how do we incorporate the changes mentioned in the
> jira related to web.xml file, Do they need to be part of README.md?
>
> Please let me know if I can help in any way with PR process.
>
> Our docs for contribution are available here [2]
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12518
> [2] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>
>
> Regards,
> Saikat
>
>
>
>
>
>
>
> On Fri, Jan 24, 2020 at 11:09 AM Denis Magda <dm...@apache.org> wrote:
>
> > Hi Luis,
> >
> > Presently, the community is on the route of Ignite simplification. We're
> > trying to define Ignite core that has minimal dependencies with 3rd party
> > libraries. That also led to the modularization initiative [1] with the
> > first results in the form of Ignite Extensions repository where we're
> > moving all 3rd party integrations.
> >
> > Saikat, do you think Luis's contribution needs to reside in the
> extensions
> > repository?
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization
> >
> > -
> > Denis
> >
> >
> > On Thu, Jan 23, 2020 at 8:48 PM Luis Arce <lu...@mc3d.cl> wrote:
> >
> > > Hi Saikat,
> > > Thanks for you response:
> > >
> > > My system need a web server for work. i work correctly with Wildfly
> and i
> > > use Ignite as Backend for database.
> > > My problem is the combination of both is around 6 GB RAM for work in
> the
> > > VPS.
> > > For this reason i modified the unique plugin with webserver inside
> > > (rest-http module).
> > > The change enabled the possibility for use only 3GB RAM in a VPS (
> > > vpsserver.com) saving money and enabling horizontal scalling.
> > > I shared this change in the Jira ticket touching the two classes of
> > > rest-http plugin.
> > > The change has less impact (programaticly), the point is the library
> > > dependencies (quantity of jars).
> > >
> > > It change has sense for you?, i think is a util because that
> technologies
> > > dont has present inside of ignite currently and is friendly with the
> code
> > > of rest-ignite.
> > >
> > >
> > >
> > >
> > > Best regards,
> > >
> > >
> > > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> > > 09-57861903
> > > Linkedin:
> > > https://cl.linkedin.com/in/luisalejandroarcemartinez
> > >
> > >
> > >
> > >
> > >
> > > El mié., 22 ene. 2020 a las 0:38, Saikat Maitra (<
> > saikat.maitra@gmail.com
> > > >)
> > > escribió:
> > >
> > > > Hello Luis,
> > > >
> > > > Thank you for your email. You can plan to create a separate
> application
> > > for
> > > > jaxws service and use any build tools like gradle or maven to define
> > your
> > > > dependencies.
> > > >
> > > > Please find below some of the performance tips related to Ignite
> > > >
> > > > https://apacheignite.readme.io/docs/durable-memory-tuning
> > > >
> > > > You can use IgniteClient in your service and can connect to remote
> > > cluster
> > > > of Apache Ignite for data persistence.
> > > >
> > > > Can you please correct my understanding on the usage of
> > ignite-rest-http
> > > > in IGNITE-12518, I see the dependencies you have mentioned are
> related
> > to
> > > > your project and my understanding is you are trying to use
> > > ignite-rest-http
> > > > jetty server for running your application. My understanding is this
> > > change
> > > > will make ignite-rest-http very large jar file with dependencies
> > > > like tomcat-servlet-api-9.0.10.jar may not needed outside of your
> > project
> > > > scope.
> > > >
> > > > Please let me know your thoughts.
> > > >
> > > > Regards,
> > > > Saikat
> > > >
> > > >
> > > > On Sun, Jan 19, 2020 at 9:47 PM Luis Arce <lu...@mc3d.cl> wrote:
> > > >
> > > > > Hi Saikat,
> > > > > I agree, the impact of changes is bigger on the module.
> > > > > I have a question: If i need create a jaxws service what is your
> > > > > recomendation?
> > > > > My motivation for the changes is the next:
> > > > > *Introduction.*
> > > > > A few time ago i design a ABB for traceability for Oracle Service
> Bus
> > > > with
> > > > > the objective of detecting failures points in many processes of a
> > > > customer.
> > > > > In first instance my team worked with rest-http module in ignite
> 2.4
> > > with
> > > > > poor results, the quantity of TPS was 4.Then we make a
> implementation
> > > of
> > > > > Rest service inside Apache Tomcat and call to Apache Ignite
> directly
> > to
> > > > > Database with persistence activated. This change, enabled the
> > > possibility
> > > > > for work with 4 environment of the customer (Development, Testing,
> > QA,
> > > > > Production) with 8GB of RAM in the machine, the configuration of
> the
> > > > client
> > > > > had a Oracle Portal for the View layer, EJB for composition of the
> > > > > controller layer, and OSB for the integration the TPS of the client
> > are
> > > > > biggest.
> > > > >
> > > > > *AS-IS*
> > > > >
> > > > > [image: imagen.png]
> > > > >
> > > > > *To Be roadmap*
> > > > >
> > > > > [image: imagen.png]
> > > > >
> > > > > With the ignite modification published in Jira is possible run JSF
> > for
> > > > run
> > > > > my reports and forms, JaxWS for the service SOAP and Jersey for
> Rest
> > (i
> > > > > start modification in this task).
> > > > > The code published in Jira have capabilites for work with
> Primefaces
> > > > > (tested ok), JaxWS (tested ok), but jersey is not included yet.
> > > > >
> > > > > Best regards,
> > > > >
> > > > >
> > > > > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> > > > > 09-57861903
> > > > > Linkedin:
> > > > > https://cl.linkedin.com/in/luisalejandroarcemartinez
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > El jue., 16 ene. 2020 a las 0:25, Saikat Maitra (<
> > > > saikat.maitra@gmail.com>)
> > > > > escribió:
> > > > >
> > > > >> Hi Luis,
> > > > >>
> > > > >> Thank you for sharing the details on the changes. I reviewed the
> > > > >> dependencies that you shared in the jira issue and wanted to
> discuss
> > > on
> > > > >> the
> > > > >> changes.
> > > > >>
> > > > >> The purpose of ignite-rest-http is to provide a web based
> interface
> > to
> > > > >> easily access and use the ignite features and the changes you
> > > suggested
> > > > >> can
> > > > >> be built as part of separate application and ignite-rest-http can
> be
> > > > used
> > > > >> as an add on dependency. This will help keep ignite-rest-http
> module
> > > as
> > > > >> minimal and thin as possible.
> > > > >>
> > > > >> Please review and share your thoughts.
> > > > >>
> > > > >> Regards,
> > > > >> Saikat
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> On Mon, Jan 13, 2020 at 7:24 PM Luis Arce <lu...@mc3d.cl>
> > wrote:
> > > > >>
> > > > >> > Hi Saikat,
> > > > >> > I add information for evidence for the changes of ignite
> rest-http
> > > > >> module.
> > > > >> >
> > > > >> > 1. Can you please share more information on the issue that will
> be
> > > > >> resolved
> > > > >> > with this change?
> > > > >> > R: This change add the possibility for publish war files with
> > > > webpages
> > > > >> in
> > > > >> > JSF or webservices JaxWS inside of the jetty server embedded.
> > > > >> > When the WAR file is loade automatically attached the JNDI for
> > > lockup
> > > > to
> > > > >> > Ignite DataBase to the context of the page.
> > > > >> > (I have a mvc4 application with ignite as a backend, with it
> > change
> > > i
> > > > >> dont
> > > > >> > need a primary web server).
> > > > >> >
> > > > >> > [image: imagen.png]
> > > > >> >
> > > > >> > [image: imagen.png]
> > > > >> >
> > > > >> > My webpage
> > > > >> > [image: imagen.png]
> > > > >> >
> > > > >> > My mvc4
> > > > >> > [image: imagen.png]
> > > > >> >
> > > > >> > The WebService
> > > > >> >
> > > > >> > [image: imagen.png]
> > > > >> > The WSDL
> > > > >> > [image: imagen.png]
> > > > >> >
> > > > >> > SoapUI
> > > > >> > [image: imagen.png]
> > > > >> >
> > > > >> > TestSuite SoapUI
> > > > >> > [image: imagen.png]
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y
> > Gestión
> > > > >> > 09-57861903
> > > > >> > Linkedin:
> > > > >> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > El dom., 12 ene. 2020 a las 14:43, Saikat Maitra (<
> > > > >> saikat.maitra@gmail.com>)
> > > > >> > escribió:
> > > > >> >
> > > > >> >> Hi Luis,
> > > > >> >>
> > > > >> >> 1. Can you please share more information on the issue that will
> > be
> > > > >> >> resolved
> > > > >> >> with this change?
> > > > >> >> 2. To accommodate the change, would you be able to raise a PR
> > > please.
> > > > >> >> Please take a look into the PR process
> > > > >> >>
> > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > > >> >> 3. Can you please add tests and execute the related testsuite
> in
> > > > >> teamcity
> > > > >> >> https://ci.ignite.apache.org/
> > > > >> >>
> > > > >> >> Regards,
> > > > >> >> Saikat
> > > > >> >>
> > > > >> >> On Fri, Jan 10, 2020 at 5:39 PM Luis Arce <lu...@mc3d.cl>
> > > wrote:
> > > > >> >>
> > > > >> >> > Dear community,
> > > > >> >> >
> > > > >> >> > I made modifications to the module rest-http.
> > > > >> >> > It works correctly.
> > > > >> >> > Is possible if anybody take my case for the review?
> > > > >> >> >
> > > > >> >> > The modifications are:
> > > > >> >> > Support for webpages (test with jsf and primefaces), support
> > for
> > > > root
> > > > >> >> > context.
> > > > >> >> > Support to JaxWS with RI version.
> > > > >> >> > Support for access to Ignite database with JNDI and basic
> > > > connection
> > > > >> >> > pooling'
> > > > >> >> >
> > > > >> >> > Se despide Atentamente,
> > > > >> >> >
> > > > >> >> >
> > > > >> >> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y
> > > Gestión
> > > > >> >> > 09-57861903
> > > > >> >> > Linkedin:
> > > > >> >> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> > > > >> >> >
> > > > >> >>
> > > > >> >
> > > > >>
> > > > >
> > > >
> > >
> >
>
Re: Please a reviewer for the case IGNITE-12518
Posted by Saikat Maitra <sa...@gmail.com>.
Hi, Luis, Denis
We can take up the changes in either Ignite-extensions repo as new
independent module or as part of ignite repo inside rest-http module but
since the changes are not in git pull request it is hard for us to review
and share feedback.
1. There are jar dependencies shared in the jira ticket[1] but we do not
accept jar instead we will require the changes in maven pom.xml file.
2. There are also changes in GridJettyRestHandler and GridJettyRestProtocol
but there are no corresponding tests for validation. It will be better if
required tests are added as part of PR.
3. It is also unclear how do we incorporate the changes mentioned in the
jira related to web.xml file, Do they need to be part of README.md?
Please let me know if I can help in any way with PR process.
Our docs for contribution are available here [2]
[1] https://issues.apache.org/jira/browse/IGNITE-12518
[2] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Regards,
Saikat
On Fri, Jan 24, 2020 at 11:09 AM Denis Magda <dm...@apache.org> wrote:
> Hi Luis,
>
> Presently, the community is on the route of Ignite simplification. We're
> trying to define Ignite core that has minimal dependencies with 3rd party
> libraries. That also led to the modularization initiative [1] with the
> first results in the form of Ignite Extensions repository where we're
> moving all 3rd party integrations.
>
> Saikat, do you think Luis's contribution needs to reside in the extensions
> repository?
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization
>
> -
> Denis
>
>
> On Thu, Jan 23, 2020 at 8:48 PM Luis Arce <lu...@mc3d.cl> wrote:
>
> > Hi Saikat,
> > Thanks for you response:
> >
> > My system need a web server for work. i work correctly with Wildfly and i
> > use Ignite as Backend for database.
> > My problem is the combination of both is around 6 GB RAM for work in the
> > VPS.
> > For this reason i modified the unique plugin with webserver inside
> > (rest-http module).
> > The change enabled the possibility for use only 3GB RAM in a VPS (
> > vpsserver.com) saving money and enabling horizontal scalling.
> > I shared this change in the Jira ticket touching the two classes of
> > rest-http plugin.
> > The change has less impact (programaticly), the point is the library
> > dependencies (quantity of jars).
> >
> > It change has sense for you?, i think is a util because that technologies
> > dont has present inside of ignite currently and is friendly with the code
> > of rest-ignite.
> >
> >
> >
> >
> > Best regards,
> >
> >
> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> > 09-57861903
> > Linkedin:
> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> >
> >
> >
> >
> >
> > El mié., 22 ene. 2020 a las 0:38, Saikat Maitra (<
> saikat.maitra@gmail.com
> > >)
> > escribió:
> >
> > > Hello Luis,
> > >
> > > Thank you for your email. You can plan to create a separate application
> > for
> > > jaxws service and use any build tools like gradle or maven to define
> your
> > > dependencies.
> > >
> > > Please find below some of the performance tips related to Ignite
> > >
> > > https://apacheignite.readme.io/docs/durable-memory-tuning
> > >
> > > You can use IgniteClient in your service and can connect to remote
> > cluster
> > > of Apache Ignite for data persistence.
> > >
> > > Can you please correct my understanding on the usage of
> ignite-rest-http
> > > in IGNITE-12518, I see the dependencies you have mentioned are related
> to
> > > your project and my understanding is you are trying to use
> > ignite-rest-http
> > > jetty server for running your application. My understanding is this
> > change
> > > will make ignite-rest-http very large jar file with dependencies
> > > like tomcat-servlet-api-9.0.10.jar may not needed outside of your
> project
> > > scope.
> > >
> > > Please let me know your thoughts.
> > >
> > > Regards,
> > > Saikat
> > >
> > >
> > > On Sun, Jan 19, 2020 at 9:47 PM Luis Arce <lu...@mc3d.cl> wrote:
> > >
> > > > Hi Saikat,
> > > > I agree, the impact of changes is bigger on the module.
> > > > I have a question: If i need create a jaxws service what is your
> > > > recomendation?
> > > > My motivation for the changes is the next:
> > > > *Introduction.*
> > > > A few time ago i design a ABB for traceability for Oracle Service Bus
> > > with
> > > > the objective of detecting failures points in many processes of a
> > > customer.
> > > > In first instance my team worked with rest-http module in ignite 2.4
> > with
> > > > poor results, the quantity of TPS was 4.Then we make a implementation
> > of
> > > > Rest service inside Apache Tomcat and call to Apache Ignite directly
> to
> > > > Database with persistence activated. This change, enabled the
> > possibility
> > > > for work with 4 environment of the customer (Development, Testing,
> QA,
> > > > Production) with 8GB of RAM in the machine, the configuration of the
> > > client
> > > > had a Oracle Portal for the View layer, EJB for composition of the
> > > > controller layer, and OSB for the integration the TPS of the client
> are
> > > > biggest.
> > > >
> > > > *AS-IS*
> > > >
> > > > [image: imagen.png]
> > > >
> > > > *To Be roadmap*
> > > >
> > > > [image: imagen.png]
> > > >
> > > > With the ignite modification published in Jira is possible run JSF
> for
> > > run
> > > > my reports and forms, JaxWS for the service SOAP and Jersey for Rest
> (i
> > > > start modification in this task).
> > > > The code published in Jira have capabilites for work with Primefaces
> > > > (tested ok), JaxWS (tested ok), but jersey is not included yet.
> > > >
> > > > Best regards,
> > > >
> > > >
> > > > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> > > > 09-57861903
> > > > Linkedin:
> > > > https://cl.linkedin.com/in/luisalejandroarcemartinez
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > El jue., 16 ene. 2020 a las 0:25, Saikat Maitra (<
> > > saikat.maitra@gmail.com>)
> > > > escribió:
> > > >
> > > >> Hi Luis,
> > > >>
> > > >> Thank you for sharing the details on the changes. I reviewed the
> > > >> dependencies that you shared in the jira issue and wanted to discuss
> > on
> > > >> the
> > > >> changes.
> > > >>
> > > >> The purpose of ignite-rest-http is to provide a web based interface
> to
> > > >> easily access and use the ignite features and the changes you
> > suggested
> > > >> can
> > > >> be built as part of separate application and ignite-rest-http can be
> > > used
> > > >> as an add on dependency. This will help keep ignite-rest-http module
> > as
> > > >> minimal and thin as possible.
> > > >>
> > > >> Please review and share your thoughts.
> > > >>
> > > >> Regards,
> > > >> Saikat
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> On Mon, Jan 13, 2020 at 7:24 PM Luis Arce <lu...@mc3d.cl>
> wrote:
> > > >>
> > > >> > Hi Saikat,
> > > >> > I add information for evidence for the changes of ignite rest-http
> > > >> module.
> > > >> >
> > > >> > 1. Can you please share more information on the issue that will be
> > > >> resolved
> > > >> > with this change?
> > > >> > R: This change add the possibility for publish war files with
> > > webpages
> > > >> in
> > > >> > JSF or webservices JaxWS inside of the jetty server embedded.
> > > >> > When the WAR file is loade automatically attached the JNDI for
> > lockup
> > > to
> > > >> > Ignite DataBase to the context of the page.
> > > >> > (I have a mvc4 application with ignite as a backend, with it
> change
> > i
> > > >> dont
> > > >> > need a primary web server).
> > > >> >
> > > >> > [image: imagen.png]
> > > >> >
> > > >> > [image: imagen.png]
> > > >> >
> > > >> > My webpage
> > > >> > [image: imagen.png]
> > > >> >
> > > >> > My mvc4
> > > >> > [image: imagen.png]
> > > >> >
> > > >> > The WebService
> > > >> >
> > > >> > [image: imagen.png]
> > > >> > The WSDL
> > > >> > [image: imagen.png]
> > > >> >
> > > >> > SoapUI
> > > >> > [image: imagen.png]
> > > >> >
> > > >> > TestSuite SoapUI
> > > >> > [image: imagen.png]
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y
> Gestión
> > > >> > 09-57861903
> > > >> > Linkedin:
> > > >> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > El dom., 12 ene. 2020 a las 14:43, Saikat Maitra (<
> > > >> saikat.maitra@gmail.com>)
> > > >> > escribió:
> > > >> >
> > > >> >> Hi Luis,
> > > >> >>
> > > >> >> 1. Can you please share more information on the issue that will
> be
> > > >> >> resolved
> > > >> >> with this change?
> > > >> >> 2. To accommodate the change, would you be able to raise a PR
> > please.
> > > >> >> Please take a look into the PR process
> > > >> >>
> > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > >> >> 3. Can you please add tests and execute the related testsuite in
> > > >> teamcity
> > > >> >> https://ci.ignite.apache.org/
> > > >> >>
> > > >> >> Regards,
> > > >> >> Saikat
> > > >> >>
> > > >> >> On Fri, Jan 10, 2020 at 5:39 PM Luis Arce <lu...@mc3d.cl>
> > wrote:
> > > >> >>
> > > >> >> > Dear community,
> > > >> >> >
> > > >> >> > I made modifications to the module rest-http.
> > > >> >> > It works correctly.
> > > >> >> > Is possible if anybody take my case for the review?
> > > >> >> >
> > > >> >> > The modifications are:
> > > >> >> > Support for webpages (test with jsf and primefaces), support
> for
> > > root
> > > >> >> > context.
> > > >> >> > Support to JaxWS with RI version.
> > > >> >> > Support for access to Ignite database with JNDI and basic
> > > connection
> > > >> >> > pooling'
> > > >> >> >
> > > >> >> > Se despide Atentamente,
> > > >> >> >
> > > >> >> >
> > > >> >> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y
> > Gestión
> > > >> >> > 09-57861903
> > > >> >> > Linkedin:
> > > >> >> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> > > >> >> >
> > > >> >>
> > > >> >
> > > >>
> > > >
> > >
> >
>
Re: Please a reviewer for the case IGNITE-12518
Posted by Denis Magda <dm...@apache.org>.
Hi Luis,
Presently, the community is on the route of Ignite simplification. We're
trying to define Ignite core that has minimal dependencies with 3rd party
libraries. That also led to the modularization initiative [1] with the
first results in the form of Ignite Extensions repository where we're
moving all 3rd party integrations.
Saikat, do you think Luis's contribution needs to reside in the extensions
repository?
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization
-
Denis
On Thu, Jan 23, 2020 at 8:48 PM Luis Arce <lu...@mc3d.cl> wrote:
> Hi Saikat,
> Thanks for you response:
>
> My system need a web server for work. i work correctly with Wildfly and i
> use Ignite as Backend for database.
> My problem is the combination of both is around 6 GB RAM for work in the
> VPS.
> For this reason i modified the unique plugin with webserver inside
> (rest-http module).
> The change enabled the possibility for use only 3GB RAM in a VPS (
> vpsserver.com) saving money and enabling horizontal scalling.
> I shared this change in the Jira ticket touching the two classes of
> rest-http plugin.
> The change has less impact (programaticly), the point is the library
> dependencies (quantity of jars).
>
> It change has sense for you?, i think is a util because that technologies
> dont has present inside of ignite currently and is friendly with the code
> of rest-ignite.
>
>
>
>
> Best regards,
>
>
> *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> 09-57861903
> Linkedin:
> https://cl.linkedin.com/in/luisalejandroarcemartinez
>
>
>
>
>
> El mié., 22 ene. 2020 a las 0:38, Saikat Maitra (<saikat.maitra@gmail.com
> >)
> escribió:
>
> > Hello Luis,
> >
> > Thank you for your email. You can plan to create a separate application
> for
> > jaxws service and use any build tools like gradle or maven to define your
> > dependencies.
> >
> > Please find below some of the performance tips related to Ignite
> >
> > https://apacheignite.readme.io/docs/durable-memory-tuning
> >
> > You can use IgniteClient in your service and can connect to remote
> cluster
> > of Apache Ignite for data persistence.
> >
> > Can you please correct my understanding on the usage of ignite-rest-http
> > in IGNITE-12518, I see the dependencies you have mentioned are related to
> > your project and my understanding is you are trying to use
> ignite-rest-http
> > jetty server for running your application. My understanding is this
> change
> > will make ignite-rest-http very large jar file with dependencies
> > like tomcat-servlet-api-9.0.10.jar may not needed outside of your project
> > scope.
> >
> > Please let me know your thoughts.
> >
> > Regards,
> > Saikat
> >
> >
> > On Sun, Jan 19, 2020 at 9:47 PM Luis Arce <lu...@mc3d.cl> wrote:
> >
> > > Hi Saikat,
> > > I agree, the impact of changes is bigger on the module.
> > > I have a question: If i need create a jaxws service what is your
> > > recomendation?
> > > My motivation for the changes is the next:
> > > *Introduction.*
> > > A few time ago i design a ABB for traceability for Oracle Service Bus
> > with
> > > the objective of detecting failures points in many processes of a
> > customer.
> > > In first instance my team worked with rest-http module in ignite 2.4
> with
> > > poor results, the quantity of TPS was 4.Then we make a implementation
> of
> > > Rest service inside Apache Tomcat and call to Apache Ignite directly to
> > > Database with persistence activated. This change, enabled the
> possibility
> > > for work with 4 environment of the customer (Development, Testing, QA,
> > > Production) with 8GB of RAM in the machine, the configuration of the
> > client
> > > had a Oracle Portal for the View layer, EJB for composition of the
> > > controller layer, and OSB for the integration the TPS of the client are
> > > biggest.
> > >
> > > *AS-IS*
> > >
> > > [image: imagen.png]
> > >
> > > *To Be roadmap*
> > >
> > > [image: imagen.png]
> > >
> > > With the ignite modification published in Jira is possible run JSF for
> > run
> > > my reports and forms, JaxWS for the service SOAP and Jersey for Rest (i
> > > start modification in this task).
> > > The code published in Jira have capabilites for work with Primefaces
> > > (tested ok), JaxWS (tested ok), but jersey is not included yet.
> > >
> > > Best regards,
> > >
> > >
> > > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> > > 09-57861903
> > > Linkedin:
> > > https://cl.linkedin.com/in/luisalejandroarcemartinez
> > >
> > >
> > >
> > >
> > >
> > > El jue., 16 ene. 2020 a las 0:25, Saikat Maitra (<
> > saikat.maitra@gmail.com>)
> > > escribió:
> > >
> > >> Hi Luis,
> > >>
> > >> Thank you for sharing the details on the changes. I reviewed the
> > >> dependencies that you shared in the jira issue and wanted to discuss
> on
> > >> the
> > >> changes.
> > >>
> > >> The purpose of ignite-rest-http is to provide a web based interface to
> > >> easily access and use the ignite features and the changes you
> suggested
> > >> can
> > >> be built as part of separate application and ignite-rest-http can be
> > used
> > >> as an add on dependency. This will help keep ignite-rest-http module
> as
> > >> minimal and thin as possible.
> > >>
> > >> Please review and share your thoughts.
> > >>
> > >> Regards,
> > >> Saikat
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Mon, Jan 13, 2020 at 7:24 PM Luis Arce <lu...@mc3d.cl> wrote:
> > >>
> > >> > Hi Saikat,
> > >> > I add information for evidence for the changes of ignite rest-http
> > >> module.
> > >> >
> > >> > 1. Can you please share more information on the issue that will be
> > >> resolved
> > >> > with this change?
> > >> > R: This change add the possibility for publish war files with
> > webpages
> > >> in
> > >> > JSF or webservices JaxWS inside of the jetty server embedded.
> > >> > When the WAR file is loade automatically attached the JNDI for
> lockup
> > to
> > >> > Ignite DataBase to the context of the page.
> > >> > (I have a mvc4 application with ignite as a backend, with it change
> i
> > >> dont
> > >> > need a primary web server).
> > >> >
> > >> > [image: imagen.png]
> > >> >
> > >> > [image: imagen.png]
> > >> >
> > >> > My webpage
> > >> > [image: imagen.png]
> > >> >
> > >> > My mvc4
> > >> > [image: imagen.png]
> > >> >
> > >> > The WebService
> > >> >
> > >> > [image: imagen.png]
> > >> > The WSDL
> > >> > [image: imagen.png]
> > >> >
> > >> > SoapUI
> > >> > [image: imagen.png]
> > >> >
> > >> > TestSuite SoapUI
> > >> > [image: imagen.png]
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> > >> > 09-57861903
> > >> > Linkedin:
> > >> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > El dom., 12 ene. 2020 a las 14:43, Saikat Maitra (<
> > >> saikat.maitra@gmail.com>)
> > >> > escribió:
> > >> >
> > >> >> Hi Luis,
> > >> >>
> > >> >> 1. Can you please share more information on the issue that will be
> > >> >> resolved
> > >> >> with this change?
> > >> >> 2. To accommodate the change, would you be able to raise a PR
> please.
> > >> >> Please take a look into the PR process
> > >> >>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > >> >> 3. Can you please add tests and execute the related testsuite in
> > >> teamcity
> > >> >> https://ci.ignite.apache.org/
> > >> >>
> > >> >> Regards,
> > >> >> Saikat
> > >> >>
> > >> >> On Fri, Jan 10, 2020 at 5:39 PM Luis Arce <lu...@mc3d.cl>
> wrote:
> > >> >>
> > >> >> > Dear community,
> > >> >> >
> > >> >> > I made modifications to the module rest-http.
> > >> >> > It works correctly.
> > >> >> > Is possible if anybody take my case for the review?
> > >> >> >
> > >> >> > The modifications are:
> > >> >> > Support for webpages (test with jsf and primefaces), support for
> > root
> > >> >> > context.
> > >> >> > Support to JaxWS with RI version.
> > >> >> > Support for access to Ignite database with JNDI and basic
> > connection
> > >> >> > pooling'
> > >> >> >
> > >> >> > Se despide Atentamente,
> > >> >> >
> > >> >> >
> > >> >> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y
> Gestión
> > >> >> > 09-57861903
> > >> >> > Linkedin:
> > >> >> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> > >> >> >
> > >> >>
> > >> >
> > >>
> > >
> >
>
Re: Please a reviewer for the case IGNITE-12518
Posted by Luis Arce <lu...@mc3d.cl>.
Hi Saikat,
Thanks for you response:
My system need a web server for work. i work correctly with Wildfly and i
use Ignite as Backend for database.
My problem is the combination of both is around 6 GB RAM for work in the
VPS.
For this reason i modified the unique plugin with webserver inside
(rest-http module).
The change enabled the possibility for use only 3GB RAM in a VPS (
vpsserver.com) saving money and enabling horizontal scalling.
I shared this change in the Jira ticket touching the two classes of
rest-http plugin.
The change has less impact (programaticly), the point is the library
dependencies (quantity of jars).
It change has sense for you?, i think is a util because that technologies
dont has present inside of ignite currently and is friendly with the code
of rest-ignite.
Best regards,
*Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
09-57861903
Linkedin:
https://cl.linkedin.com/in/luisalejandroarcemartinez
El mié., 22 ene. 2020 a las 0:38, Saikat Maitra (<sa...@gmail.com>)
escribió:
> Hello Luis,
>
> Thank you for your email. You can plan to create a separate application for
> jaxws service and use any build tools like gradle or maven to define your
> dependencies.
>
> Please find below some of the performance tips related to Ignite
>
> https://apacheignite.readme.io/docs/durable-memory-tuning
>
> You can use IgniteClient in your service and can connect to remote cluster
> of Apache Ignite for data persistence.
>
> Can you please correct my understanding on the usage of ignite-rest-http
> in IGNITE-12518, I see the dependencies you have mentioned are related to
> your project and my understanding is you are trying to use ignite-rest-http
> jetty server for running your application. My understanding is this change
> will make ignite-rest-http very large jar file with dependencies
> like tomcat-servlet-api-9.0.10.jar may not needed outside of your project
> scope.
>
> Please let me know your thoughts.
>
> Regards,
> Saikat
>
>
> On Sun, Jan 19, 2020 at 9:47 PM Luis Arce <lu...@mc3d.cl> wrote:
>
> > Hi Saikat,
> > I agree, the impact of changes is bigger on the module.
> > I have a question: If i need create a jaxws service what is your
> > recomendation?
> > My motivation for the changes is the next:
> > *Introduction.*
> > A few time ago i design a ABB for traceability for Oracle Service Bus
> with
> > the objective of detecting failures points in many processes of a
> customer.
> > In first instance my team worked with rest-http module in ignite 2.4 with
> > poor results, the quantity of TPS was 4.Then we make a implementation of
> > Rest service inside Apache Tomcat and call to Apache Ignite directly to
> > Database with persistence activated. This change, enabled the possibility
> > for work with 4 environment of the customer (Development, Testing, QA,
> > Production) with 8GB of RAM in the machine, the configuration of the
> client
> > had a Oracle Portal for the View layer, EJB for composition of the
> > controller layer, and OSB for the integration the TPS of the client are
> > biggest.
> >
> > *AS-IS*
> >
> > [image: imagen.png]
> >
> > *To Be roadmap*
> >
> > [image: imagen.png]
> >
> > With the ignite modification published in Jira is possible run JSF for
> run
> > my reports and forms, JaxWS for the service SOAP and Jersey for Rest (i
> > start modification in this task).
> > The code published in Jira have capabilites for work with Primefaces
> > (tested ok), JaxWS (tested ok), but jersey is not included yet.
> >
> > Best regards,
> >
> >
> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> > 09-57861903
> > Linkedin:
> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> >
> >
> >
> >
> >
> > El jue., 16 ene. 2020 a las 0:25, Saikat Maitra (<
> saikat.maitra@gmail.com>)
> > escribió:
> >
> >> Hi Luis,
> >>
> >> Thank you for sharing the details on the changes. I reviewed the
> >> dependencies that you shared in the jira issue and wanted to discuss on
> >> the
> >> changes.
> >>
> >> The purpose of ignite-rest-http is to provide a web based interface to
> >> easily access and use the ignite features and the changes you suggested
> >> can
> >> be built as part of separate application and ignite-rest-http can be
> used
> >> as an add on dependency. This will help keep ignite-rest-http module as
> >> minimal and thin as possible.
> >>
> >> Please review and share your thoughts.
> >>
> >> Regards,
> >> Saikat
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Mon, Jan 13, 2020 at 7:24 PM Luis Arce <lu...@mc3d.cl> wrote:
> >>
> >> > Hi Saikat,
> >> > I add information for evidence for the changes of ignite rest-http
> >> module.
> >> >
> >> > 1. Can you please share more information on the issue that will be
> >> resolved
> >> > with this change?
> >> > R: This change add the possibility for publish war files with
> webpages
> >> in
> >> > JSF or webservices JaxWS inside of the jetty server embedded.
> >> > When the WAR file is loade automatically attached the JNDI for lockup
> to
> >> > Ignite DataBase to the context of the page.
> >> > (I have a mvc4 application with ignite as a backend, with it change i
> >> dont
> >> > need a primary web server).
> >> >
> >> > [image: imagen.png]
> >> >
> >> > [image: imagen.png]
> >> >
> >> > My webpage
> >> > [image: imagen.png]
> >> >
> >> > My mvc4
> >> > [image: imagen.png]
> >> >
> >> > The WebService
> >> >
> >> > [image: imagen.png]
> >> > The WSDL
> >> > [image: imagen.png]
> >> >
> >> > SoapUI
> >> > [image: imagen.png]
> >> >
> >> > TestSuite SoapUI
> >> > [image: imagen.png]
> >> >
> >> >
> >> >
> >> >
> >> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> >> > 09-57861903
> >> > Linkedin:
> >> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > El dom., 12 ene. 2020 a las 14:43, Saikat Maitra (<
> >> saikat.maitra@gmail.com>)
> >> > escribió:
> >> >
> >> >> Hi Luis,
> >> >>
> >> >> 1. Can you please share more information on the issue that will be
> >> >> resolved
> >> >> with this change?
> >> >> 2. To accommodate the change, would you be able to raise a PR please.
> >> >> Please take a look into the PR process
> >> >> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> >> >> 3. Can you please add tests and execute the related testsuite in
> >> teamcity
> >> >> https://ci.ignite.apache.org/
> >> >>
> >> >> Regards,
> >> >> Saikat
> >> >>
> >> >> On Fri, Jan 10, 2020 at 5:39 PM Luis Arce <lu...@mc3d.cl> wrote:
> >> >>
> >> >> > Dear community,
> >> >> >
> >> >> > I made modifications to the module rest-http.
> >> >> > It works correctly.
> >> >> > Is possible if anybody take my case for the review?
> >> >> >
> >> >> > The modifications are:
> >> >> > Support for webpages (test with jsf and primefaces), support for
> root
> >> >> > context.
> >> >> > Support to JaxWS with RI version.
> >> >> > Support for access to Ignite database with JNDI and basic
> connection
> >> >> > pooling'
> >> >> >
> >> >> > Se despide Atentamente,
> >> >> >
> >> >> >
> >> >> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> >> >> > 09-57861903
> >> >> > Linkedin:
> >> >> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> >> >> >
> >> >>
> >> >
> >>
> >
>
Re: Please a reviewer for the case IGNITE-12518
Posted by Saikat Maitra <sa...@gmail.com>.
Hello Luis,
Thank you for your email. You can plan to create a separate application for
jaxws service and use any build tools like gradle or maven to define your
dependencies.
Please find below some of the performance tips related to Ignite
https://apacheignite.readme.io/docs/durable-memory-tuning
You can use IgniteClient in your service and can connect to remote cluster
of Apache Ignite for data persistence.
Can you please correct my understanding on the usage of ignite-rest-http
in IGNITE-12518, I see the dependencies you have mentioned are related to
your project and my understanding is you are trying to use ignite-rest-http
jetty server for running your application. My understanding is this change
will make ignite-rest-http very large jar file with dependencies
like tomcat-servlet-api-9.0.10.jar may not needed outside of your project
scope.
Please let me know your thoughts.
Regards,
Saikat
On Sun, Jan 19, 2020 at 9:47 PM Luis Arce <lu...@mc3d.cl> wrote:
> Hi Saikat,
> I agree, the impact of changes is bigger on the module.
> I have a question: If i need create a jaxws service what is your
> recomendation?
> My motivation for the changes is the next:
> *Introduction.*
> A few time ago i design a ABB for traceability for Oracle Service Bus with
> the objective of detecting failures points in many processes of a customer.
> In first instance my team worked with rest-http module in ignite 2.4 with
> poor results, the quantity of TPS was 4.Then we make a implementation of
> Rest service inside Apache Tomcat and call to Apache Ignite directly to
> Database with persistence activated. This change, enabled the possibility
> for work with 4 environment of the customer (Development, Testing, QA,
> Production) with 8GB of RAM in the machine, the configuration of the client
> had a Oracle Portal for the View layer, EJB for composition of the
> controller layer, and OSB for the integration the TPS of the client are
> biggest.
>
> *AS-IS*
>
> [image: imagen.png]
>
> *To Be roadmap*
>
> [image: imagen.png]
>
> With the ignite modification published in Jira is possible run JSF for run
> my reports and forms, JaxWS for the service SOAP and Jersey for Rest (i
> start modification in this task).
> The code published in Jira have capabilites for work with Primefaces
> (tested ok), JaxWS (tested ok), but jersey is not included yet.
>
> Best regards,
>
>
> *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> 09-57861903
> Linkedin:
> https://cl.linkedin.com/in/luisalejandroarcemartinez
>
>
>
>
>
> El jue., 16 ene. 2020 a las 0:25, Saikat Maitra (<sa...@gmail.com>)
> escribió:
>
>> Hi Luis,
>>
>> Thank you for sharing the details on the changes. I reviewed the
>> dependencies that you shared in the jira issue and wanted to discuss on
>> the
>> changes.
>>
>> The purpose of ignite-rest-http is to provide a web based interface to
>> easily access and use the ignite features and the changes you suggested
>> can
>> be built as part of separate application and ignite-rest-http can be used
>> as an add on dependency. This will help keep ignite-rest-http module as
>> minimal and thin as possible.
>>
>> Please review and share your thoughts.
>>
>> Regards,
>> Saikat
>>
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Jan 13, 2020 at 7:24 PM Luis Arce <lu...@mc3d.cl> wrote:
>>
>> > Hi Saikat,
>> > I add information for evidence for the changes of ignite rest-http
>> module.
>> >
>> > 1. Can you please share more information on the issue that will be
>> resolved
>> > with this change?
>> > R: This change add the possibility for publish war files with webpages
>> in
>> > JSF or webservices JaxWS inside of the jetty server embedded.
>> > When the WAR file is loade automatically attached the JNDI for lockup to
>> > Ignite DataBase to the context of the page.
>> > (I have a mvc4 application with ignite as a backend, with it change i
>> dont
>> > need a primary web server).
>> >
>> > [image: imagen.png]
>> >
>> > [image: imagen.png]
>> >
>> > My webpage
>> > [image: imagen.png]
>> >
>> > My mvc4
>> > [image: imagen.png]
>> >
>> > The WebService
>> >
>> > [image: imagen.png]
>> > The WSDL
>> > [image: imagen.png]
>> >
>> > SoapUI
>> > [image: imagen.png]
>> >
>> > TestSuite SoapUI
>> > [image: imagen.png]
>> >
>> >
>> >
>> >
>> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
>> > 09-57861903
>> > Linkedin:
>> > https://cl.linkedin.com/in/luisalejandroarcemartinez
>> >
>> >
>> >
>> >
>> >
>> > El dom., 12 ene. 2020 a las 14:43, Saikat Maitra (<
>> saikat.maitra@gmail.com>)
>> > escribió:
>> >
>> >> Hi Luis,
>> >>
>> >> 1. Can you please share more information on the issue that will be
>> >> resolved
>> >> with this change?
>> >> 2. To accommodate the change, would you be able to raise a PR please.
>> >> Please take a look into the PR process
>> >> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>> >> 3. Can you please add tests and execute the related testsuite in
>> teamcity
>> >> https://ci.ignite.apache.org/
>> >>
>> >> Regards,
>> >> Saikat
>> >>
>> >> On Fri, Jan 10, 2020 at 5:39 PM Luis Arce <lu...@mc3d.cl> wrote:
>> >>
>> >> > Dear community,
>> >> >
>> >> > I made modifications to the module rest-http.
>> >> > It works correctly.
>> >> > Is possible if anybody take my case for the review?
>> >> >
>> >> > The modifications are:
>> >> > Support for webpages (test with jsf and primefaces), support for root
>> >> > context.
>> >> > Support to JaxWS with RI version.
>> >> > Support for access to Ignite database with JNDI and basic connection
>> >> > pooling'
>> >> >
>> >> > Se despide Atentamente,
>> >> >
>> >> >
>> >> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
>> >> > 09-57861903
>> >> > Linkedin:
>> >> > https://cl.linkedin.com/in/luisalejandroarcemartinez
>> >> >
>> >>
>> >
>>
>
Re: Please a reviewer for the case IGNITE-12518
Posted by Luis Arce <lu...@mc3d.cl>.
Hi Saikat,
I agree, the impact of changes is bigger on the module.
I have a question: If i need create a jaxws service what is your
recomendation?
My motivation for the changes is the next:
*Introduction.*
A few time ago i design a ABB for traceability for Oracle Service Bus with
the objective of detecting failures points in many processes of a customer.
In first instance my team worked with rest-http module in ignite 2.4 with
poor results, the quantity of TPS was 4.Then we make a implementation of
Rest service inside Apache Tomcat and call to Apache Ignite directly to
Database with persistence activated. This change, enabled the possibility
for work with 4 environment of the customer (Development, Testing, QA,
Production) with 8GB of RAM in the machine, the configuration of the client
had a Oracle Portal for the View layer, EJB for composition of the
controller layer, and OSB for the integration the TPS of the client are
biggest.
*AS-IS*
[image: imagen.png]
*To Be roadmap*
[image: imagen.png]
With the ignite modification published in Jira is possible run JSF for run
my reports and forms, JaxWS for the service SOAP and Jersey for Rest (i
start modification in this task).
The code published in Jira have capabilites for work with Primefaces
(tested ok), JaxWS (tested ok), but jersey is not included yet.
Best regards,
*Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
09-57861903
Linkedin:
https://cl.linkedin.com/in/luisalejandroarcemartinez
El jue., 16 ene. 2020 a las 0:25, Saikat Maitra (<sa...@gmail.com>)
escribió:
> Hi Luis,
>
> Thank you for sharing the details on the changes. I reviewed the
> dependencies that you shared in the jira issue and wanted to discuss on the
> changes.
>
> The purpose of ignite-rest-http is to provide a web based interface to
> easily access and use the ignite features and the changes you suggested can
> be built as part of separate application and ignite-rest-http can be used
> as an add on dependency. This will help keep ignite-rest-http module as
> minimal and thin as possible.
>
> Please review and share your thoughts.
>
> Regards,
> Saikat
>
>
>
>
>
>
>
>
> On Mon, Jan 13, 2020 at 7:24 PM Luis Arce <lu...@mc3d.cl> wrote:
>
> > Hi Saikat,
> > I add information for evidence for the changes of ignite rest-http
> module.
> >
> > 1. Can you please share more information on the issue that will be
> resolved
> > with this change?
> > R: This change add the possibility for publish war files with webpages
> in
> > JSF or webservices JaxWS inside of the jetty server embedded.
> > When the WAR file is loade automatically attached the JNDI for lockup to
> > Ignite DataBase to the context of the page.
> > (I have a mvc4 application with ignite as a backend, with it change i
> dont
> > need a primary web server).
> >
> > [image: imagen.png]
> >
> > [image: imagen.png]
> >
> > My webpage
> > [image: imagen.png]
> >
> > My mvc4
> > [image: imagen.png]
> >
> > The WebService
> >
> > [image: imagen.png]
> > The WSDL
> > [image: imagen.png]
> >
> > SoapUI
> > [image: imagen.png]
> >
> > TestSuite SoapUI
> > [image: imagen.png]
> >
> >
> >
> >
> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> > 09-57861903
> > Linkedin:
> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> >
> >
> >
> >
> >
> > El dom., 12 ene. 2020 a las 14:43, Saikat Maitra (<
> saikat.maitra@gmail.com>)
> > escribió:
> >
> >> Hi Luis,
> >>
> >> 1. Can you please share more information on the issue that will be
> >> resolved
> >> with this change?
> >> 2. To accommodate the change, would you be able to raise a PR please.
> >> Please take a look into the PR process
> >> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> >> 3. Can you please add tests and execute the related testsuite in
> teamcity
> >> https://ci.ignite.apache.org/
> >>
> >> Regards,
> >> Saikat
> >>
> >> On Fri, Jan 10, 2020 at 5:39 PM Luis Arce <lu...@mc3d.cl> wrote:
> >>
> >> > Dear community,
> >> >
> >> > I made modifications to the module rest-http.
> >> > It works correctly.
> >> > Is possible if anybody take my case for the review?
> >> >
> >> > The modifications are:
> >> > Support for webpages (test with jsf and primefaces), support for root
> >> > context.
> >> > Support to JaxWS with RI version.
> >> > Support for access to Ignite database with JNDI and basic connection
> >> > pooling'
> >> >
> >> > Se despide Atentamente,
> >> >
> >> >
> >> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> >> > 09-57861903
> >> > Linkedin:
> >> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> >> >
> >>
> >
>
Re: Please a reviewer for the case IGNITE-12518
Posted by Saikat Maitra <sa...@gmail.com>.
Hi Luis,
Thank you for sharing the details on the changes. I reviewed the
dependencies that you shared in the jira issue and wanted to discuss on the
changes.
The purpose of ignite-rest-http is to provide a web based interface to
easily access and use the ignite features and the changes you suggested can
be built as part of separate application and ignite-rest-http can be used
as an add on dependency. This will help keep ignite-rest-http module as
minimal and thin as possible.
Please review and share your thoughts.
Regards,
Saikat
On Mon, Jan 13, 2020 at 7:24 PM Luis Arce <lu...@mc3d.cl> wrote:
> Hi Saikat,
> I add information for evidence for the changes of ignite rest-http module.
>
> 1. Can you please share more information on the issue that will be resolved
> with this change?
> R: This change add the possibility for publish war files with webpages in
> JSF or webservices JaxWS inside of the jetty server embedded.
> When the WAR file is loade automatically attached the JNDI for lockup to
> Ignite DataBase to the context of the page.
> (I have a mvc4 application with ignite as a backend, with it change i dont
> need a primary web server).
>
> [image: imagen.png]
>
> [image: imagen.png]
>
> My webpage
> [image: imagen.png]
>
> My mvc4
> [image: imagen.png]
>
> The WebService
>
> [image: imagen.png]
> The WSDL
> [image: imagen.png]
>
> SoapUI
> [image: imagen.png]
>
> TestSuite SoapUI
> [image: imagen.png]
>
>
>
>
> *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> 09-57861903
> Linkedin:
> https://cl.linkedin.com/in/luisalejandroarcemartinez
>
>
>
>
>
> El dom., 12 ene. 2020 a las 14:43, Saikat Maitra (<sa...@gmail.com>)
> escribió:
>
>> Hi Luis,
>>
>> 1. Can you please share more information on the issue that will be
>> resolved
>> with this change?
>> 2. To accommodate the change, would you be able to raise a PR please.
>> Please take a look into the PR process
>> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>> 3. Can you please add tests and execute the related testsuite in teamcity
>> https://ci.ignite.apache.org/
>>
>> Regards,
>> Saikat
>>
>> On Fri, Jan 10, 2020 at 5:39 PM Luis Arce <lu...@mc3d.cl> wrote:
>>
>> > Dear community,
>> >
>> > I made modifications to the module rest-http.
>> > It works correctly.
>> > Is possible if anybody take my case for the review?
>> >
>> > The modifications are:
>> > Support for webpages (test with jsf and primefaces), support for root
>> > context.
>> > Support to JaxWS with RI version.
>> > Support for access to Ignite database with JNDI and basic connection
>> > pooling'
>> >
>> > Se despide Atentamente,
>> >
>> >
>> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
>> > 09-57861903
>> > Linkedin:
>> > https://cl.linkedin.com/in/luisalejandroarcemartinez
>> >
>>
>
Re: Please a reviewer for the case IGNITE-12518
Posted by Luis Arce <lu...@mc3d.cl>.
Hi Saikat,
I add information for evidence for the changes of ignite rest-http module.
1. Can you please share more information on the issue that will be resolved
with this change?
R: This change add the possibility for publish war files with webpages in
JSF or webservices JaxWS inside of the jetty server embedded.
When the WAR file is loade automatically attached the JNDI for lockup to
Ignite DataBase to the context of the page.
(I have a mvc4 application with ignite as a backend, with it change i dont
need a primary web server).
[image: imagen.png]
[image: imagen.png]
My webpage
[image: imagen.png]
My mvc4
[image: imagen.png]
The WebService
[image: imagen.png]
The WSDL
[image: imagen.png]
SoapUI
[image: imagen.png]
TestSuite SoapUI
[image: imagen.png]
*Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
09-57861903
Linkedin:
https://cl.linkedin.com/in/luisalejandroarcemartinez
El dom., 12 ene. 2020 a las 14:43, Saikat Maitra (<sa...@gmail.com>)
escribió:
> Hi Luis,
>
> 1. Can you please share more information on the issue that will be resolved
> with this change?
> 2. To accommodate the change, would you be able to raise a PR please.
> Please take a look into the PR process
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> 3. Can you please add tests and execute the related testsuite in teamcity
> https://ci.ignite.apache.org/
>
> Regards,
> Saikat
>
> On Fri, Jan 10, 2020 at 5:39 PM Luis Arce <lu...@mc3d.cl> wrote:
>
> > Dear community,
> >
> > I made modifications to the module rest-http.
> > It works correctly.
> > Is possible if anybody take my case for the review?
> >
> > The modifications are:
> > Support for webpages (test with jsf and primefaces), support for root
> > context.
> > Support to JaxWS with RI version.
> > Support for access to Ignite database with JNDI and basic connection
> > pooling'
> >
> > Se despide Atentamente,
> >
> >
> > *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> > 09-57861903
> > Linkedin:
> > https://cl.linkedin.com/in/luisalejandroarcemartinez
> >
>
Re: Please a reviewer for the case IGNITE-12518
Posted by Saikat Maitra <sa...@gmail.com>.
Hi Luis,
1. Can you please share more information on the issue that will be resolved
with this change?
2. To accommodate the change, would you be able to raise a PR please.
Please take a look into the PR process
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
3. Can you please add tests and execute the related testsuite in teamcity
https://ci.ignite.apache.org/
Regards,
Saikat
On Fri, Jan 10, 2020 at 5:39 PM Luis Arce <lu...@mc3d.cl> wrote:
> Dear community,
>
> I made modifications to the module rest-http.
> It works correctly.
> Is possible if anybody take my case for the review?
>
> The modifications are:
> Support for webpages (test with jsf and primefaces), support for root
> context.
> Support to JaxWS with RI version.
> Support for access to Ignite database with JNDI and basic connection
> pooling'
>
> Se despide Atentamente,
>
>
> *Luis Arce Martínez*Licenciado e Ingeniero en Informática y Gestión
> 09-57861903
> Linkedin:
> https://cl.linkedin.com/in/luisalejandroarcemartinez
>