[JBoss JIRA] (WFLY-10319) NameBinding annotations on resources are ignored in subresources
by Ron Sigal (Jira)
[ https://issues.jboss.org/browse/WFLY-10319?page=com.atlassian.jira.plugin... ]
Ron Sigal commented on WFLY-10319:
----------------------------------
I agree with Marek here. Everything in the spec tells me that resource methods and resource locators have an empty intersection.
I would add that the processing of resource locators leads, eventually, to the execution of exactly one resource method, and the presence of a name binding annotations on that resource method (or its class) determines the binding of interceptors and filters. So, "Annotating the sub-resource class or the method within works as expected" is what I would expect.
In effect, the direct execution of a resource method is a degenerate case of a sequence of zero resource locators leading to a resource method.
[~jestevezsanchez], I'm open to argument.
-Ron
> NameBinding annotations on resources are ignored in subresources
> ----------------------------------------------------------------
>
> Key: WFLY-10319
> URL: https://issues.jboss.org/browse/WFLY-10319
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 12.0.0.Final
> Reporter: Javier Estevez Sanchez
> Assignee: Alessio Soldano
> Priority: Major
>
> The following JAX-RS resource exposes two resources via a GET operation: /demo and /demo/subresource. The first one via a sub-resource method, the latter via a sub-resource locator. Additionally, a response filter is binded to the JAX-RS resource class to modify the response. From the JAX-RS 2.0 spec, §6.5.2 Name Binding:
> {quote}
> Binding annotations that decorate resource classes apply to all resource methods defined in them.
> {quote}
> However, the binding annotation is not applying to the sub-resource locator method. This happens when the name binding annotation is on the resource class or on the sub-resource locator method. Annotating the sub-resource class or the method within works as expected, though.
> Below is the code needed to reproduce this issue:
> {code:java|title=The resource and subresource}
> @DemoNameBinding
> @Produces(MediaType.APPLICATION_JSON)
> @Path("/demo")
> public class DemoResource {
> @GET
> public String getDemoValue() {
> return "A value";
> }
> @Path("/subresource")
> public DemoSubResource getSubResource() {
> return new DemoSubResource();
> }
> public class DemoSubResource {
> @GET
> public String getDemoValue() {
> return "A value";
> }
> }
> }
> {code}
> {code:java|title=The filter}
> @Provider
> @DemoNameBinding
> public class SomeFilter implements ContainerResponseFilter {
> @Override
> public void filter(ContainerRequestContext requestContext, ContainerResponseContext responseContext) {
> responseContext.setEntity("A filtered value");
> }
> }
> {code}
> {code:java|title=The binding}
> @NameBinding
> @Target({ElementType.TYPE, ElementType.METHOD})
> @Retention(RetentionPolicy.RUNTIME)
> public @interface DemoNameBinding {
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years
[JBoss JIRA] (AG-104) Pluggable security
by Luis Barreiro (Jira)
Luis Barreiro created AG-104:
--------------------------------
Summary: Pluggable security
Key: AG-104
URL: https://issues.jboss.org/browse/AG-104
Project: Agroal
Issue Type: Bug
Components: api, pool
Affects Versions: 1.3
Reporter: Luis Barreiro
Assignee: Luis Barreiro
Fix For: 1.4
Allow pluggable security providers, able to translate from principal/credentials into JDBC properties.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years
[JBoss JIRA] (DROOLS-3445) Data type constraints: Date
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3445?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3445:
--------------------------------
Attachment: (was: range.png)
> Data type constraints: Date
> ---------------------------
>
> Key: DROOLS-3445
> URL: https://issues.jboss.org/browse/DROOLS-3445
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration2.png, expression.png, range2.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 tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> 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
[JBoss JIRA] (DROOLS-3445) Data type constraints: Date
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3445?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3445:
--------------------------------
Attachment: (was: enumeration.png)
> Data type constraints: Date
> ---------------------------
>
> Key: DROOLS-3445
> URL: https://issues.jboss.org/browse/DROOLS-3445
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration2.png, expression.png, range2.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 tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> 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
[JBoss JIRA] (DROOLS-3445) Data type constraints: Date
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3445?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3445:
--------------------------------
Attachment: enumeration2.png
range2.png
> Data type constraints: Date
> ---------------------------
>
> Key: DROOLS-3445
> URL: https://issues.jboss.org/browse/DROOLS-3445
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration2.png, expression.png, range2.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 tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> 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
[JBoss JIRA] (DROOLS-3453) Data type constraints: Time
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3453?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3453:
--------------------------------
Attachment: (was: range3.png)
> Data type constraints: Time
> ---------------------------
>
> Key: DROOLS-3453
> URL: https://issues.jboss.org/browse/DROOLS-3453
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration2.png, range4.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 tab - as a user I want the ability to define constraints for the following types: Time (Expression, Enumeration, and Range.)
> 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
[JBoss JIRA] (DROOLS-3453) Data type constraints: Time
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3453?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3453:
--------------------------------
Attachment: range4.png
> Data type constraints: Time
> ---------------------------
>
> Key: DROOLS-3453
> URL: https://issues.jboss.org/browse/DROOLS-3453
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration2.png, range3.png, range4.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 tab - as a user I want the ability to define constraints for the following types: Time (Expression, Enumeration, and Range.)
> 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
[JBoss JIRA] (DROOLS-3458) Data type constraints: Text
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3458?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3458:
--------------------------------
Attachment: enumeration2.png
> Data type constraints: Text
> ---------------------------
>
> Key: DROOLS-3458
> URL: https://issues.jboss.org/browse/DROOLS-3458
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration2.png, expression.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 tab - as a user I want the ability to define constraints for the following types: Text (Expression and Enumeration.)
> 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
[JBoss JIRA] (DROOLS-3458) Data type constraints: Text
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3458?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3458:
--------------------------------
Attachment: (was: enumeration.png)
> Data type constraints: Text
> ---------------------------
>
> Key: DROOLS-3458
> URL: https://issues.jboss.org/browse/DROOLS-3458
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration2.png, expression.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 tab - as a user I want the ability to define constraints for the following types: Text (Expression and Enumeration.)
> 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