[jboss-jira] [JBoss JIRA] (ELY-428) HTTP Mechanism configuration during deployment

[Darran Lofthouse (JIRA)]

    [ https://issues.jboss.org/browse/ELY-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179012#comment-13179012 ] 

Darran Lofthouse commented on ELY-428:
--------------------------------------

We discussed this during our design sessions this week, the outcome was: -

Mechanisms will be able to access resources from their application, however they will not be able to do this until the first request is received making this a lazy approach to initialisation, in addition to this we will have an 'Application' attachment context the mechanism can use to cache this.

The alternative for mechanisms is to provide a pre-configured mechanism factory that will have already managed that configuration in advance.

> 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.Beta5
>
>
> 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)