March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1372) CompositeIndexProcessor::calculateModuleIndex does not respect import filters

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1372?page=com.atlassian.jira.plugi... ] Stuart Douglas commented on WFCORE-1372: ---------------------------------------- Not sure what you mean? This happens before the module exists, so we have to manually iterate dependencies. > CompositeIndexProcessor::calculateModuleIndex does not respect import filters > ----------------------------------------------------------------------------- > > Key: WFCORE-1372 > URL: https://issues.jboss.org/browse/WFCORE-1372 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Alessio Soldano > Assignee: David Lloyd > > I have a deployment whose manifest declares > {noformat}Dependencies: org.foo annotations{noformat} > What I'm trying to do with the org.foo module is basically filtering (and exposing) a subset of the org.apache.cxf.impl module. To achieve that, I have the following module.xml: > {noformat} > <module xmlns="urn:jboss:module:1.3" name="org.foo"> > <resources> > </resources> > <dependencies> > <module name="org.apache.cxf.impl" services="import"> > <imports> > <include path="META-INF/cxf"/> > <include path="META-INF"/> > <include path="org/apache/cxf/sts"/> > <include path="org/apache/cxf/sts/**"/> > <include path="org/apache/cxf/ws/security/sts/**"/> > </imports> > <exports> > <include path="META-INF/cxf"/> > <include path="META-INF"/> > <include path="org/apache/cxf/sts"/> > <include path="org/apache/cxf/sts/**"/> > <include path="org/apache/cxf/ws/security/sts/**"/> > </exports> > </module> > <module name="asm.asm" /> > <module name="javax.api" /> > <module name="javax.annotation.api" /> > <module name="javax.validation.api"/> > <module name="javax.jms.api" /> > <module name="javax.jws.api" /> > <module name="javax.mail.api" /> > <module name="javax.resource.api" /> > <module name="javax.servlet.api" /> > <module name="javax.wsdl4j.api" /> > <module name="javax.xml.bind.api" services="import"/> > <module name="com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider"/> > <module name="com.sun.xml.bind" services="import"/> > <module name="javax.xml.soap.api" /> > <module name="javax.xml.stream.api" /> > <module name="javax.xml.ws.api" /> > <module name="javax.ws.rs.api" /> > <module name="org.apache.commons.lang" /> > <module name="org.apache.httpcomponents"/> > <module name="org.apache.neethi" /> > <module name="org.apache.velocity" /> > <module name="org.apache.xml-resolver" /> > <module name="org.apache.ws.xmlschema" /> > <module name="org.apache.ws.security" /> > <module name="org.apache.santuario.xmlsec" /> > <module name="org.codehaus.jettison" /> > <module name="org.codehaus.woodstox" /> > <module name="org.joda.time" /> > <module name="org.opensaml" /> > </dependencies> > </module> > {noformat} > The problem I'm having is that the composite annotation index that's attached to my deployment includes annotations from org.apache.cxf.impl module classes that are not included in the imports/exports above. > To me, this is due to the CompositeIndexProcessor::calculateModuleIndex(Module module) method that uses PathFilters.getDefaultImportFilter() (instead of my filters) for adding stuff to the index. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-36) Script To Compare Actual vs Expected Services JSON

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-36?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-36: ------------------------------ Team: Saturn (was: Saturn) > Script To Compare Actual vs Expected Services JSON > -------------------------------------------------- > > Key: SWSQE-36 > URL: https://issues.jboss.org/browse/SWSQE-36 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Create simple/prototype script to compare Actual SWS JSON vs Expected ISTIO Services Graph JSON. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-36) Script To Compare Actual vs Expected Services JSON

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-36?page=com.atlassian.jira.plugin.s... ] Matt Mahoney commented on SWSQE-36: ----------------------------------- Note: JSON validation was done manually for Sprint-1 https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... > Script To Compare Actual vs Expected Services JSON > -------------------------------------------------- > > Key: SWSQE-36 > URL: https://issues.jboss.org/browse/SWSQE-36 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Create simple/prototype script to compare Actual SWS JSON vs Expected ISTIO Services Graph JSON. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-13) Deploy Simple Service Mesh Configuration

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-13?page=com.atlassian.jira.plugin.s... ] Matt Mahoney resolved SWSQE-13. ------------------------------- Resolution: Done > Deploy Simple Service Mesh Configuration > ---------------------------------------- > > Key: SWSQE-13 > URL: https://issues.jboss.org/browse/SWSQE-13 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Matt Mahoney > > Create a simple Service Mesh which produces "real" data, which will be used for Service Graph validation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-12) Test IBM Istio Resilient as option to Service Mesh

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-12?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo closed SWSQE-12. ---------------------------------------- Resolution: Done > Test IBM Istio Resilient as option to Service Mesh > -------------------------------------------------- > > Key: SWSQE-12 > URL: https://issues.jboss.org/browse/SWSQE-12 > Project: Swift Sunshine QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > https://github.com/IBM/resilient-java-microservices-with-istio -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-2) Service Graph Acceptance Tests

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-2?page=com.atlassian.jira.plugin.sy... ] Matt Mahoney resolved SWSQE-2. ------------------------------ Resolution: Done > Service Graph Acceptance Tests > ------------------------------ > > Key: SWSQE-2 > URL: https://issues.jboss.org/browse/SWSQE-2 > Project: Swift Sunshine QE > Issue Type: Epic > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Acceptance Criteria - 1 Verify graph against Prometheus metrics graphs - data should be the same > Acceptance Criteria - 2 Verify graph against ISTIO graphs - data should be the same -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-58) Move ConnectionValidator interface to AgroalConnectionPoolConfiguration

