THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
GAE service | Camel component | Component description | |
|---|---|---|---|
Provides connectivity to the GAE URL fetch service but can also be used to receive messages from servlets. | |||
Supports asynchronous message processing on GAE by using the task queueing service as message queue. | |||
Supports sending of emails via the GAE mail service. Receiving mails is not supported yet but will be added later. | |||
| Not supported yet. | ||
| Not supported yet. | ||
| Not supported yet. | ||
| Not supported yet. | ||
| These components interact with the Google Accounts API for authentication and authorization. Google Accounts Not supported yet. The Google Accounts service is not specific to Google App Engine but is often used by GAE applications for authentication and authorization. See also #Security sectionimplementing security. The gauth component is used by web applications to implement a Google-specific OAuth consumer. This component can also be used to OAuth-enable non-GAE web applications. The glogin component is used by Java clients (outside GAE) for programmatic login to GAE applications. For instructions how to protect GAE applications against unauthorized access refer to the Security for Camel GAE applications page. |
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
...
.