March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9993) Upgrade Picketlink and Picketlink Bindings from 2.5.5.SP9 to 2.5.5.SP10

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-9993?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos reassigned WFLY-9993: --------------------------------------------- Assignee: Peter Skopek (was: Panagiotis Sotiropoulos) > Upgrade Picketlink and Picketlink Bindings from 2.5.5.SP9 to 2.5.5.SP10 > ----------------------------------------------------------------------- > > Key: WFLY-9993 > URL: https://issues.jboss.org/browse/WFLY-9993 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Panagiotis Sotiropoulos > Assignee: Peter Skopek > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9993) Upgrade Picketlink and Picketlink Bindings from 2.5.5.SP9 to 2.5.5.SP10

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-9993?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos moved JBEAP-14358 to WFLY-9993: ------------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9993 (was: JBEAP-14358) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Affects Version/s: (was: 7.1.0.GA) Fix Version/s: (was: 7.1.2.GA) > Upgrade Picketlink and Picketlink Bindings from 2.5.5.SP9 to 2.5.5.SP10 > ----------------------------------------------------------------------- > > Key: WFLY-9993 > URL: https://issues.jboss.org/browse/WFLY-9993 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9992) The hibernate4 README file still refers to the renamed hibernate5 quickstart

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9992?page=com.atlassian.jira.plugin.... ] Sande Gilda reassigned WFLY-9992: --------------------------------- Assignee: Sande Gilda (was: Tomaz Cerar) > The hibernate4 README file still refers to the renamed hibernate5 quickstart > ---------------------------------------------------------------------------- > > Key: WFLY-9992 > URL: https://issues.jboss.org/browse/WFLY-9992 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Sande Gilda > > The hibernate5 quickstart was renamed to hibernate. The hibernate4 README file still refers to the old name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9992) The hibernate4 README file still refers to the renamed hibernate5 quickstart

by Sande Gilda (JIRA)

Sande Gilda created WFLY-9992: --------------------------------- Summary: The hibernate4 README file still refers to the renamed hibernate5 quickstart Key: WFLY-9992 URL: https://issues.jboss.org/browse/WFLY-9992 Project: WildFly Issue Type: Bug Components: Quickstarts Reporter: Sande Gilda Assignee: Tomaz Cerar The hibernate5 quickstart was renamed to hibernate. The hibernate4 README file still refers to the old name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

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

by Amine Achouri (JIRA)

[ https://issues.jboss.org/browse/WFLY-9990?page=com.atlassian.jira.plugin.... ] 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 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 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. > 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 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)

8 years, 4 months

1
0
0 / 0

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

by Amine Achouri (JIRA)

[ https://issues.jboss.org/browse/WFLY-9990?page=com.atlassian.jira.plugin.... ] 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)

8 years, 4 months

1
0
0 / 0

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

by Aminer Achouri (JIRA)

[ https://issues.jboss.org/browse/WFLY-9990?page=com.atlassian.jira.plugin.... ] Aminer Achouri updated WFLY-9990: --------------------------------- Summary: module not found exception org.kohsuke.rngom (was: module not found expection org.kohsuke.rngom) > 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: Aminer Achouri > Assignee: Kurt Stam > Fix For: 12.0.0.Final > > > 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. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

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

by Aminer Achouri (JIRA)

[ https://issues.jboss.org/browse/WFLY-9990?page=com.atlassian.jira.plugin.... ] Aminer Achouri updated WFLY-9990: --------------------------------- Description: 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. 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 execption: 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 implicilty used by jaxbimpl. need to validate this. > module not found expection 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: Aminer Achouri > Assignee: Kurt Stam > Fix For: 12.0.0.Final > > > 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. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

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

by Aminer Achouri (JIRA)

[ https://issues.jboss.org/browse/WFLY-9990?page=com.atlassian.jira.plugin.... ] Aminer Achouri updated WFLY-9990: --------------------------------- Description: 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 execption: 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 implicilty 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 execption: the solution that worked with me was to delete the reference of org.kohsuke.rngom as a module and this work fine. need to validate this. > module not found expection 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: Aminer Achouri > Assignee: Kurt Stam > Fix For: 12.0.0.Final > > > 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 execption: > 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 implicilty used by jaxbimpl. > need to validate this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9991) Create http-custom-mechanism quickstart

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9991?page=com.atlassian.jira.plugin.... ] Sande Gilda reopened WFLY-9991: ------------------------------- > Create http-custom-mechanism quickstart > --------------------------------------- > > Key: WFLY-9991 > URL: https://issues.jboss.org/browse/WFLY-9991 > Project: WildFly > Issue Type: Enhancement > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Sande Gilda > Fix For: 13.0.0.Beta1 > > > Create a quickstart that demonstrates how to implement a custom HTTP authentication mechanism. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2018