by Luis Barreiro (JIRA)

Luis Barreiro created AG-58: ------------------------------- Summary: Move ConnectionValidator interface to AgroalConnectionPoolConfiguration Key: AG-58 URL: https://issues.jboss.org/browse/AG-58 Project: Agroal Issue Type: Bug Components: api Affects Versions: 0.4 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.5 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-57) Rename AgroalConnectionFactoryConfiguration.driverClassName()

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-57?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-57. ----------------------------- Resolution: Done {{AgroalConnectionFactoryConfiguration.driverClassName()}} got deprecated and {{ClassLoaderProvider}} as well. Add {{AgroalConnectionFactoryConfiguration.connectionProviderClass()}} instead. The connection provider class can still be loaded from a String, using either {{AgroalConnectionFactoryConfigurationSupplier}} or {{AgroalPropertiesReader}} > Rename AgroalConnectionFactoryConfiguration.driverClassName() > ------------------------------------------------------------- > > Key: AG-57 > URL: https://issues.jboss.org/browse/AG-57 > Project: Agroal > Issue Type: Bug > Components: api > Affects Versions: 0.4 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.5 > > > After AG-54 the connection factory can create connections from multiple sources, not only a java.sql.Driver. Therefore the name of the property should be changed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9917) renewal of server certificate for Undertow without restarting server

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9917?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-9917: ---------------------------------------- If there's no other solution, sure. Using allow-resource-service-restart=true is not a good improvement vs a reload. It should not be the basis of a feature. > renewal of server certificate for Undertow without restarting server > -------------------------------------------------------------------- > > Key: WFLY-9917 > URL: https://issues.jboss.org/browse/WFLY-9917 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 11.0.0.Final > Reporter: Hisanobu Okuda > Assignee: Darran Lofthouse > > It is convenient that a server certificate for https interface can be renewed without restarting a server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9939) Eliminate the need to override the org.jboss.as.clustering.jgroups module in our openshift images

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-9939: -------------------------------------- Summary: Eliminate the need to override the org.jboss.as.clustering.jgroups module in our openshift images Key: WFLY-9939 URL: https://issues.jboss.org/browse/WFLY-9939 Project: WildFly Issue Type: Enhancement Components: Clustering Reporter: Brian Stansberry Assignee: Paul Ferraro Our openshift images are overriding the org.jboss.as.clustering.jgroups module.xml in order to include a dependency on the org.openshift.ping module. This is fragile because any update to the overridden module.xml needs to be applied to the override file as well, and that can easily break. Let's make the need for this go away. Possibilities: 1) Add an optional dependency on module "org.openshift.ping" to the org.jboss.as.clustering.jgroups module. The openshift images then just add that module. In bare metal installations the module is not present. 2) Change the standalone-openshift.xml configs such that whatever is using this module declares a "module" attribute, removing the need for the module.xml dependency. (If this is the correct solution, please move this issue to the CLOUD JIRA project where we can use it to track removing the override.) 3) Ship whatever's needed from org.openshift.ping in WF itself, eliminating the need for that module. This may already be in progress as I've seen some relevant JIRAs. (If this is the correct solution, please move this issue to the CLOUD JIRA project where we can use it to track removing the override and the installation of the org.openshift.ping module.) [~luck3y] FYI. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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