June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12709) Add MP REST Client TCK to WildFly testsuite

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12709?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12709: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Add MP REST Client TCK to WildFly testsuite > ------------------------------------------- > > Key: WFLY-12709 > URL: https://issues.redhat.com/browse/WFLY-12709 > Project: WildFly > Issue Type: Task > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Labels: downstream_dependency > Fix For: 21.0.0.Beta1 > > > The MP REST Client TCK is currently part of the RESTEasy testsuite. It should be added to the WildFly testsuite too. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12881) Cannot customize split behavior and merge policy for Infinispan partition handling

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12881?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12881: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Cannot customize split behavior and merge policy for Infinispan partition handling > ---------------------------------------------------------------------------------- > > Key: WFLY-12881 > URL: https://issues.redhat.com/browse/WFLY-12881 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final, 19.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Critical > Fix For: 21.0.0.Beta1 > > > Currently, partition handling of an Infinispan cache is hard coded. When enabled, both reads and writes are denied on minority partitions (of a given segment) and, more critically, upon partition merge, no reconciliation of any data conflicts occurs. > Users need to be able to configure this, at least to support the built in read/write on split policy and the built-in merge policies. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8136) Allow JAX-RS annotations in CDI @Stereotype

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-8136?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-8136: ----------------------------------- Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Allow JAX-RS annotations in CDI @Stereotype > ------------------------------------------- > > Key: WFLY-8136 > URL: https://issues.redhat.com/browse/WFLY-8136 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld, REST > Affects Versions: 9.0.1.Final, 15.0.0.Final > Environment: Windows 7, JDK 1.8.0_60 > Reporter: Andreas Klemp > Assignee: Martin Stefanko > Priority: Major > Fix For: 21.0.0.Beta1 > > > A simple JAX-RS REST service can be annotated with @Produces to define the resulting mime-type. However, it is not working anymore, when the annotation is moved to a stereotype. The default application/octet-stream is used. > {code} > @Stereotype > @Produces(MediaType.APPLICATION_JSON) > @Target(ElementType.TYPE) > @Retention(RetentionPolicy.RUNTIME) > public @interface RestService { > } > @Path("/some") > @RestService > public class SomeRestService { > @GET > @Path("/") > public Response getSome() { > return Response.ok().entity("{\"x\" : 42, \"y\" : \"foo\"}").build(); > } > } > {code} > Using the following dependencies in Gradle project. > {noformat} > providedCompile( > [group: 'javax.enterprise', name: 'cdi-api', version: '1.2'], > [group: 'org.jboss.spec.javax.ws.rs', name: 'jboss-jaxrs-api_2.0_spec', version: '1.0.0.Final'], > [group: 'com.fasterxml.jackson.core', name: 'jackson-databind', version: '2.7.4'] > ) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13481) Upgrade wildfly-transaction-client to 1.1.12.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13481?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13481: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Upgrade wildfly-transaction-client to 1.1.12.Final > -------------------------------------------------- > > Key: WFLY-13481 > URL: https://issues.redhat.com/browse/WFLY-13481 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB, Transactions > Affects Versions: 19.1.0.Final > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Critical > Labels: downstream_dependency > Fix For: 21.0.0.Beta1 > > > Release diff: https://github.com/wildfly/wildfly-transaction-client/compare/1.1.11.Fina... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13319) Wildfly 19 MP-JWT & EJB Integration

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13319?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13319: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Wildfly 19 MP-JWT & EJB Integration > ----------------------------------- > > Key: WFLY-13319 > URL: https://issues.redhat.com/browse/WFLY-13319 > Project: WildFly > Issue Type: Enhancement > Components: EJB, MP JWT, Test Suite > Affects Versions: 19.0.0.Final > Reporter: Radu Cimpean > Assignee: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Beta1 > > Attachments: server-cli.txt, web.xml > > > ===Previous configuration & situation=== > As written https://groups.google.com/forum/#!topic/wildfly/L1BxATschCU, > We were running wildfly 18 and used jwt for securing the application. We did this via a series of cli commands (see server-cli.txt) to configure the server, as well as referencing the created domains in the web.xml. > Under jboss-web.xml we are referencing the "ejb-domain" created in the CLIs. The web.xml (see attachments) protects the resource wit the role referenced in the CLIs (role present in the token) > All our jax-rs resources are annotated with @Stateless and are calling EJBs which in turn are @Statless and declare allowed roles. > ===Current situation=== > We've upgraded to wildfly 19 in hopes of using microprofile jwt. To do this, we've annotated the Application class with > @LoginConfig(authMethod = "MP-JWT", realmName = "MP-JWT-REALM"), removed the login-config from the web.xml, and removed the security-domain from jboss-web.xml (since otherwise I would receive an error: ELY01148: A SecurityDomain has already been associated with the specified ClassLoader"). > After also removing the security-constraint tag from the web.xml I was able to get to the resource and noticed that the JWTToken was properly injected (all claims and entries are there), and the SecurityContext injected in the resource also contained the jwt specific values. From what I can tell, in the context of the jax-rs classloader, I am authenticated. > I would, however, always receive a "Invocation on method... is not allowed" the second the resource would try calling a bean, even if the role matched. Upon checking the logs, and what the injected SessionContext contained, I noticed the principal was anonymous and had no roles allowed. > I therefore believe that the credentials are somehow not being properly passed. > Is there a documented way of properly integrating jax-rs&ejb with microprofile jwt? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13150) Create a Galleon layer for distributable web

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13150?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13150: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Create a Galleon layer for distributable web > -------------------------------------------- > > Key: WFLY-13150 > URL: https://issues.redhat.com/browse/WFLY-13150 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Web (Undertow) > Reporter: Brian Stansberry > Assignee: Paul Ferraro > Priority: Major > Fix For: 21.0.0.Beta1 > > > We have a web-clustering layer that provides the distributable-web subsystem and the related infinispan web session caching resources, configured for multi-server distributed sessions. > We need a variant of this with infinispan configured for local caching. > The WFLY-13099 standalone-microprofile.xml config should have this kind of setup; otherwise session sharing does not work . (A failure in org.jboss.as.test.clustering.cluster.web.shared.SharedSessionTestCase if the server uses a config without it shows this.) For WFLY-13099 I can work around this by adding the needed config stuff without a layer, but as everything else needed for those configs are from layers, it's better to use a layer in WF 20. > Besides it's a good layer to have anyway. :) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6892) Access logging for EJBs

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-6892?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-6892: ----------------------------------- Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Access logging for EJBs > ----------------------- > > Key: WFLY-6892 > URL: https://issues.redhat.com/browse/WFLY-6892 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Assignee: Cheng Fang > Priority: Major > Labels: affects-model, affects_elytron > Fix For: 21.0.0.Beta1 > > > Access logging for EJB requests similar to Web access logging would be very useful. > Possibly something like: > {code} > [date-time] [host/IP of caller] [EJB Name] [EJB Method] [invocation id] Request Received ... > [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Starting Invocation ... > [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Finished Invocation ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13471) Fail the ws deployment packaged with JAXP implementation

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13471?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13471: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Fail the ws deployment packaged with JAXP implementation > -------------------------------------------------------- > > Key: WFLY-13471 > URL: https://issues.redhat.com/browse/WFLY-13471 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 19.1.0.Final > Reporter: Jim Ma > Assignee: Jim Ma > Priority: Major > Fix For: 21.0.0.Beta1 > > > Deploy JAXWS application that packages an older JAXP implementation. > Try to get the wsdl: wget http://localhost:8080/helloWorld?wsdl > When the container is performing operations, it should use the container's JAXP implementation, else it could fail if the application is packaging a version that is not compatible. > {code} > 19:28:42,560 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.3.0.GA (WildFly Core 10.1.2.Final-redhat-00001) started in 4091ms - Started 426 of 652 services (374 services are lazy, passive or on-demand) > 19:28:45,537 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /helloWorld: java.lang.AbstractMethodError: org.apache.xerces.dom.DeferredDocumentImpl.setXmlStandalone(Z)V > at org.apache.cxf.frontend.WSDLGetUtils.updateDoc(WSDLGetUtils.java:332) > at org.apache.cxf.frontend.WSDLGetUtils.writeWSDLDocument(WSDLGetUtils.java:708) > at org.apache.cxf.frontend.WSDLGetUtils.getDocument(WSDLGetUtils.java:151) > at org.apache.cxf.frontend.WSDLGetInterceptor.getDocument(WSDLGetInterceptor.java:129) > at org.apache.cxf.frontend.WSDLGetInterceptor.handleMessage(WSDLGetInterceptor.java:77) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) > at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267) > at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:110) > at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:134) > at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:88) > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:301) > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:225) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:503) > at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:136) > at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:590) > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13564) Clustering TS: Running a single test with -Dtest= can only be used with main tests

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-13564: ------------------------------------- Summary: Clustering TS: Running a single test with -Dtest= can only be used with main tests Key: WFLY-13564 URL: https://issues.redhat.com/browse/WFLY-13564 Project: WildFly Issue Type: Task Components: Clustering, Test Suite Affects Versions: 20.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 21.0.0.Beta1 Related to WFLY-13563. The -Dtest=foo will only run if the test foo is part of the main surefire execution. e.g. running a single node test will try to run that test in the main execution and would fail. Unfortunately, the -Dtest overrides includes/excludes fo the surefire plugin execution, which does not work for us well. Document how profile selection introduced in WFLY-13557 could be used to run single test. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13563) Clustering TS: All clustering tests need not run on full-ha server profile

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-13563: ------------------------------------- Summary: Clustering TS: All clustering tests need not run on full-ha server profile Key: WFLY-13563 URL: https://issues.redhat.com/browse/WFLY-13563 Project: WildFly Issue Type: Task Components: Clustering, Test Suite Affects Versions: 20.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 21.0.0.Beta1 In order to speed up the clustering testsuite by eliminating unnecessary application server starts and stops, the main surefire plugin execution has been combined into one. However, this required the full-ha profile which is necessary for only a couple of tests. The full-ha profile yields a lot of unnecessary warnings, starts unneeded services, so by splitting the tests into ha and full-ha profiles, these problems should go away. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 June 2020