Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <26147965.26141285060120663.JavaMail.jira@thor>
Date: Tue, 21 Sep 2010 05:08:40 -0400 (EDT)
From: "Martin Krasser (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-3140) Document required usage of
 JavaUUIDGenerator when running Camel on GAE
In-Reply-To: <13328046.26051285053400395.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/CAMEL-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61955#action_61955 ] 

Martin Krasser commented on CAMEL-3140:
---------------------------------------

When an application uses the GAE-specific CamelContext implementations provided by camel-gae, then your changes free applications from doing any additional configurations. With this ticket I was mainly referring to cases where applications use the camel-spring XML namespaces for configuring a SpringCamelContext (this became possible after GAE introduced support for JAXB). In these cases the apps need to change the UUID generator explicitly. Maybe we can free applications from doing that as well by introducing an environment-sensitive UUID generator factory (i.e. one that detects wether it is running on GAE). I'll think about that and come up with a proposal. (Hope to find some time tomorrow).

> Document required usage of JavaUUIDGenerator when running Camel on GAE
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-3140
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3140
>             Project: Apache Camel
>          Issue Type: Task
>          Components: camel-gae
>    Affects Versions: 2.4.0
>            Reporter: Martin Krasser
>            Assignee: Martin Krasser
>            Priority: Minor
>             Fix For: 2.5.0
>
>
> JavaUUIDGenerator won't be the default one in Camel 2.5 and Camel GAE apps will need to configure the JavaUUIDGenerator explicitly. The former ActiveMQUUIDGenerator uses APIs that are not on the GAE JDK whitelist.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.