[
https://issues.apache.org/activemq/browse/CAMEL-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53860#action_53860
]
Alan Feng commented on CAMEL-1953:
----------------------------------
Thanks. It is dependency issue. We are not using Maven here so it's very hard
to ensure all dependencies are included, especially the error is not a
"ClassNotFoundException".
Will it be possible to include a dependency list (by camel components) with
each release, auto-generated from your Maven settings?
> DefaultPackageScanClassResolver gives warning when matching anonymous inner
> class SftpOperations$1.class
> --------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-1953
> URL: https://issues.apache.org/activemq/browse/CAMEL-1953
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.0.0
> Environment: N/A
> Reporter: Alan Feng
> Assignee: Claus Ibsen
> Priority: Minor
>
> During a package scan in the DefaultPackageScanClassResolver class, it gives
> warning:
> WARN [DefaultPackageScanClassResolver] Could not find class
> 'org/apache/camel/component/file/remote/SftpOperations$1.class' in any
> classloaders: [sun.misc.launcher$appclassloa...@567c567c]
> However, the SftpOperations$1.class exists in the camel-ftp-2.0.0.jar file.
> To recreate this problem, use the following test class and make sure only
> include commons-logging.jar, camel-core-2.0.0.jar, and camel-ftp-2.0.0.jar in
> the classpath.
> import org.apache.camel.CamelContext;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.impl.DefaultCamelContext;
> public class CamelTest {
> public static void main(String[] args) throws Exception{
> CamelContext context = new DefaultCamelContext();
> context.start();
>
> context.addRoutes(new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from("direct:start").to("log:test?level=INFO");
> }
> });
> context.createProducerTemplate().sendBody("direct:start", "test");
> }
> }
> This bug can be reproduced with both IBM and Sun JDK.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
