Aleš Justin was born in Ljubljana, Slovenia and graduated with a degree in mathematics from the University of Ljubljana. He fell in love with Java long ago and has spent most of his time developing information systems, ranging from customer service to energy management. He joined JBoss in 2006 to work full time on the Microcontainer project. He currently leads CapeDwarf project, while still contributing to ApplicationServer, Weld, Ceylon and many other JBoss projects.
27. Dec 2013
11. Sep 2013
10. Jul 2013
22. Apr 2013
12. Mar 2013
14. Jan 2013
04. Dec 2012
02. Dec 2012
30. Oct 2012
12. Oct 2012
07. May 2012
22. Mar 2012
19. Jan 2012
06. Jan 2012
22. Nov 2011
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!
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.
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.
After successful Google I/O and Red Hat Summit presentations, and some vacation, it's finally time to do a new release.
Regarding the release issues, they've been mostly driven by TCK failures, hence I'll let the release notes speak for themselves.
Note: for the Windows users, an issue I just discovered after releasing the .zip, and it's unfortunately not as trivial as it looks like, hence I didn't want to stale the release even more. So the fix for this is coming in the next release.
The simple workaround is to run the full AS start command:
standalone.bat -c standalone-capedwarf.xml.
(and a bit more work if you wanna use GAE API jar as a module)
Apart from classic coding, it's been busy three months with a lot of news and new things around CapeDwarf project.
For those who missed my tweets about GAE TCK, here is the link again
It looks like we're getting more and more traction on the blog / article scene
- Ludo's blog, Google Cloud Platform
- The H Open
- Yefim Natis, Gartner
- Peter Magnusson, Google
Since JavaOne notifications are out, I can happily say that my Implementing your own Google App Engine talk got accepted. And I'll prolong my US stay with my visit to DC JBUG. Welcome to drop by!
Continuing with our monthly releases, we’re happy to announce new 1.0.0.Beta4 release.
- all logging data was moved into separate cache,
- enabled metadata handling,
- default cache is now “SYNC” by default (which made MapReduce tests very happy :-)),
- we put back legacy factory transformers - which means older GAE API versions now again work to some extent,
- Velocity is jarjar-ed - so it doesn’t conflict with your version anymore,
- we support static files handling - you don’t hit your filters and listeners anymore,
- and a bunch of other small tweaks.
CapeDwarf team will be at this year’s Google I/O’ Sandbox! Make sure you drop by for a chat, demo and a nice T-shirt.
Also be careful you don’t miss the exciting surprise announcement! ;-)
Download it here:
As you can see from the JIRA release notes, it’s been super busy 2 months.
Another new sub-project: CapeDwarf Shared.
It’s where we keep the shared code between our GAE API implementation (Blue) and JBossAS integration.
There has been a lot of detail polishing on Blobstore, Logging and TaskQueue. And we also added BlackList / WhiteList support, getting even closer to GAE behavior this way.
And yes, we finally simplified how you start the whole thing - thanks Lazo. ;-)
- ./capedwarf.sh or capedwarf.bat (in JBOSS_HOME/bin/) will do
As always, feedback welcome!
|Showing 1 to 5 of 35 blog entries||