Re: ComputeTask with JSON POST data

2019-04-02 Thread kellan
It's Scala. But don't worry, I'll just use my work around. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ComputeTask with JSON POST data

2019-04-02 Thread Ilya Kasnacheev
Hello! Is this Kotlin? I don't think I have build chain for it. Will be easier if you took the trouble of building a zip ball out of it. Regards, -- Ilya Kasnacheev вт, 2 апр. 2019 г. в 16:55, kellan : > Just build an ignite project with this and try to reference it from the > Handlers sectio

Re: ComputeTask with JSON POST data

2019-04-02 Thread kellan
Just build an ignite project with this and try to reference it from the Handlers section of your jetty.xml file. Should be pretty straightforward. package my.custom import javax.servlet.http.{HttpServletRequest, HttpServletResponse} import org.eclipse.jetty.server.Request import org.eclipse.jetty

Re: ComputeTask with JSON POST data

2019-04-02 Thread ilya.kasnacheev
Hello! Can you share a sample reproducer project? I guess I could try to make it work. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ComputeTask with JSON POST data

2019-04-02 Thread kellan
I did. I replaced the handler block with: But Ignite is still calling GridJettyRestHandler internally. I was able to get my custom handler to work by dropping the ignite-rest-http module, then copying in GridJettyRestProtocol and modifying the code to set my custom handler in

Re: ComputeTask with JSON POST data

2019-04-02 Thread Ilya Kasnacheev
Hello! Have you looked at https://apacheignite.readme.io/docs/rest-api#sample-jetty-xml-configuration ? I did not go through it myself so I'm unable to guide you step-by-step, but if you had some code which did not work as expected, I could lend a hand. Regards, -- Ilya Kasnacheev вт, 2 апр.

Re: ComputeTask with JSON POST data

2019-04-02 Thread kellan
To me, it looks like GridJettyRestProtocol.loadJettyConfiguration is overriding the handler from the jetty configuration file with GridJettyRestHandler. Is there something I'm missing here, or do I need to just drop ignite-rest-http and implement the jetty server from scratch in lifecycle event o

Re: ComputeTask with JSON POST data

2019-04-01 Thread kellan
Sorry, I'm not really familiar with Jetty. I see that there's a GridJettyRestHandler class in Ignite, but I don't see any place in jetty configuration where this class is being referenced, so it's not really clear to me how this class is being initialized, or how to override it. -- Sent from: ht

Re: ComputeTask with JSON POST data

2019-04-01 Thread Ilya Kasnacheev
Hello! You can specify your own Jetty configuration, and in it you should be able to define your own handlers. Regards, -- Ilya Kasnacheev пн, 1 апр. 2019 г. в 14:38, kellan : > But is there a built-in way to write a custom REST handler for Ignite? Or > do > I need to create a separate applic

Re: ComputeTask with JSON POST data

2019-04-01 Thread kellan
But is there a built-in way to write a custom REST handler for Ignite? Or do I need to create a separate application that routes requests to Ignite? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ComputeTask with JSON POST data

2019-04-01 Thread Ilya Kasnacheev
Hello! You can implement REST handler in your user code to run tasks with arbitrary results. However, the question of writing REST handlers for Jetty is not really related to Ignite anymore. Regards, -- Ilya Kasnacheev пт, 29 мар. 2019 г. в 23:09, kellan : > How exactly would I go about doing

Re: ComputeTask with JSON POST data

2019-03-29 Thread kellan
How exactly would I go about doing that? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ComputeTask with JSON POST data

2019-03-29 Thread Ilya Kasnacheev
Hello! I don't think you can do that with Ignite's REST, but it should be trivial to write such REST handler on your side and plug it into Jetty. Regards, -- Ilya Kasnacheev ср, 27 мар. 2019 г. в 21:25, kellan : > How do I create a ComputeTask that accepts JSON POST data from a REST API > end