[jboss-jira] [JBoss JIRA] (JBEE-250) JBoss Modules based resolution executed too early in FactoryFinder

[Alessio Soldano (Jira)]

    [ https://issues.redhat.com/browse/JBEE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951075#comment-13951075 ] 

Alessio Soldano commented on JBEE-250:
--------------------------------------

Fixed with https://github.com/jboss/jboss-jakarta-saaj-api_spec/commit/9880c34333419c43a7609a470aa443ff9d1b6fba

> JBoss Modules based resolution executed too early in FactoryFinder
> ------------------------------------------------------------------
>
>                 Key: JBEE-250
>                 URL: https://issues.redhat.com/browse/JBEE-250
>             Project: JBoss Enterprise Spec APIs
>          Issue Type: Bug
>          Components: jboss-saaj-api
>            Reporter: Alessio Soldano
>            Assignee: Jim Ma
>            Priority: Major
>             Fix For: jboss-jakarta-saaj-api_1.4_spec-1.0.2.Final
>
>
> Our fork of SAAJ spec api uses JBoss Modules as one of the mechanisms for resolving factories; it looks like the resolution through jboss modules is attempted (when jboss-modules jar being available in the classpath) too early and that can result in a classloading issue when trying creating a SAAJMetaFactory instance.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)