I am using Akka version 2.3.11 in an OSGi-based project and we tried to add
akka-contrib (com.typesafe.akka/akka-contrib_2.11/2.3.11) to the mix. To
our surprise, the jar contains no OSGi information in its MANIFEST.MF file.
Is this intentional? Could we perhaps get that added to the build?
I don't have an answer nor time to respond to a blog comparison, but if you
google Akka vs Quasar you will find plenty of opinions and depending on
what you want or need to hear you will make your decision, now, in a
nutshell:
*Typesafe is a great, innovative and more matured company which
That's quite possibly the only thing missing. Would you like to submit a
PullRequest and we'll look into it there?
On Sat, Jun 6, 2015 at 2:40 PM, James Carman jcar...@savoirtech.com wrote:
It looks to be as simple as adding:
OSGi.contrib
to the sbt file for contrib. Is that all there is
It looks to be as simple as adding:
OSGi.contrib
to the sbt file for contrib. Is that all there is to it?
On Saturday, June 6, 2015 at 8:37:34 AM UTC-4, James Carman wrote:
I am using Akka version 2.3.11 in an OSGi-based project and we tried to
add akka-contrib
Just noticed the PR, thanks!
https://github.com/akka/akka/pull/17673
On Sat, Jun 6, 2015 at 3:36 PM, Konrad Malawski kt...@typesafe.com wrote:
That's quite possibly the only thing missing. Would you like to submit a
PullRequest and we'll look into it there?
On Sat, Jun 6, 2015 at 2:40 PM,
It was a tad bit more than that, but not much. Had to do an import and
define the contrib val on OSGi. Then, it was off to the races! Looks
like the jenkins build is running now. Hopefully this can make it in. For
now, I'm wrapping the bundle in Karaf. Yuck! :) Do you guys want any help
After digging into the source code, the Flow.wrap is simply a container for
an In and an Out.
There are no associated semantics.
I had incorrectly assumed some coupling would apply.
--
Read the docs: http://akka.io/docs/
Check the FAQ:
I am using akka-streams for handling incoming TCP connections. After
putting application behind AWS Elastic Load Balancer, it started to fall
into too many open files problem because of lots of connections in
CLOSE_WAIT state. Is there an ability to close such connection on a server
side?
--
Just found this issue: https://github.com/akka/akka/issues/17122
So, it's akka-io problem and there is no currently any workaround when
using akka-streams, am i right?
On Sunday, June 7, 2015 at 7:03:01 AM UTC+3, Andrey Kuznetsov wrote:
I am using akka-streams for handling incoming TCP
Bounded Contexts are more about understanding that the word Order means two
very different things when I talk to OrderManagement vs Shipping. If I try
to use one single language for everything the language often becomes
polluted in terms and we end up with supersets of concepts. You can host
Right, in a way Bounded Contexts is a mitigation against LCD.
On Sat, Jun 6, 2015 at 7:47 PM, Greg Young gregoryyou...@gmail.com wrote:
Bounded Contexts are more about understanding that the word Order means
two very different things when I talk to OrderManagement vs Shipping. If I
try to use
It can work this way yes.
For me personally I think its more about fighting against all the
problems we have in describing our problems. It is not a technical
pattern.
On Sat, Jun 6, 2015 at 10:00 PM, Viktor Klang viktor.kl...@gmail.com wrote:
Right, in a way Bounded Contexts is a mitigation
Hi,
I have been using Akka now for three months now and one thing that got my
attention in a very good way is the fact that you can use Scala methods and
functions from Java, then I wonder:
- Is it really necessary to have an Akka Java API for Java developers in
general?
- I have not
13 matches
Mail list logo
