[
https://issues.apache.org/activemq/browse/CAMEL-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48438#action_48438
]
Claus Ibsen commented on CAMEL-1215:
------------------------------------
And if so then the Dummy classes could stay in the camel-mail.jar.
If still a problem then we need to write a little bit on the camel mail wiki
about this change.
> Moved the DummyTrustManager and DummySSLSocketFactory into src/test/java
> directory
> ----------------------------------------------------------------------------------
>
> Key: CAMEL-1215
> URL: https://issues.apache.org/activemq/browse/CAMEL-1215
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-mail
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Priority: Minor
> Fix For: 1.5.1, 2.0.0
>
>
> DummyTrustManager and DummySSLSocketFactory is for the unit test, so we need
> to move it into src/test/java directory.
> So we can avoid the class not found error in OSGI environment like this.
> {code}
> Could not find class
> 'org/apache/camel/component/mail/security/DummyTrustManager.class' in any
> classloaders: [BundleDelegatingClassLoader for [camel-mail-osgi
> (camel-mail-osgi)], 102.0,
> BundleDelegatingClassLoader for [camel-mail-osgi (camel-mail-osgi)],
> BundleDelegatingClassLoader for [camel-mail-osgi (camel-mail-osgi)]]
> Could not find class
> 'org/apache/camel/component/mail/security/DummySSLSocketFactory.class' in any
> classloaders: [BundleDelegatingClassLoader for [camel-mail-osgi
> (camel-mail-osgi)], 102.0,
> BundleDelegatingClassLoader for [camel-mail-osgi (camel-mail-osgi)],
> BundleDelegatingClassLoader for [camel-mail-osgi (camel-mail-osgi)]]
> {code}
> If the other module wants to extends camel-mail, it should also include the
> camel-mail-test.jar for unit testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
