You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2009/03/31 11:59:37 UTC

[jira] Created: (CAMEL-1505) deploy the CamelContext with velocity endpoint into the Servicemix 4.0 will get the NoClassDefFoundError

deploy the CamelContext with velocity endpoint into the Servicemix 4.0 will get the  NoClassDefFoundError
---------------------------------------------------------------------------------------------------------

                 Key: CAMEL-1505
                 URL: https://issues.apache.org/activemq/browse/CAMEL-1505
             Project: Apache Camel
          Issue Type: Bug
    Affects Versions: 2.0-M1, 1.6.0
            Reporter: Willem Jiang
            Assignee: Willem Jiang
             Fix For: 2.0.0, 1.6.1


[trace] ***********************************************************
********
 [debug] Starting Apache Velocity v1.5 (compiled: 2007-02-22 08:52:29)
 [trace] RuntimeInstance initializing.
 [debug] Default Properties File: org\apache\velocity\runtime\defaults\velocity.
properties
 [debug] Trying to use logger class org.apache.velocity.runtime.log.Log4JLogChut
e
 [debug] Couldn't find class org.apache.velocity.runtime.log.Log4JLogChute or ne
cessary supporting classes in classpath.
org/apache/log4j/Layout
java.lang.NoClassDefFoundError: org/apache/log4j/Layout
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:164)
        at org.apache.velocity.util.ClassUtils.getClass(ClassUtils.java:76)
        at org.apache.velocity.util.ClassUtils.getNewInstance(ClassUtils.java:95
)
        at org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.
java:147)


We can get around this issue by replacing the org.apache.velocity.runtime.log.Log4JLogChute with
org.apache.velocity.runtime.log.Log4JLogChute, and also need to update the Servicemix Velocity bundle to 1.6.

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


[jira] Resolved: (CAMEL-1505) deploy the CamelContext with velocity endpoint into the Servicemix 4.0 will get the NoClassDefFoundError

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

Willem Jiang resolved CAMEL-1505.
---------------------------------

    Resolution: Fixed

trunk
http://svn.apache.org/viewvc?rev=760779&view=rev
camel-1.x branch
http://svn.apache.org/viewvc?rev=760780&view=rev

> deploy the CamelContext with velocity endpoint into the Servicemix 4.0 will get the  NoClassDefFoundError
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1505
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1505
>             Project: Apache Camel
>          Issue Type: Bug
>    Affects Versions: 1.6.0, 2.0-M1
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.0.0, 1.6.1
>
>
> [trace] ***********************************************************
> ********
>  [debug] Starting Apache Velocity v1.5 (compiled: 2007-02-22 08:52:29)
>  [trace] RuntimeInstance initializing.
>  [debug] Default Properties File: org\apache\velocity\runtime\defaults\velocity.
> properties
>  [debug] Trying to use logger class org.apache.velocity.runtime.log.Log4JLogChut
> e
>  [debug] Couldn't find class org.apache.velocity.runtime.log.Log4JLogChute or ne
> cessary supporting classes in classpath.
> org/apache/log4j/Layout
> java.lang.NoClassDefFoundError: org/apache/log4j/Layout
>         at java.lang.Class.forName0(Native Method)
>         at java.lang.Class.forName(Class.java:164)
>         at org.apache.velocity.util.ClassUtils.getClass(ClassUtils.java:76)
>         at org.apache.velocity.util.ClassUtils.getNewInstance(ClassUtils.java:95
> )
>         at org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.
> java:147)
> We can get around this issue by replacing the org.apache.velocity.runtime.log.Log4JLogChute with
> org.apache.velocity.runtime.log.Log4JLogChute, and also need to update the Servicemix Velocity bundle to 1.6.

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