March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2752) Using an injected UriInfo object by the JAX-RS runtime environment does not work

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-2752?page=com.atlassian.jira.plugin.... ] Marek Kopecký updated WFLY-2752: -------------------------------- Description: The code that works perfectly in WildFly.8.0.0.Beta: {code:java} package jdsu.vts.tcpcontroller.webservices.rest.resources; import java.net.URI; import javax.ws.rs.DELETE; import javax.ws.rs.GET; import javax.ws.rs.PUT; import javax.ws.rs.Path; import javax.ws.rs.PathParam; import javax.ws.rs.Produces; import javax.ws.rs.Consumes; import javax.ws.rs.core.Context; import javax.ws.rs.core.Response; import javax.ws.rs.core.UriInfo; import jdsu.vts.tcpcontroller.webservices.rest.application.V1_TCPController; import jdsu.vts.shared.transferobjects.V1_TCPSetups; @Path("/v1") public class V1_TCPControllerResource { @Context UriInfo uriInfo; @GET @Produces("application/json") public Response getControllers() { //String json = String.valueOf(m_testsMap.size()); return Response.ok(V1_TCPController.getCollection()).build(); } @PUT @Path("{id}") @Produces("application/json") public Response addController(@PathParam("id") String id) { V1_TCPController controller = V1_TCPController.find(id); if(controller != null) { return Response.status(Response.Status.CONFLICT).build(); } controller = new V1_TCPController(id); URI uri = uriInfo.getAbsolutePathBuilder().path(id).build(); return Response.created(uri).build(); } } {code} does not work in WildFly.8.0.0.CR1. uriInfo is null in the call. Please help. Stan was: The code that works perfectly in WildFly.8.0.0.Beta: {code:java} package jdsu.vts.tcpcontroller.webservices.rest.resources; import java.net.URI; import javax.ws.rs.DELETE; import javax.ws.rs.GET; import javax.ws.rs.PUT; import javax.ws.rs.Path; import javax.ws.rs.PathParam; import javax.ws.rs.Produces; import javax.ws.rs.Consumes; import javax.ws.rs.core.Context; import javax.ws.rs.core.Response; import javax.ws.rs.core.UriInfo; import jdsu.vts.tcpcontroller.webservices.rest.application.V1_TCPController; import jdsu.vts.shared.transferobjects.V1_TCPSetups; @Path("/v1") public class V1_TCPControllerResource { @Context UriInfo uriInfo; @GET @Produces("application/json") public Response getControllers() { //String json = String.valueOf(m_testsMap.size()); return Response.ok(V1_TCPController.getCollection()).build(); } @PUT @Path("{id}") @Produces("application/json") public Response addController(@PathParam("id") String id) { V1_TCPController controller = V1_TCPController.find(id); if(controller != null) { return Response.status(Response.Status.CONFLICT).build(); } controller = new V1_TCPController(id); URI uri = uriInfo.getAbsolutePathBuilder().path(id).build(); return Response.created(uri).build(); } } {code:java} does not work in WildFly.8.0.0.CR1. uriInfo is null in the call. Please help. Stan > Using an injected UriInfo object by the JAX-RS runtime environment does not work > -------------------------------------------------------------------------------- > > Key: WFLY-2752 > URL: https://issues.jboss.org/browse/WFLY-2752 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 8.0.0.CR1 > Environment: Linux Fedora > Reporter: Stan Zelivinski > Assignee: Bill Burke > Priority: Major > > The code that works perfectly in WildFly.8.0.0.Beta: > {code:java} > package jdsu.vts.tcpcontroller.webservices.rest.resources; > import java.net.URI; > import javax.ws.rs.DELETE; > import javax.ws.rs.GET; > import javax.ws.rs.PUT; > import javax.ws.rs.Path; > import javax.ws.rs.PathParam; > import javax.ws.rs.Produces; > import javax.ws.rs.Consumes; > import javax.ws.rs.core.Context; > import javax.ws.rs.core.Response; > import javax.ws.rs.core.UriInfo; > import jdsu.vts.tcpcontroller.webservices.rest.application.V1_TCPController; > import jdsu.vts.shared.transferobjects.V1_TCPSetups; > @Path("/v1") > public class V1_TCPControllerResource { > @Context UriInfo uriInfo; > > @GET > @Produces("application/json") > public Response getControllers() { > //String json = String.valueOf(m_testsMap.size()); > return Response.ok(V1_TCPController.getCollection()).build(); > } > > @PUT > @Path("{id}") > @Produces("application/json") > public Response addController(@PathParam("id") String id) { > V1_TCPController controller = V1_TCPController.find(id); > if(controller != null) { > return Response.status(Response.Status.CONFLICT).build(); > } > controller = new V1_TCPController(id); > URI uri = uriInfo.getAbsolutePathBuilder().path(id).build(); > return Response.created(uri).build(); > } > } > {code} > does not work in WildFly.8.0.0.CR1. uriInfo is null in the call. > Please help. > Stan -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-624) Cleanup https://hub.docker.com/r/kialiqe/kiali/tags

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-624?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-624. ---------------------------------- Resolution: Done > Cleanup https://hub.docker.com/r/kialiqe/kiali/tags > --------------------------------------------------- > > Key: SWSQE-624 > URL: https://issues.jboss.org/browse/SWSQE-624 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11808) Unable to do jndi lookup when starting batch job from web console

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-11808?page=com.atlassian.jira.plugin... ] Cheng Fang updated WFLY-11808: ------------------------------ Description: when starting a batch job from web console, jndi lookup inside the application's batch artifacts failed with NameNotFoundException. When the same job is started by the application, the lookups all go well. Need to check if the naming context is properly propagated when starting job from the web console. (was: when starting a batch job from web console, jndi lookup inside the application's batch artifacts failed with NameNotFoundException. When the same job is started by the application, the lookups all go well.) > Unable to do jndi lookup when starting batch job from web console > ----------------------------------------------------------------- > > Key: WFLY-11808 > URL: https://issues.jboss.org/browse/WFLY-11808 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 16.0.0.Final > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > Attachments: Screen Shot 2019-03-04 at 10.38.47 PM.png > > > when starting a batch job from web console, jndi lookup inside the application's batch artifacts failed with NameNotFoundException. When the same job is started by the application, the lookups all go well. Need to check if the naming context is properly propagated when starting job from the web console. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11808) Unable to do jndi lookup when starting batch job from web console

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-11808?page=com.atlassian.jira.plugin... ] Cheng Fang updated WFLY-11808: ------------------------------ Attachment: Screen Shot 2019-03-04 at 10.38.47 PM.png > Unable to do jndi lookup when starting batch job from web console > ----------------------------------------------------------------- > > Key: WFLY-11808 > URL: https://issues.jboss.org/browse/WFLY-11808 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 16.0.0.Final > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > Attachments: Screen Shot 2019-03-04 at 10.38.47 PM.png > > > when starting a batch job from web console, jndi lookup inside the application's batch artifacts failed with NameNotFoundException. When the same job is started by the application, the lookups all go well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11808) Unable to do jndi lookup when starting batch job from web console

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-11808?page=com.atlassian.jira.plugin... ] Cheng Fang updated WFLY-11808: ------------------------------ Description: when starting a batch job from web console, jndi lookup inside the application's batch artifacts failed with NameNotFoundException. When the same job is started by the application, the lookups all go well. > Unable to do jndi lookup when starting batch job from web console > ----------------------------------------------------------------- > > Key: WFLY-11808 > URL: https://issues.jboss.org/browse/WFLY-11808 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 16.0.0.Final > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > > when starting a batch job from web console, jndi lookup inside the application's batch artifacts failed with NameNotFoundException. When the same job is started by the application, the lookups all go well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11808) Unable to do jndi lookup when starting batch job from web console

