[jboss-jira] [JBoss JIRA] (WFCORE-4961) Move PARSE_MICROPROFILE_JWT_DETECTION Earlier
Darran Lofthouse (Jira)
issues at jboss.org
Wed May 6 06:11:00 EDT 2020
[ https://issues.redhat.com/browse/WFCORE-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darran Lofthouse resolved WFCORE-4961.
--------------------------------------
Resolution: Rejected
Checking further from WarMetaData we need warMetaData.getMergedJBossWebMetaData() however this is set by DUP WarMetaDataProcessor which is installed at PARSE_WEB_MERGE_METADATA = 0x2000.
This is after the DUP we are trying to get before at 0x1150 so an alternative will be needed instead.
> Move PARSE_MICROPROFILE_JWT_DETECTION Earlier
> ---------------------------------------------
>
> Key: WFCORE-4961
> URL: https://issues.redhat.com/browse/WFCORE-4961
> Project: WildFly Core
> Issue Type: Task
> Components: Server
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 12.0.0.Beta3
>
>
> JwtActivationProcessor is presently installed at PARSE_MICROPROFILE_JWT_DETECTION = 0x4C0D
> However I need it to have performed it's activation check before: -
> AnnotatedEJBComponentDescriptionDeploymentUnitProcessor which is installed at PARSE_CREATE_COMPONENT_DESCRIPTIONS = 0x1150
> JwtActivationProcessor depends on two attachments.
> WarMetaData.ATTACHMENT_KEY which is created by WarStructureDeploymentProcessor and installed at STRUCTURE_WAR = 0x0900 - So before Phase.PARSE.
> Attachments.COMPOSITE_ANNOTATION_INDEX which is created by CompositeIndexProcessor and installed at PARSE_COMPOSITE_ANNOTATION_INDEX = 0x0301
> So anywhere after 0x0301 but before 0x1150 should be safe.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jboss-jira
mailing list