September 2019 - jboss-jira - Jboss List Archives

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

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-8136?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-8136: -------------------------------- Fix Version/s: 18.0.0.Final (was: 18.0.0.Beta1) > Allow JAX-RS annotations in CDI @Stereotype > ------------------------------------------- > > Key: WFLY-8136 > URL: https://issues.jboss.org/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: 18.0.0.Final > > > 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.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11935) Remove unused commons-cli, commons-lang and commons-lang3 modules

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11935?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11935: --------------------------------- Fix Version/s: 18.0.0.Final (was: 18.0.0.Beta1) > Remove unused commons-cli, commons-lang and commons-lang3 modules > ----------------------------------------------------------------- > > Key: WFLY-11935 > URL: https://issues.jboss.org/browse/WFLY-11935 > Project: WildFly > Issue Type: Task > Components: JSF, Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 18.0.0.Final > > > Currently WildFly includes 3 JBoss Modules modules that are not used in our runtime. I would like to remove these in WildFly 17: > org.apache.commons.cli > org.apache.commons.lang[1] > org.apache.commons.lang3 > All three have the "jboss.api" = "private" property set in their module.xml, meaning they are marked for internal use only and we are free to remove them. End user applications should not have referenced these modules, and if they do we log a WARN on boot advising not to do that. > However, other projects that extend WildFly (i.e. write their own subsystems) may be using these modules, so I sent out a notification that these may be going away: > http://lists.jboss.org/pipermail/wildfly-dev/2019-April/006829.html -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11904) No ActiveMQ connection factory with RAR deployment

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11904?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11904: --------------------------------- Fix Version/s: 18.0.0.Final (was: 18.0.0.Beta1) > No ActiveMQ connection factory with RAR deployment > -------------------------------------------------- > > Key: WFLY-11904 > URL: https://issues.jboss.org/browse/WFLY-11904 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Thomas Diesler > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 18.0.0.Final > > > The ActiveMQ RAR deployment no longer registers its connection factory nor destination. > Is org.apache.activemq:activemq-rar:rar:5.15.7 no longer supported? > CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/2783 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11873) JGroups subsystem pbcast.GMS/view attribute only shows the viewId

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11873?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11873: --------------------------------- Fix Version/s: 18.0.0.Final (was: 18.0.0.Beta1) > JGroups subsystem pbcast.GMS/view attribute only shows the viewId > ----------------------------------------------------------------- > > Key: WFLY-11873 > URL: https://issues.jboss.org/browse/WFLY-11873 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 16.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 18.0.0.Final > > > {code} > [standalone@127.0.0.1:10190 /] /subsystem=jgroups/channel=ee/protocol=pbcast.GMS:read-resource(include-runtime=true > { > "outcome" => "success", > "result" => { > "after_creation_hook" => undefined, > "coord" => false, > "ergonomics" => true, > "flush_invoker_class" => undefined, > "id" => 12, > "implementation" => "ParticipantGmsImpl", > "install_view_locally_first" => true, > "is_leaving" => false, > "join_timeout" => 3000L, > "leave_timeout" => 3000L, > "level" => undefined, > "local_address" => "node3", > "log_collect_msgs" => false, > "log_view_warnings" => true, > "max_bundling_time" => 50L, > "max_join_attempts" => 10L, > "members" => "(2) node2,node3", > "merge_id" => undefined, > "merge_in_progress" => false, > "merge_killer_running" => false, > "merge_task_running" => false, > "merge_timeout" => 5000L, > "num_members" => 2, > "num_prev_mbrs" => 50, > "num_prev_views" => 10, > "number_of_views" => 0, > "print_local_addr" => false, > "print_physical_addrs" => true, > "stats" => false, > "use_delta_views" => true, > "use_flush_if_present" => true, > "view" => "[node2|1]", > "view_ack_collection_timeout" => 2000L, > "view_bundling" => true, > "view_handler_size" => 0, > "view_handler_suspended" => false > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11783) Rewrite some WildFly EE services to don't use deprecated MSC API

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11783?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11783: --------------------------------- Fix Version/s: 18.0.0.Final (was: 18.0.0.Beta1) > Rewrite some WildFly EE services to don't use deprecated MSC API > ---------------------------------------------------------------- > > Key: WFLY-11783 > URL: https://issues.jboss.org/browse/WFLY-11783 > Project: WildFly > Issue Type: Enhancement > Components: EE > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 18.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11697) WS integration with WildFly Elytron - AuthenticationClient for Authentication / SSL

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11697?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11697: --------------------------------- Fix Version/s: 18.0.0.Final (was: 18.0.0.Beta1) > WS integration with WildFly Elytron - AuthenticationClient for Authentication / SSL > ----------------------------------------------------------------------------------- > > Key: WFLY-11697 > URL: https://issues.jboss.org/browse/WFLY-11697 > Project: WildFly > Issue Type: Feature Request > Components: Security, Web Services > Affects Versions: 16.0.0.Final > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > Fix For: 18.0.0.Final > > > This feature request is about making use of authentication configuration on the client side of the WS deployment. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11538) Opentracing - SmallRye - IllegalStateException

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11538?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11538: --------------------------------- Fix Version/s: 18.0.0.Final (was: 18.0.0.Beta1) > Opentracing - SmallRye - IllegalStateException > ---------------------------------------------- > > Key: WFLY-11538 > URL: https://issues.jboss.org/browse/WFLY-11538 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 15.0.0.Final > Reporter: Alessandro Moscatelli > Assignee: Jeff Mesnil > Priority: Major > Fix For: 18.0.0.Final > > > Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-000713: Unable to inject ServletContext. None is associated with ModuleClassLoader for Module > The problem is the interaction between these two: > https://github.com/wildfly/wildfly/blob/master/microprofile/opentracing-s... > https://github.com/smallrye/smallrye-opentracing/blob/1.1.1/implementatio... > Those are delivered with Wildfly 15 out of the box in: > smallrye-opentracing-1.1.1.jar > wildfly-microprofile-opentracing-smallrye-15.0.0.Final.jar > I have an EAR with a EJB jar, WAR and a common JAR library. > To reproduce the issue I created a Stateless EJB in the EJB jar and then I injected a Traced ApplicationScoped bean from the JAR library in the Stateless EJB. > SmallRyeTracingCDIInterceptor triggers and it requires an Injected Tracer. > TracerProducer triggers and it has no active ServletContext and this leads to the error above. > My suggestion: > I don't think the ServletContext is a really good place to store the Tracer. > I think that the Tracer created by Wildfly should be registered into the GlobalTracer. > This should be done by: > https://github.com/wildfly/wildfly/blob/master/microprofile/opentracing-s... > If you don't want Wildfly to register automatically its Tracer in the GlobalTracer, this behavior could be disabled in the subsystem. > Also please be aware that SmallRyeTracingCDIInterceptor is dismissed in the last versions of the library and SmallRye states (https://github.com/smallrye/smallrye-opentracing) it has been replaced with: > https://github.com/opentracing-contrib/java-interceptors/blob/master/src/... > Also be aware that what I am suggesting is similar to the same behavior adopted in opentracing java-cdi (not yet integrated in Wildfly): > https://github.com/opentracing-contrib/java-cdi/blob/master/opentracing-c... > https://github.com/opentracing-contrib/java-cdi/blob/master/opentracing-c... > Also notice that opentracing java-ejb (not yet integrated in Wildfly) also requires a registration in GlobalTracing: > https://github.com/opentracing-contrib/java-ejb/blob/master/opentracing-e... > Thank you for your support. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11492) Quickstart http-custom-mechanism: documentation step fails

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11492?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11492: --------------------------------- Fix Version/s: 18.0.0.Final (was: 18.0.0.Beta1) > Quickstart http-custom-mechanism: documentation step fails > ---------------------------------------------------------- > > Key: WFLY-11492 > URL: https://issues.jboss.org/browse/WFLY-11492 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Alan Hantke > Assignee: Darran Lofthouse > Priority: Major > Fix For: 18.0.0.Final > > > Step #3, entitled *Configure the Application Security Domain* has the developer executing the following CLI command: > {code:java} > $ {jbossHomeName}/bin/jboss-cli.sh --connect --file=configure-security-domain.cli > {code} > However, this results in the following error: > {code:java} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): > WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: > Step: step-1 > Operation: /subsystem=undertow/application-security-domain=other:add(http-authentication-factory=application-http-authentication) > Failure: WFLYCTL0369: Required capabilities are not available: > org.wildfly.security.http-authentication-factory.application-http-authentication; Possible registration points for this capability: > /subsystem=elytron/http-authentication-factory=* > {code} > I am by no means an expert on this, but in looking at the standalone.xml file, I think that there needs to be a mate for the inserted *application-http-authentication*. I have attempted to continue without this changes installed by the CLI, but I am unable to execute the webapp even after providing the correct user/pass in the BASIC AUTH. > I have verified that the same problem-causing syntax exists on the quickstart 'master', although I have been using branch '14.x' because neither 15.x nor 'master' would build when I execute 'mvn clean build'. Finally, the I encounter the problem with fresh installs of WildFly versions 10.1.0 and 14.0. > Please change change the project if I have categorized the ticket incorrectly. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12353) Enable SSL tests on JDK14+

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12353?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12353: --------------------------------- Fix Version/s: 18.0.0.Final (was: 18.0.0.Beta1) > Enable SSL tests on JDK14+ > -------------------------- > > Key: WFLY-12353 > URL: https://issues.jboss.org/browse/WFLY-12353 > Project: WildFly > Issue Type: Enhancement > Components: Security > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 18.0.0.Final > > > WFLY-12219 disabled the tests, this is a reminder to enable them again (although also mentioned in WFCORE-4532) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12322) Avoid redispatching to a worker the ejb call if it is not async (at AssociationImpl)

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12322?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12322: --------------------------------- Fix Version/s: 18.0.0.Final (was: 18.0.0.Beta1) > Avoid redispatching to a worker the ejb call if it is not async (at AssociationImpl) > ------------------------------------------------------------------------------------ > > Key: WFLY-12322 > URL: https://issues.jboss.org/browse/WFLY-12322 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Reporter: Flavia Rainone > Assignee: Stuart Douglas > Priority: Major > Fix For: 18.0.0.Final > > > Prevent the extra cost of dispatching the message at AssociationImpl.execute if the message is synchronous, by just executing it right away -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 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 September 2019