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 <[email protected]> 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 (<[email protected]>) > 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 <[email protected]> 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 (< >> [email protected]>) >> > 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 <[email protected]> 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 >> >> > >> >> >> > >> >
