[JBoss JIRA] (WFLY-11809) RBAC: Deployment button not available for server group scoped role.
by Eugen Pribulla (Jira)
[ https://issues.jboss.org/browse/WFLY-11809?page=com.atlassian.jira.plugin... ]
Eugen Pribulla updated WFLY-11809:
----------------------------------
Steps to Reproduce:
* Install Wildfly 16.0.0.Final.
* Enable RBAC with admin as SuperUser.
* Create new server group scoped role *MainGroupDeployer* based on role *Deployer* scoped to *main-server-group*.
* Create new management user *test* and assign *MainGroupDeployer* to it.
* Login to HAL console as user *test*.
* Select from menu "Deployments" -> "Server Groups" -> "main-server-group"
* Deployment button on top of ServerGroupDeployment column should be visible but isn't.
was:
* Install Wildfly 16.0.0.Final.
* Enable RBAC with admin as SuperUser.
* Create new +Server Group Scoped Role+ +MainGroupDeployer+ based on role +Deployer+ scoped to +main-server-group+.
* Create new management user +test+ and assign +MainGroupDeployer+ to it.
* Login to HAL console as user *test*.
* Select from menu "Deployments" -> "Server Groups" -> "main-server-group"
* Deployment button on top of ServerGroupDeployment column should be visible but isn't.
> RBAC: Deployment button not available for server group scoped role.
> -------------------------------------------------------------------
>
> Key: WFLY-11809
> URL: https://issues.jboss.org/browse/WFLY-11809
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 16.0.0.Final
> Environment: Windows 10 x64
> Reporter: Eugen Pribulla
> Assignee: Harald Pehl
> Priority: Major
>
> RBAC security enabled.
> If you create a new server group scoped role (Deployer as base) then deployment buttons in the ServerGroupDeploymentColumn are hidden for that role.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (WFLY-11809) RBAC: Deployment button not available for server group scoped role.
by Eugen Pribulla (Jira)
Eugen Pribulla created WFLY-11809:
-------------------------------------
Summary: RBAC: Deployment button not available for server group scoped role.
Key: WFLY-11809
URL: https://issues.jboss.org/browse/WFLY-11809
Project: WildFly
Issue Type: Bug
Components: Web Console
Affects Versions: 16.0.0.Final
Environment: Windows 10 x64
Reporter: Eugen Pribulla
Assignee: Harald Pehl
RBAC security enabled.
If you create a new server group scoped role (Deployer as base) then deployment buttons in the ServerGroupDeploymentColumn are hidden for that role.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (WFLY-4621) RESTEasy SMIME doesn't work with WildFly current module setup
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-4621?page=com.atlassian.jira.plugin.... ]
Marek Kopecký updated WFLY-4621:
--------------------------------
Description:
RESTEasy provides the functions of SMIME encryption and here is an example that can be deployed into WildFly:
https://github.com/liweinan/digital-signatures/tree/master/smime
And currently resteasy-crypto module doesn't work properly in WildFly unless applied the following patch:
{code:diff}
power:modules weinanli$ git diff
warning: LF will be replaced by CRLF in system/layers/base/org/bouncycastle/main/module.xml.
The file will have its original line endings in your working directory.
diff --git a/system/layers/base/org/bouncycastle/main/module.xml b/system/layers/base/org/bouncycastle/main/module.xml
index 5d13395..83ae97c 100644
--- a/system/layers/base/org/bouncycastle/main/module.xml
+++ b/system/layers/base/org/bouncycastle/main/module.xml
@@ -24,12 +24,17 @@
<module xmlns="urn:jboss:module:1.3" name="org.bouncycastle">
<resources>
+ <!--
<resource-root path="bcprov-jdk15on-1.52.jar"/>
<resource-root path="bcmail-jdk15on-1.52.jar"/>
+ -->
+ <resource-root path="bcprov-jdk16-1.46.jar"/>
+ <resource-root path="bcmail-jdk16-1.46.jar"/>
<resource-root path="bcpkix-jdk15on-1.52.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
+ <module name="javax.mail.api"/>
+ <module name="javax.activation.api"/>
</dependencies>
-
</module>
{code}
After applying the above patch then the example can pass all the tests:
{code}
power:smime weinanli$ mvn -q clean package
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
power:smime weinanli$ mvn -q wildfly:deploy
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
May 11, 2015 9:24:27 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.0.Final
May 11, 2015 9:24:27 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.0.Final
May 11, 2015 9:24:27 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 4.0.7.Final
power:smime weinanli$ mvn -q integration-test
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.resteasy.tests.smime.SMIMETest
Encrypted Message From Server:
Customer{name='Bill'}
Signed Message From Server:
Customer{name='Bill'}
Customer{name='Bill'}
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.682 sec - in org.jboss.resteasy.tests.smime.SMIMETest
Results :
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
power:smime weinanli$
{code}
was:
RESTEasy provides the functions of SMIME encryption and here is an example that can be deployed into WildFly:
https://github.com/liweinan/digital-signatures/tree/master/smime
And currently resteasy-crypto module doesn't work properly in WildFly unless applied the following patch:
{code}
power:modules weinanli$ git diff
warning: LF will be replaced by CRLF in system/layers/base/org/bouncycastle/main/module.xml.
The file will have its original line endings in your working directory.
diff --git a/system/layers/base/org/bouncycastle/main/module.xml b/system/layers/base/org/bouncycastle/main/module.xml
index 5d13395..83ae97c 100644
--- a/system/layers/base/org/bouncycastle/main/module.xml
+++ b/system/layers/base/org/bouncycastle/main/module.xml
@@ -24,12 +24,17 @@
<module xmlns="urn:jboss:module:1.3" name="org.bouncycastle">
<resources>
+ <!--
<resource-root path="bcprov-jdk15on-1.52.jar"/>
<resource-root path="bcmail-jdk15on-1.52.jar"/>
+ -->
+ <resource-root path="bcprov-jdk16-1.46.jar"/>
+ <resource-root path="bcmail-jdk16-1.46.jar"/>
<resource-root path="bcpkix-jdk15on-1.52.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
+ <module name="javax.mail.api"/>
+ <module name="javax.activation.api"/>
</dependencies>
-
</module>
{code}
After applying the above patch then the example can pass all the tests:
{code}
power:smime weinanli$ mvn -q clean package
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
power:smime weinanli$ mvn -q wildfly:deploy
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
May 11, 2015 9:24:27 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.0.Final
May 11, 2015 9:24:27 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.0.Final
May 11, 2015 9:24:27 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 4.0.7.Final
power:smime weinanli$ mvn -q integration-test
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.resteasy.tests.smime.SMIMETest
Encrypted Message From Server:
Customer{name='Bill'}
Signed Message From Server:
Customer{name='Bill'}
Customer{name='Bill'}
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.682 sec - in org.jboss.resteasy.tests.smime.SMIMETest
Results :
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
power:smime weinanli$
{code}
> RESTEasy SMIME doesn't work with WildFly current module setup
> -------------------------------------------------------------
>
> Key: WFLY-4621
> URL: https://issues.jboss.org/browse/WFLY-4621
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 9.0.0.CR1
> Reporter: Weinan Li
> Assignee: Weinan Li
> Priority: Major
> Attachments: patch_WFLY-4621_all, patch_WFLY-4621_new
>
>
> RESTEasy provides the functions of SMIME encryption and here is an example that can be deployed into WildFly:
> https://github.com/liweinan/digital-signatures/tree/master/smime
> And currently resteasy-crypto module doesn't work properly in WildFly unless applied the following patch:
> {code:diff}
> power:modules weinanli$ git diff
> warning: LF will be replaced by CRLF in system/layers/base/org/bouncycastle/main/module.xml.
> The file will have its original line endings in your working directory.
> diff --git a/system/layers/base/org/bouncycastle/main/module.xml b/system/layers/base/org/bouncycastle/main/module.xml
> index 5d13395..83ae97c 100644
> --- a/system/layers/base/org/bouncycastle/main/module.xml
> +++ b/system/layers/base/org/bouncycastle/main/module.xml
> @@ -24,12 +24,17 @@
> <module xmlns="urn:jboss:module:1.3" name="org.bouncycastle">
> <resources>
> + <!--
> <resource-root path="bcprov-jdk15on-1.52.jar"/>
> <resource-root path="bcmail-jdk15on-1.52.jar"/>
> + -->
> + <resource-root path="bcprov-jdk16-1.46.jar"/>
> + <resource-root path="bcmail-jdk16-1.46.jar"/>
> <resource-root path="bcpkix-jdk15on-1.52.jar"/>
> </resources>
> <dependencies>
> <module name="javax.api"/>
> + <module name="javax.mail.api"/>
> + <module name="javax.activation.api"/>
> </dependencies>
> -
> </module>
> {code}
> After applying the above patch then the example can pass all the tests:
> {code}
> power:smime weinanli$ mvn -q clean package
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
> power:smime weinanli$ mvn -q wildfly:deploy
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
> May 11, 2015 9:24:27 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.3.0.Final
> May 11, 2015 9:24:27 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.3.0.Final
> May 11, 2015 9:24:27 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 4.0.7.Final
> power:smime weinanli$ mvn -q integration-test
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.resteasy.tests.smime.SMIMETest
> Encrypted Message From Server:
> Customer{name='Bill'}
> Signed Message From Server:
> Customer{name='Bill'}
> Customer{name='Bill'}
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.682 sec - in org.jboss.resteasy.tests.smime.SMIMETest
> Results :
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
> power:smime weinanli$
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (WFLY-1049) Add equivalent @WebContext for JAX-RS?
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-1049?page=com.atlassian.jira.plugin.... ]
Marek Kopecký updated WFLY-1049:
--------------------------------
Description:
Currently, in our application we use @WebContext to set a different contextRoot for JAX-WS. For example:
{code:java}
@Stateless
@SecurityDomain("test2")
@WebService(name = "HelloSoap", portName = "HelloSoapPort", serviceName = "HelloSoap", targetNamespace = "http://com.test")
@WebContext(contextRoot = "/ws", urlPattern = "/HelloSoap", secureWSDLAccess = false, authMethod = "BASIC", transportGuarantee = "NONE")
public class HelloSoap { ... }
{code}
We would like to have an equivalent annotation for JAX-RS? It is required whenever a web app uses FORM_AUTH and there exists web services (JAX-WS and JAX-RS), inside of the same package, using as BASIC_AUTH.
Thankyou in advance,
Fernando Rubbo
was:
Currently, in our application we use @WebContext to set a different contextRoot for JAX-WS. For example:
@Stateless
@SecurityDomain("test2")
@WebService(name = "HelloSoap", portName = "HelloSoapPort", serviceName = "HelloSoap", targetNamespace = "http://com.test")
@WebContext(contextRoot = "/ws", urlPattern = "/HelloSoap", secureWSDLAccess = false, authMethod = "BASIC", transportGuarantee = "NONE")
public class HelloSoap { ... }
We would like to have an equivalent annotation for JAX-RS? It is required whenever a web app uses FORM_AUTH and there exists web services (JAX-WS and JAX-RS), inside of the same package, using as BASIC_AUTH.
Thankyou in advance,
Fernando Rubbo
> Add equivalent @WebContext for JAX-RS?
> --------------------------------------
>
> Key: WFLY-1049
> URL: https://issues.jboss.org/browse/WFLY-1049
> Project: WildFly
> Issue Type: Feature Request
> Components: REST
> Reporter: Fernando Rubbo
> Priority: Major
> Labels: BASIC_AUTH, FORM_AUTH, JAX-RS,
>
> Currently, in our application we use @WebContext to set a different contextRoot for JAX-WS. For example:
>
> {code:java}
> @Stateless
> @SecurityDomain("test2")
> @WebService(name = "HelloSoap", portName = "HelloSoapPort", serviceName = "HelloSoap", targetNamespace = "http://com.test")
> @WebContext(contextRoot = "/ws", urlPattern = "/HelloSoap", secureWSDLAccess = false, authMethod = "BASIC", transportGuarantee = "NONE")
> public class HelloSoap { ... }
> {code}
> We would like to have an equivalent annotation for JAX-RS? It is required whenever a web app uses FORM_AUTH and there exists web services (JAX-WS and JAX-RS), inside of the same package, using as BASIC_AUTH.
>
> Thankyou in advance,
> Fernando Rubbo
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[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ý commented on WFLY-2752:
-------------------------------------
[~ron_sigal]: Looking to the description of this jira. V1_TCPController class from the reproducer is not listed in the description, but I believe V1_TCPController class is not necessary and this end-point should reproduce the issue if valid:
{code:java}
@Path("/v1")
@ApplicationScoped
public class V1_TCPControllerResource {
@Context
UriInfo uriInfo;
@PUT
@Path("{id}")
@Produces("application/json")
public Response addController(@PathParam("id") String id) {
URI uri = uriInfo.getAbsolutePathBuilder().path(id).build();
return Response.created(uri).build();
}
}
{code}
* curl -v -X PUT http://localhost:8080/jaxrs-wf/v1/aaa
Anyway, location is created correctly, so it seems that this issue is no longer valid. Can you please close this issue as out-of-date? [~stanzelivinski] can reopen this issue with a reproducer, if [~stanzelivinski] still see this issue ...
{noformat}
[mkopecky@dhcp-10-40-5-71 bin]$ curl -v -X PUT http://localhost:8080/jaxrs-wf/v1/aaa
...
> PUT /jaxrs-wf/v1/aaa HTTP/1.1
...
< HTTP/1.1 201 Created
< Connection: keep-alive
< Location: http://localhost:8080/jaxrs-wf/v1/aaa/aaa
...
[mkopecky@dhcp-10-40-5-71 bin]$
{noformat}
> 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
> Reporter: Stan Zelivinski
> Assignee: Ron Sigal
> 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, 9 months
[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ý edited comment on WFLY-2752 at 3/5/19 2:15 AM:
-------------------------------------------------------------
[~ron_sigal]: Looking to the description of this jira. V1_TCPController class from the reproducer is not listed in the description, but I believe V1_TCPController class is not necessary and this end-point should reproduce the issue if valid:
{code:java}
@Path("/v1")
@ApplicationScoped
public class V1_TCPControllerResource {
@Context
UriInfo uriInfo;
@PUT
@Path("{id}")
@Produces("application/json")
public Response addController(@PathParam("id") String id) {
URI uri = uriInfo.getAbsolutePathBuilder().path(id).build();
return Response.created(uri).build();
}
}
{code}
* curl -v -X PUT http://localhost:8080/jaxrs-wf/v1/aaa
Anyway, location is created correctly in WF16, so it seems that this issue is no longer valid. Can you please close this issue as out-of-date? [~stanzelivinski] can reopen this issue with a reproducer, if [~stanzelivinski] still see this issue ...
{noformat}
[mkopecky@dhcp-10-40-5-71 bin]$ curl -v -X PUT http://localhost:8080/jaxrs-wf/v1/aaa
...
> PUT /jaxrs-wf/v1/aaa HTTP/1.1
...
< HTTP/1.1 201 Created
< Connection: keep-alive
< Location: http://localhost:8080/jaxrs-wf/v1/aaa/aaa
...
[mkopecky@dhcp-10-40-5-71 bin]$
{noformat}
was (Author: mkopecky):
[~ron_sigal]: Looking to the description of this jira. V1_TCPController class from the reproducer is not listed in the description, but I believe V1_TCPController class is not necessary and this end-point should reproduce the issue if valid:
{code:java}
@Path("/v1")
@ApplicationScoped
public class V1_TCPControllerResource {
@Context
UriInfo uriInfo;
@PUT
@Path("{id}")
@Produces("application/json")
public Response addController(@PathParam("id") String id) {
URI uri = uriInfo.getAbsolutePathBuilder().path(id).build();
return Response.created(uri).build();
}
}
{code}
* curl -v -X PUT http://localhost:8080/jaxrs-wf/v1/aaa
Anyway, location is created correctly, so it seems that this issue is no longer valid. Can you please close this issue as out-of-date? [~stanzelivinski] can reopen this issue with a reproducer, if [~stanzelivinski] still see this issue ...
{noformat}
[mkopecky@dhcp-10-40-5-71 bin]$ curl -v -X PUT http://localhost:8080/jaxrs-wf/v1/aaa
...
> PUT /jaxrs-wf/v1/aaa HTTP/1.1
...
< HTTP/1.1 201 Created
< Connection: keep-alive
< Location: http://localhost:8080/jaxrs-wf/v1/aaa/aaa
...
[mkopecky@dhcp-10-40-5-71 bin]$
{noformat}
> 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
> Reporter: Stan Zelivinski
> Assignee: Ron Sigal
> 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, 9 months
[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ý reassigned WFLY-2752:
-----------------------------------
Assignee: Ron Sigal (was: Bill Burke)
> 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
> Reporter: Stan Zelivinski
> Assignee: Ron Sigal
> 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, 9 months
[JBoss JIRA] (WFLY-2859) Treating all JAX-RS components as CDI Beans has some negative consequences
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ]
Marek Kopecký edited comment on WFLY-2859 at 3/5/19 2:05 AM:
-------------------------------------------------------------
This issue is still valid in WF16, see the details in RESTEASY-1015
was (Author: mkopecky):
This issue is still valid in WF16.
> Treating all JAX-RS components as CDI Beans has some negative consequences
> --------------------------------------------------------------------------
>
> Key: WFLY-2859
> URL: https://issues.jboss.org/browse/WFLY-2859
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, REST
> Affects Versions: 8.0.0.CR1, 16.0.0.Beta1
> Reporter: Matt Drees
> Assignee: Stuart Douglas
> Priority: Major
>
> It seems that wildfly is now treating all jax-rs Providers and Resources as CDI Beans. This is probably fine most of the time, but there are some Provider classes that cause UnproxyableResolutionException (WELD-001437) errors, due to the fact that resteasy-cdi attempts to get bean reference whose type is identical to the bean class.
> See the forum link for a specific instance of this.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months