As the title - taken from a cheesy romantic movie :-) - says, we now finally have proper mail API support on CapeDwarf.
We also moved our capedwarf.org site to Awestruct and Asciidoctor, plus adding a bunch of content to it — faq, docs, blogs, …
CapeDwarf now uses WildFly 8.0.0.Final underneath, which fixed some of the deployment’ concurrency handling issues.
The full release notes can be found here:
Download the full .zip distribution:
Feedback welcome!
Yes, we finally moved the CapeDwarf runtime over to new WildFly codebase! It took time to get all the components aligned, all our provided patches merged and all issues resolved. But it was worth it!
Apart from new runtime with WildFly, we also switched to new Infinispan version 6.x and new UnderTow web server. With new Infinispan version 6.x you get much faster file store impl, while the move to UnderTow allowed us to implement Channel API on top of WebSockets.
The full release notes can be found here:
Download the full .zip distribution:
To name a few new features or resolved issues - we finally have initial OAuth impl, we’re now using original Endpoints resources from GAE for our Endpoints support, Marko found and fixed a nasty namespace bug in our Datastore, and we fixed a bunch of small issues exposed by the GAE TCK.
The old codebase based on JBossAS7 can be found under 1.0 branch in our GitHub repos.
Give this new release a spin. Feedback is welcome as always!
Happy holidays!
As you can see from the title, and from a bit late release, we’ve again been very busy.
Let’s just go over all new features.
There is a bit of limitation on our end here, as there is no (easy / nice) dynamic way (to my knowledge) to scale up / down virtual servers (at runtime during deployment phase) in JBossWeb that comes with JBossAS7 (which is what we use). In order to use Modules with CapeDwarf, you must use “standalone-capedwarf-modules.xml” configuration when you startup CapeDwarf AS instance.
You must also configure the number of virtual servers to match your application’s modularization. See web subsystem configuration in “standalone-capedwarf-modules.xml” for more details.
(or simply ping me for any Modules questions - via forums, email, Twitter or Freenode IRC #capedwarf)
We’ve managed to map GAE’s Endpoints annotations to JAXRS/RestEasy annotations, and we also support custom serialization.
In our case / implementation we only need .api files as markers, and not to read any information from it — you can have a single .api dummy file if you like.
SQL was of course supported out-of-the-box for us. We we just had to hack GAE’s Driver class to connect against selected DataSource:
FileService is being deprecated in favor of Google Cloud Storage (GCS) API. At the moment dev / local implementation of the GCS client library still goes against FileService implementation, so supporting this was easy, as we already fully implemented FileService API.
We re-implemented Channel API.
Big thanks to @chrisritter for kicking our butt to do this, and contributing a simple but cool chat app for testing purposes: SimpleChat.
Also thanks to Karel for stepping up and fixing Arquillian Drone so we can finally automagically test this.
Don’t miss my presentation at JavaOne — Tuesday 24th September at 11:30am, Parc55.
Or my previously mentioned DC JBUG talk: http://www.meetup.com/DC-JBug/events/128068042/
Markus Eisele posted a nice overview of CapeDwarf:
Anyway, enjoy the new release! Feedback welcome as always.
