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.
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.