Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Camel components for Google App Engine (GAE) are part of the camel-gae project and provide connectivity to GAE's cloud computing services. They make the GAE cloud computing environment accessible to applications via Camel interfaces. Following this pattern for other cloud computing environments could make it easier to port Camel applications from one cloud computing provider to another. The following table lists the cloud computing services provided by Google App Engine and the supporting Camel components. The documentation of each component can be found by following the link in the Camel Component column.

GAE service

Camel component

Component description

URL fetch service

ghttp

Provides connectivity to the GAE URL fetch service but can also be used to receive messages from servlets.

Task queueing service

gtask

Supports asynchronous message processing on GAE by using the task queueing service as message queue.

Mail service

gmail

Supports sending of emails via the GAE mail service. Receiving mails is not supported yet but will be added later.

Memcache service

 

Not supported yet.

XMPP service

 

Not supported yet.

Images service

 

Not supported yet.

Datastore service

 

Not supported yet.

Authentication service

 

gauth

Provides access to the Google authentication services

  • Allow Camel client applications to login to Google App Engine services
  • Allow Camel GAE applications to login to other Google services (e.g. calendar)
Not supported yet.

Camel context

Setting up a SpringCamelContext on Google App Engine differs between Camel 2.1 and Camel 2.2. The problem is that usage of the Camel-specific Spring configuration XML schema from the http://camel.apache.org/schema/spring namespace requires JAXB and Camel 2.1 depends on a Google App Engine SDK version that doesn't support JAXB yet.

...

The location of the Spring application context XML file is given by the contextConfigLocation init parameter. The appctx.xml file must be on the classpath. The servlet mapping makes the Camel application accessible under http://<appname>.appspot.com/camel/... when deployed to Google App Engine where <appname> must be replaced by a real GAE application name. The second servlet mapping is used internally by the task queueing service for background processing via web hooks. This mapping is relevant for the gtask component and is explained there in more detail.

Security

  • For instructions how to protect Camel applications on GAE refer to Security for Camel GAE Applications page.
  • The gauth component provides access to the Google authentication services and can also be used outside Google App Engine.