by Cheng Fang (Jira)

Cheng Fang created WFLY-11808: --------------------------------- Summary: Unable to do jndi lookup when starting batch job from web console Key: WFLY-11808 URL: https://issues.jboss.org/browse/WFLY-11808 Project: WildFly Issue Type: Bug Components: Batch Affects Versions: 16.0.0.Final Reporter: Cheng Fang Assignee: Cheng Fang -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11807) Better port configuration for JGroups FD_SOCK

by Rich DiCroce (Jira)

Rich DiCroce created WFLY-11807: ----------------------------------- Summary: Better port configuration for JGroups FD_SOCK Key: WFLY-11807 URL: https://issues.jboss.org/browse/WFLY-11807 Project: WildFly Issue Type: Enhancement Components: Clustering Affects Versions: 14.0.0.Final Reporter: Rich DiCroce Assignee: Paul Ferraro The JGroups FD_SOCK protocol requires 2 TCP sockets. Older versions of WildFly accepted a socket-binding for this protocol, but that was removed around version 11, apparently because the binding's port number [wasn't actually used|https://access.redhat.com/solutions/3485801]. Now the port selection is random by default, which is a problem if you've got firewalls to deal with, as noted in the linked document. The suggested workaround is to set the client_bind_port and start_port properties of the protocol, but that has the drawback of not being affected by a socket-binding-group's port-offset. This means that if you want to run 2 WildFly instances on the same box with the same config (which I do, as a developer, to test application code related to clustering), simply changing the port offset is insufficient to get the second instance to start. So I'd like to suggest that socket-binding for FD_SOCK be resurrected, given that it can be implemented correctly now. FD_SOCK calls the configured SocketFactory for both the server socket (with name jgroups.fd_sock.srv_sock) and the client socket (with name jgroups.fd.ping_sock), so it should be possible for WildFly to fully manage the socket bindings. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3077) Enhance data type restrictions UX - Decision Table/properties

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3077: ------------------------------------- [~tirelli] [~manstis] Here's a comprehensive click-thru, in case you want to check this change out in relationship to some of the other changes: https://redhat.invisionapp.com/share/DEQTMGIXU3Y The input flow starts around slide 11, and the changes to the property panel due to the addition of Documentation starts at screen 46. Thanks. > Enhance data type restrictions UX - Decision Table/properties > ------------------------------------------------------------- > > Key: DROOLS-3077 > URL: https://issues.jboss.org/browse/DROOLS-3077 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3077) Enhance data type restrictions UX - Decision Table/properties

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3077: ------------------------------------- [~manstis] I updated the demo above, based on discussion/decisions - only changes were: * If the user select a data type that already has constraints they can add Input constraints two ways: - inline in the input field as an expression. - (CHANGE) also allow the user to employ the (+) Add icon to launch the dialog to add input constraints. * If the user adds input constraints to a type that already has input constraints - the new constraints will over-write the existing ones (only for Input constraints, not data types.) Didn't ask [~tirelli] whether we need to replicate all of this in the property panel; it's still an Open Issue. > Enhance data type restrictions UX - Decision Table/properties > ------------------------------------------------------------- > > Key: DROOLS-3077 > URL: https://issues.jboss.org/browse/DROOLS-3077 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3077) Enhance data type restrictions UX - Decision Table/properties

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ] Liz Clayton edited comment on DROOLS-3077 at 3/4/19 5:14 PM: ------------------------------------------------------------- [~manstis] I updated the demo above, based on discussion/decisions - only changes were: * If the user select a data type that already has constraints they can add Input constraints two ways: A. inline in the input field as an expression. B. (CHANGE) also allow the user to employ the (+) Add icon to launch the dialog to add input constraints. * If the user adds input constraints to a type that already has input constraints - the new constraints will over-write the existing ones (only for Input constraints, not data types.) Didn't ask [~tirelli] whether we need to replicate all of this in the property panel; it's still an Open Issue. was (Author: uxdlc): [~manstis] I updated the demo above, based on discussion/decisions - only changes were: * If the user select a data type that already has constraints they can add Input constraints two ways: - inline in the input field as an expression. - (CHANGE) also allow the user to employ the (+) Add icon to launch the dialog to add input constraints. * If the user adds input constraints to a type that already has input constraints - the new constraints will over-write the existing ones (only for Input constraints, not data types.) Didn't ask [~tirelli] whether we need to replicate all of this in the property panel; it's still an Open Issue. > Enhance data type restrictions UX - Decision Table/properties > ------------------------------------------------------------- > > Key: DROOLS-3077 > URL: https://issues.jboss.org/browse/DROOLS-3077 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019