[
https://issues.jboss.org/browse/ELY-428?page=com.atlassian.jira.plugin.sy...
]
Darran Lofthouse resolved ELY-428.
----------------------------------
Resolution: Rejected
This issue has been discussed.
The Elytron HTTP mechanism framework is based around mechanisms being stateless so there
is no 'on deployment' step from the perspective of the mechanism. Mechanisms
however can store state in scopes and so on first access if required information is not in
the scope generate it and store it.
Within the application server alternative mechanism factories can be provided by other
subsystems which have the option of subsystem level configuration instead of configuraton
bundled within a deployment.
HTTP Mechanism configuration during deployment
----------------------------------------------
Key: ELY-428
URL:
https://issues.jboss.org/browse/ELY-428
Project: WildFly Elytron
Issue Type: Enhancement
Components: HTTP
Affects Versions: 1.0.2.Final
Reporter: Pedro Igor
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 1.1.0.Beta9
It should be possible to configure a HTTP mechanism during deployment in order to
parse/load configuration and reuse it in subsequent requests to an application.
The most common use case for that is around mechanisms that need to read some
configuration from inside a deployment (or provided by the mech config) when it is being
deployed to the server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)