Details
-
Task
-
Resolution: Done
-
Minor
-
None
-
None
-
User Experience
Description
When I try to create imap server in mail subsystem, I can provide nonexistent reference to outbound-socket-binding-ref:
[standalone@localhost:9990 /] /subsystem=mail/mail-session=default/server=imap:add(outbound-socket-binding-ref=nonexistent) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } }
operation is successful and requires reload of server configuration. During configuration reload server complains that 'nonexistent' binding does not exist:
12:30:42,824 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "mail"), ("mail-session" => "default") ]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.outbound-socket-binding.nonexistent"], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.mail-session.default is missing [jboss.outbound-socket-binding.nonexistent]"] }
When I try similar action e.g. in Undertow subsystem, I get error rightaway during the add operation:
[standalone@localhost:9990 /] /subsystem=undertow/server=default-server/http-listener=moje:add(socket-binding=nonexistent) { "outcome" => "failed", "failure-description" => "WFLYCTL0369: Required capabilities are not available: org.wildfly.network.socket-binding.nonexistent; There are no known registration points which can provide this capability.", "rolled-back" => true }
I like Undertow's approach much more as user is directly warned that particular reference is not available. It would be nice if the same approach could be used also in mail subsystem. This applies on all three mail server types imap, pop3 and smtp during both add operation and also write-attribute operation.
Attachments
Issue Links
- clones
-
JBEAP-7459 Add capabilities to mail subsystem
-
- Closed
-
