February 2016 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3978) Upgrade to Apache CXF 3.1.5

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3978?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3978: ---------------------------------- Issue Type: Component Upgrade (was: Task) > Upgrade to Apache CXF 3.1.5 > --------------------------- > > Key: JBWS-3978 > URL: https://issues.jboss.org/browse/JBWS-3978 > Project: JBoss Web Services > Issue Type: Component Upgrade > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3977) slf4j is used by ws security related bits, logging bridge probably needed

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3977?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3977: --------------------------------------- [~rsvoboda] can you please specify here the contents of the pom.xml that's setting the dependencies and/or provide a dependency:tree? (EAP productized bits being used, or community ones?) > slf4j is used by ws security related bits, logging bridge probably needed > ------------------------------------------------------------------------- > > Key: JBWS-3977 > URL: https://issues.jboss.org/browse/JBWS-3977 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.1.3.Final > Reporter: Rostislav Svoboda > Priority: Minor > Fix For: jbossws-cxf-5.2.0.Final > > > WS security related bits use slf4j and warning message is logged on client > Logging bridge is probably needed. > {code} > 13:01:11,794 INFO [AbstractPerfJUnitTest] Running wsse.SimpleSignEncryptTest > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > {code} > workaround is to add dependency like: > {code} > <dependency>  > <groupId>org.slf4j</groupId> > <artifactId>slf4j-log4j12</artifactId> > <version>1.7.7</version> > <scope>test</scope> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3950) Broken link on developers.redhat.com

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3950?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3950: --------------------------------------- [~dcoughlin1] Is there (still) any action to take here? Otherwise I'd close this jira. > Broken link on developers.redhat.com > ------------------------------------ > > Key: JBWS-3950 > URL: https://issues.jboss.org/browse/JBWS-3950 > Project: JBoss Web Services > Issue Type: Feature Request > Reporter: Daniel Coughlin > > The following broken link is currently listed against this project on developers.redhat.com/projects. > http://jbossws-qa.jboss.org:8180/hudson - Hudson Link > If you maintain a project.properties file that you have told the RHD team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3978) Upgrade to Apache CXF 3.1.5

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3978: ------------------------------------- Summary: Upgrade to Apache CXF 3.1.5 Key: JBWS-3978 URL: https://issues.jboss.org/browse/JBWS-3978 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.2.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3977) slf4j is used by ws security related bits, logging bridge probably needed

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3977?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3977: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.0.Final > slf4j is used by ws security related bits, logging bridge probably needed > ------------------------------------------------------------------------- > > Key: JBWS-3977 > URL: https://issues.jboss.org/browse/JBWS-3977 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.1.3.Final > Reporter: Rostislav Svoboda > Priority: Minor > Fix For: jbossws-cxf-5.2.0.Final > > > WS security related bits use slf4j and warning message is logged on client > Logging bridge is probably needed. > {code} > 13:01:11,794 INFO [AbstractPerfJUnitTest] Running wsse.SimpleSignEncryptTest > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > {code} > workaround is to add dependency like: > {code} > <dependency>  > <groupId>org.slf4j</groupId> > <artifactId>slf4j-log4j12</artifactId> > <version>1.7.7</version> > <scope>test</scope> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3977) slf4j is used by ws security related bits, logging bridge probably needed

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/JBWS-3977?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda updated JBWS-3977: ------------------------------------ Affects Version/s: jbossws-cxf-5.1.3.Final > slf4j is used by ws security related bits, logging bridge probably needed > ------------------------------------------------------------------------- > > Key: JBWS-3977 > URL: https://issues.jboss.org/browse/JBWS-3977 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.1.3.Final > Reporter: Rostislav Svoboda > Priority: Minor > > WS security related bits use slf4j and warning message is logged on client > Logging bridge is probably needed. > {code} > 13:01:11,794 INFO [AbstractPerfJUnitTest] Running wsse.SimpleSignEncryptTest > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > {code} > workaround is to add dependency like: > {code} > <dependency>  > <groupId>org.slf4j</groupId> > <artifactId>slf4j-log4j12</artifactId> > <version>1.7.7</version> > <scope>test</scope> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3977) slf4j is used by ws security related bits, logging bridge probably needed

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created JBWS-3977: --------------------------------------- Summary: slf4j is used by ws security related bits, logging bridge probably needed Key: JBWS-3977 URL: https://issues.jboss.org/browse/JBWS-3977 Project: JBoss Web Services Issue Type: Bug Reporter: Rostislav Svoboda Priority: Minor WS security related bits use slf4j and warning message is logged on client Logging bridge is probably needed. {code} 13:01:11,794 INFO [AbstractPerfJUnitTest] Running wsse.SimpleSignEncryptTest SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. {code} workaround is to add dependency like: {code} <dependency>  <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>1.7.7</version> <scope>test</scope> </dependency> {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3976) Two different versions of ASM artifact in client dependency tree

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3976?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3976: ---------------------------------- Project: JBoss Web Services (was: JBoss Enterprise Application Platform) Key: JBWS-3976 (was: JBEAP-3249) Workflow: classic default workflow (was: CDW with loose statuses v1) Status: Open (was: New) Component/s: jbossws-cxf productization (was: Web Services) Target Release: (was: 7.0.0.GA) Affects Version/s: (was: 7.0.0.ER5) > Two different versions of ASM artifact in client dependency tree > ---------------------------------------------------------------- > > Key: JBWS-3976 > URL: https://issues.jboss.org/browse/JBWS-3976 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > > In dependency tree of jbossws-cxf-client 5.1.3.Final-redhat-2, there are two different versions of ASM artifact: > {noformat} > +- org.apache.cxf:cxf-rt-frontend-jaxws:jar:3.1.4.redhat-1:compile > | +- xml-resolver:xml-resolver:jar:1.2.0.redhat-11:compile > | +- org.ow2.asm:asm:jar:5.0.4:compile > +- asm:asm:jar:3.3.1.redhat-12:compile > {noformat} > It should probably be chosen which one to keep and exclude the other. > See [upstream client tree|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-...] and [productized client tree with BOM import|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3976) Two different versions of ASM artifact in client dependency tree

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3976?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3976: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.0.Final > Two different versions of ASM artifact in client dependency tree > ---------------------------------------------------------------- > > Key: JBWS-3976 > URL: https://issues.jboss.org/browse/JBWS-3976 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.0.Final > > > In dependency tree of jbossws-cxf-client 5.1.3.Final-redhat-2, there are two different versions of ASM artifact: > {noformat} > +- org.apache.cxf:cxf-rt-frontend-jaxws:jar:3.1.4.redhat-1:compile > | +- xml-resolver:xml-resolver:jar:1.2.0.redhat-11:compile > | +- org.ow2.asm:asm:jar:5.0.4:compile > +- asm:asm:jar:3.3.1.redhat-12:compile > {noformat} > It should probably be chosen which one to keep and exclude the other. > See [upstream client tree|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-...] and [productized client tree with BOM import|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3975) Create ASIL for WildFly 10.0.0.Final

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3975: ------------------------------------- Summary: Create ASIL for WildFly 10.0.0.Final Key: JBWS-3975 URL: https://issues.jboss.org/browse/JBWS-3975 Project: JBoss Web Services Issue Type: Task Reporter: Alessio Soldano Fix For: jbossws-cxf-5.2.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues February 2016