You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Martin Krasser (JIRA)" <ji...@apache.org> on 2010/09/21 09:16:40 UTC

[jira] Created: (CAMEL-3140) Document required usage of JavaUUIDGenerator when running Camel on GAE

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.


[jira] Commented: (CAMEL-3140) Document required usage of JavaUUIDGenerator when running Camel on GAE

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61954#action_61954 ] 

Claus Ibsen commented on CAMEL-3140:
------------------------------------

Ah we should only change the generator if its the AMQ one so the code should be
{code}
        if (getUuidGenerator() instanceof ActiveMQUuidGenerator) {
            // use java uuid generator as ActiveMQ uses JDK API which is not allowed on GAE
            setUuidGenerator(new JavaUuidGenerator());
        }
{code}

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


[jira] Commented: (CAMEL-3140) Document required usage of JavaUUIDGenerator when running Camel on GAE

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61956#action_61956 ] 

Claus Ibsen commented on CAMEL-3140:
------------------------------------

@Martin

Ah that is a good idea. 

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


[jira] Resolved: (CAMEL-3140) Context-sensitive setting of default UuidGenerator

Posted by "Martin Krasser (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Krasser resolved CAMEL-3140.
-----------------------------------

    Resolution: Fixed

Revision: 1000565


> Context-sensitive setting of default UuidGenerator
> --------------------------------------------------
>
>                 Key: CAMEL-3140
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3140
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.4.0
>            Reporter: Martin Krasser
>            Assignee: Martin Krasser
>            Priority: Minor
>             Fix For: 2.5.0
>
>
> Use JavaUuidGenerator in GAE environment, otherwise use ActiveMQUuidGenerator as default UuidGenerator. 

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


[jira] Updated: (CAMEL-3140) Context-sensitive setting of default UuidGenerator

Posted by "Martin Krasser (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Krasser updated CAMEL-3140:
----------------------------------

        Summary: Context-sensitive setting of default UuidGenerator  (was: Document required usage of JavaUUIDGenerator when running Camel on GAE)
     Issue Type: Improvement  (was: Task)
    Description: Use JavaUuidGenerator in GAE environment, otherwise use ActiveMQUuidGenerator as default UuidGenerator.   (was: 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.)
    Component/s: camel-core
                     (was: camel-gae)

> Context-sensitive setting of default UuidGenerator
> --------------------------------------------------
>
>                 Key: CAMEL-3140
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3140
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.4.0
>            Reporter: Martin Krasser
>            Assignee: Martin Krasser
>            Priority: Minor
>             Fix For: 2.5.0
>
>
> Use JavaUuidGenerator in GAE environment, otherwise use ActiveMQUuidGenerator as default UuidGenerator. 

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


[jira] Commented: (CAMEL-3140) Document required usage of JavaUUIDGenerator when running Camel on GAE

Posted by "Martin Krasser (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62016#action_62016 ] 

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

Will add something like the following to {{DefaultCamelContext}}

{code:java|title=DefaultCamelContext.java}
    // ...
    private UuidGenerator uuidGenerator = createDefaultUuidGenerator();
    // ...
    private static UuidGenerator createDefaultUuidGenerator() {
        if (System.getProperty("com.google.appengine.runtime.environment") != null) {
            // either "Production" (on GAE) or "Development" (on local development server)
            return new JavaUuidGenerator();
        } else {
            return new ActiveMQUuidGenerator();
        }
    }
{code}

Then we can also revert the changes made to {{GaeDefaultCamelContext}} and {{GaeSpringCamelContext}}. Still need to test it on GAE, then I'll commit.

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


[jira] Commented: (CAMEL-3140) Document required usage of JavaUUIDGenerator when running Camel on GAE

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61953#action_61953 ] 

Claus Ibsen commented on CAMEL-3140:
------------------------------------

In the camel-gae component I will set the UUID to be the JavaUUIDGenerator explicitly.
{code}
     @Override
     protected void doStart() throws Exception {
-        disableJMX(); // JMX not allowed on GAE
+        // JMX not allowed on GAE
+        disableJMX();
+        // use java uuid generator as ActiveMQ uses JDK API which is not allowed on GAE
+        setUuidGenerator(new JavaUuidGenerator());
+
         super.doStart();
     }
{code}

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


[jira] Commented: (CAMEL-3140) Document required usage of JavaUUIDGenerator when running Camel on GAE

Posted by "Martin Krasser (JIRA)" <ji...@apache.org>.
    [ 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.