[
https://issues.apache.org/jira/browse/SLING-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044689#comment-16044689
]
Oliver Lietz commented on SLING-6949:
-------------------------------------
[~rombert], I do not understand your problem but have a look at
[Fling|https://github.com/apache/sling/tree/trunk/samples/fling] and [Commons
Messaging
Mail|https://github.com/apache/sling/tree/trunk/bundles/commons/org.apache.sling.commons.messaging.mail]
where mails are sent and read.
Is it for AEM where your instance is not controlled by the test framework in
JVM but over HTTP?
> Create testing utilities for email-enabled applications
> -------------------------------------------------------
>
> Key: SLING-6949
> URL: https://issues.apache.org/jira/browse/SLING-6949
> Project: Sling
> Issue Type: New Feature
> Components: Testing
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
>
> When working with email-enabled applications it is sometimes desirable to
> interact with the emails send by the applications, either by verifying the
> contents of the emails or just validating that a certain email is sent.
> A good solution for this is
> [Wiser|https://github.com/voodoodyne/subethasmtp/blob/master/Wiser.md], which
> works quite well.
> One scenario where this does not apply is when the application under test is
> running as a container, and it cannot access the host application to deliver
> emails to the Wiser instance.
> To have an unitary approach I propose that we create an OSGi bundle which
> wraps Wiser and starts in the Sling application. The messages received by
> Wiser can then be read using an HTTP API.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
