You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/05/10 08:14:04 UTC
[jira] [Updated] (IGNITE-4586) REST on JBOSS instead of JETTY
[ https://issues.apache.org/jira/browse/IGNITE-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-4586:
------------------------------------
Component/s: (was: rest)
clients
> REST on JBOSS instead of JETTY
> ------------------------------
>
> Key: IGNITE-4586
> URL: https://issues.apache.org/jira/browse/IGNITE-4586
> Project: Ignite
> Issue Type: Improvement
> Components: clients
> Affects Versions: 1.8
> Reporter: Sam
>
> GridRestProcessor initialization done only when connector configuration provided. During GridRestProcessor initialization it starts JETTY server with hard coded class name for REST handler
> private static final String HTTP_PROTO_CLS = "org.apache.ignite.internal.processors.rest.protocols.http.jetty.GridJettyRestProtocol";
> If an application integrate Ignite with JBOSS/Tomcat/WebSphere then there is no need of JETTY server. Which means no connector configuration. In this case REST can not be integrated. Improvements needed to -
> 1. Integrate Ignite REST with application REST endpoint
> 2. No JETTY server mandatory
> Some more information at -
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-REST-with-JBOSS-td10108.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)