[jboss-jira] [JBoss JIRA] (WFLY-9990) module not found exception org.kohsuke.rngom

[Amine Achouri (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amine Achouri updated WFLY-9990:
--------------------------------
    Description: 
before the version 9.0 final, the module org.kohsuke.rngom exist as Jboss or wildfly module. but with the newer versions of wildfly 9.0, 10, 11 and the versions of Jboss EAP 7.0 and 7.1, this module was replaced by the name of the jar  rngom-2.2.11.jbossorg-1, directly putted near jaxb-iml on the path "com/sun/xml/bind/", but  what we remark is that the module.xml com/sun/xml/bind/main still referencing org.kohsuke.rngom as module and this what generate the module not found exception: 
the solution, to avoid such module not found exception, that worked with me was to delete the reference of org.kohsuke.rngom as a module and this work fine since it will be implicitly used by jaxbimpl.

need to validate this.

  was:
before the version 9.0 final, the module org.kohsuke.rngom exit as Jboss or wildfly module. but with the newer versions of wildfly 9.0, 10, 11 and the versions of Jboss EAP 7.0 and 7.1, this module was replaced by the name of the jar  rngom-2.2.11.jbossorg-1, directly putted near jaxb-iml on the path "com/sun/xml/bind/", but  what we remark is that the module.xml com/sun/xml/bind/main still referencing org.kohsuke.rngom as module and this what generate the module not found exception: 
the solution, to avoid such module not found exception, that worked with me was to delete the reference of org.kohsuke.rngom as a module and this work fine since it will be implicitly used by jaxbimpl.

need to validate this.



> module not found exception org.kohsuke.rngom
> --------------------------------------------
>
>                 Key: WFLY-9990
>                 URL: https://issues.jboss.org/browse/WFLY-9990
>             Project: WildFly
>          Issue Type: Bug
>          Components: JAXR
>    Affects Versions: 10.0.0.Final, 12.0.0.Final
>            Reporter: Amine Achouri
>            Assignee: Kurt Stam
>             Fix For: 12.0.0.Final
>
>
> before the version 9.0 final, the module org.kohsuke.rngom exist as Jboss or wildfly module. but with the newer versions of wildfly 9.0, 10, 11 and the versions of Jboss EAP 7.0 and 7.1, this module was replaced by the name of the jar  rngom-2.2.11.jbossorg-1, directly putted near jaxb-iml on the path "com/sun/xml/bind/", but  what we remark is that the module.xml com/sun/xml/bind/main still referencing org.kohsuke.rngom as module and this what generate the module not found exception: 
> the solution, to avoid such module not found exception, that worked with me was to delete the reference of org.kohsuke.rngom as a module and this work fine since it will be implicitly used by jaxbimpl.
> need to validate this.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)