CapeDwarf News

CapeDwarf News

There was a small bug on how we handled security constraints — it should re-direct you to login page in case of non-authorized access. This is now fixed. While we also added fine-grained configuration of authorization mechanism, and moved default to GAE/CapeDwarf mechanism.

I’ve also created new Docker image, with this release, under "alesj/capedwarf".

It’s been a while since our last release. But that doesn’t mean we haven’t been busy. With Google App Engine’s ManagedVMs getting more and more traction, we figured out we needed to support that too. And voila, a new CapeDwarf Managed project was created.

But in order to not duplicate the code between Managed and Blue, some refactoring was required, hence the delay. And along the way - while implementing Managed - we saw we were also missing a few things in Blue as well: warmup request and GAE-like HTTP session handling.

While playing with some Endpoints GAE example app, I noticed our non-XG transactions weren’t following the concurrent threads limits — only one transaction per entity group allowed. This quickly shows how you easily miss things when you don’t have proper tests.

In our case setting this concurrency contention is not as easy as it sounds. But … luckily at JBoss we have a tool called Byteman, which is exactly what we’re looking for (and it even came from initially testing concurrency on transactions).

And, as I expected from Aslak, Arquillian already had Byteman support integrated. OK, to be honest, it did need some minor changes to make it work as expected. :-)