[
https://issues.jboss.org/browse/WFCORE-966?page=com.atlassian.jira.plugin...
]
James Perkins commented on WFCORE-966:
--------------------------------------
The issue is the profile isn't running and therefore runtime stage steps are not run.
In some cases validation only runs at runtime since it's the best place to validate
whether or not something like a handler exists. Some thought would have to go into the
best way to validate this. It won't allow the profile to actually boot as it would
fail in the runtime stages.
I'll leave this unscheduled for now as it's likely fixable, just needs to be well
thought out.
In domain mode non existing subhandler is saved to attributes.
--------------------------------------------------------------
Key: WFCORE-966
URL:
https://issues.jboss.org/browse/WFCORE-966
Project: WildFly Core
Issue Type: Bug
Components: Logging
Environment: Running unsecured EAP 7.0.0 DR9 version in domain mode.
Reporter: Patrik Cyprian
Assignee: James Perkins
When you in domain mode in created async handler add non existing sub handler to
attributes it is successfully saved. In standalone mode it is not possible (subhandler is
not saved - saving operation failed).
1.Run EAP in domain mode (default profile)
2.Create async handler
3.Try to add non existing subhandler to async handler attributes
4.Try the same in standalone mode with standalone-full-ha profile
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)