Hi Feyyaz,
I'm thinking what you'd have to do to stay within your organization's
required JEE environment is to create a servlet that could feed messages to
a Source.actorRef or Source.queue. based on whether you could use the
servlet async API, or need to use the venerable synchronous servlet
Hi,
I'm struggling the same issue as well. It's not a choice, but it's a
requirement from the infrastructure team.
Unfortunately there is no way to directly bind it to a servlet. The easiest
way is, as @√ says, to start/stop it with servlet, but it will run on a
different port. For example,
Hi √ and everyone,
It's 2017 and I'm still struggling with this (migrating from spray)…
Could somebody share the easy integration using ServletContextListener
described above?
In particular I'm quite interested in
- how to use a generic servlet implementation backed up by a "routes:
Route"
is there an example showing how to integrate servlet container with
akka-http? i'm currently using spray with serlvet
with
https://github.com/spray/spray/blob/master/spray-servlet/src/main/scala/spray/servlet/Servlet30ConnectorServlet.scala
and was hoping to find an example showing how to
Hi Tomer,
the servlet container way of running things completely negates all the benefits
that Akka HTTP would give you, so there is no point in supporting this
scenario—spray-servlet will not be ported to Akka HTTP.
Sorry for the bad news,
Roland
14 apr 2015 kl. 15:45 skrev Jas
thank you! sounds like a good option considering my system is already
integrated with tomcat!
On Tuesday, April 14, 2015 at 5:55:10 PM UTC+3, √ wrote:
One integration you can do easily is to have a ServletContextListener that
creates the Akka Http server endpoint when loaded and stops it on
One integration you can do easily is to have a ServletContextListener that
creates the Akka Http server endpoint when loaded and stops it on unload.
On Tue, Apr 14, 2015 at 3:53 PM, Roland Kuhn goo...@rkuhn.info wrote:
Hi Tomer,
the servlet container way of running things completely negates
