I've been reading up about Akka and it really seems nice. Can you somehow set it up to work with Apache Mina or similar techs? I.e not only use it in conjunction with servlets.
Hmmm, seems you already have a technical solution (Mina).
May I ask what is the problem you're trying to solve?
RemoteActors are using Netty, it's basically only the JAX-RS (Jersey) and Comet (Atmosphere) integration that runs over servlets.
Related
I have an application written in Scala/Akka and trying to add SOAP support. Anyone did it with Alpakka? Or what is the best way to do it. So far I think Camel is the best solution.
Currently, Alpakka does not support SOAP, but there is an open ticket. Your best bet is probably to use Camel integration in your Scala/Akka project. To that end, take a look at the streamz project or the Camel integration module in Akka (the latter is deprecated but may serve your needs).
There is also a library that provides some SOAP integration with Play.
Im looking to mock out calls to a third party API from my scala microservice. Can anybody recommend a library they have tried and tested for this? I have seen a couple of older and not very active projects on github, but they do not look too promising.
This mock server is appropriate for your purpose, like alternative, you can look at [simplle framework][2], which is very simple in use, btw, they provide examples of usage.
I used wiremock (Java)
It's very simple and yet powerful.
I would like to implement an API in Spray (Scala), that allows me to process a simple SOAP request. The request is a POST with a WS-Addressing payload. Although I can get the XML document, and I am aware of the existence of javax.xml.ws.soap.Addressing, I'm not sure how to tie the two together.
Can I use the above mentioned Addressing support in a spray route? if so, how? I can't figure out how to use an AddressingFeature in Scala.
Any help would be appreciated. If I can solve this, I can probably address other WS-* support I need.
Can I use the above mentioned Addressing support in a spray route?
The short answer is no, or better, why would you want to?
It's possible to build JAX-WS web services in Scala, but if you're trying to do it in Spray you're crossing paradigms. You really need a JAX-WS framework if you have to support WS-Addressing and other WS-* features.
I started with Spray as a WS-* refugee, and I doubt I'm the only one. I prefer Spray and I know you can use it to parse out your e.g. MessageId or Action and use them to build a Route, but I wouldn't reach for JAX-WS to make it happen.
There is a list of usable frameworks in the creators blog of Atmosphere. I want to use scala and the Play Framework included with Atmosphere. In the blog he writes that Atmosphere works with "every" framework. Could it be that easy to integrate Atmosphere, and how?
I understand that this isn't necessarily the answer you were looking for, but I would suggest you look at Play's native comet support.
http://www.playframework.org/documentation/2.0/ScalaComet
http://www.playframework.org/documentation/api/2.0/scala/play/api/libs/Comet$.html
Do you have a particular use case that Atmosphere can solve more elegantly? If so, here's a thread that might help.
https://groups.google.com/forum/m/?fromgroups#!topic/atmosphere-framework/GM6fC6-eSLE
Yes, take a look at this project - it's a native implementation of Atmosphere running on top of Play!
I'm looking for this too. The benefits it would give are graceful degradation from websocket to long polling and a common api for these both client and server side.
UrlRewriteFilter depends on httpclient-3.1, while Couchbase client depends on httpclient-4.0.
I came up with two choices:
Use two different versions of httpclient together
Replace UrlRewriteFilter with other solutions
I found that using httpclient 3.1 and 4.0 together is ok (reference), but is it the best way?
As for the second choice, I use proxying, redirecting, and forwarding with UrlRewriteFilter. Redirecting and forwarding would be possible if I user Spring MVC. But I have no idea how can I proxy some URIs without using Apache web server or haproxy.
Any advices or corrections for this question are welcomed.
HttpClient 3.1 and 4.0 can coexist with no problem. I would say the best solution at the moment is to do that. It's always tempting to form UrlRewriteFilter for example. But in the end, that kind of solutions are just time-consuming.
Whatever you are doing do NOT use Apache to proxy som URLs, you will just be mad that you can never just use Jetty in development and you have to maintain rewrites that are not in the codebase, that is the worst solution.