[
https://issues.jboss.org/browse/WFLY-1409?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on WFLY-1409:
-----------------------------------------------
Jakub Cechacek <jcechace(a)redhat.com> changed the Status of [bug
968200|https://bugzilla.redhat.com/show_bug.cgi?id=968200] from ON_QA to VERIFIED
custom mail server should allow definition of independent properties
--------------------------------------------------------------------
Key: WFLY-1409
URL:
https://issues.jboss.org/browse/WFLY-1409
Project: WildFly
Issue Type: Feature Request
Components: Mail
Reporter: Jakub Cechacek
Assignee: Tomaz Cerar
Priority: Minor
Fix For: 8.0.0.Beta1
Current implementation doesn't allow definition of independent properties - instead
they will always have form of "mail.$ServerName.someprop". Thus it's not
possible to setup properties such as "mail.transport.protocol"[1] inside custom
server.
Also customer will unlikely design custom transport protocol from scratch. More often it
will be just a wrapper around existing protocol such as smtp with some additional
functionality (this is also case of [2]). However as a workaround one can define custom
server together with server for underlying protocol within one mail session.
[1] which will cause session.getTransport(); to return null as default protocol is not
set.
[2]
https://c.na7.visual.force.com/apex/Case_View?id=500A000000A4N8b
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira