August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2830) kie-maven-plugin can't resolve custom operators declared in project's kmodule.xml

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2830?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-2830: ----------------------------------- Assignee: Luca Molteni (was: Mario Fusco) > kie-maven-plugin can't resolve custom operators declared in project's kmodule.xml > --------------------------------------------------------------------------------- > > Key: DROOLS-2830 > URL: https://issues.jboss.org/browse/DROOLS-2830 > Project: Drools > Issue Type: Bug > Affects Versions: 7.9.0.Final > Reporter: Esteban Aliverti > Assignee: Luca Molteni > Attachments: sample2.zip > > > The kie-maven-plugin fails to build a KieBase when it uses a custom operator defined in the projects' kmodule.xml. > As far as I can tell, it seems like the kie-maven-plugin is not even using the project's kmodule.xml but it is using a predefined one. > The same project works when using Drools 6.5. > I'm attaching a simple project showing this problem. The project won't build when using version 7.9 but it will work fine then using version 6.5. Just unzip the .zip file and run _mvn clean package_ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3997) Add HostExcludeResourceDefinition.KnownRelease items for EAP 7.2

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3997?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-3997: ------------------------------- Labels: blocker-WF15 (was: ) > Add HostExcludeResourceDefinition.KnownRelease items for EAP 7.2 > ---------------------------------------------------------------- > > Key: WFCORE-3997 > URL: https://issues.jboss.org/browse/WFCORE-3997 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Martin Simka > Priority: Blocker > Labels: blocker-WF15 > Fix For: 7.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3997) Add HostExcludeResourceDefinition.KnownRelease items for EAP 7.2

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3997?page=com.atlassian.jira.plugi... ] Kabir Khan commented on WFCORE-3997: ------------------------------------ [~jmesnil] I am bumping this up to blocker so that it gets done early in WF15 > Add HostExcludeResourceDefinition.KnownRelease items for EAP 7.2 > ---------------------------------------------------------------- > > Key: WFCORE-3997 > URL: https://issues.jboss.org/browse/WFCORE-3997 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Martin Simka > Priority: Blocker > Labels: blocker-WF15 > Fix For: 7.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10806) Add mixed domain tests for EAP 7.2.0

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10806?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-10806: ------------------------------ Priority: Blocker (was: Major) > Add mixed domain tests for EAP 7.2.0 > ------------------------------------ > > Key: WFLY-10806 > URL: https://issues.jboss.org/browse/WFLY-10806 > Project: WildFly > Issue Type: Task > Components: Management, Test Suite > Reporter: Martin Simka > Priority: Blocker > Labels: blocker-WF15 > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10806) Add mixed domain tests for EAP 7.2.0

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10806?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-10806: ------------------------------ Labels: blocker-WF15 (was: ) > Add mixed domain tests for EAP 7.2.0 > ------------------------------------ > > Key: WFLY-10806 > URL: https://issues.jboss.org/browse/WFLY-10806 > Project: WildFly > Issue Type: Task > Components: Management, Test Suite > Reporter: Martin Simka > Priority: Blocker > Labels: blocker-WF15 > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3997) Add HostExcludeResourceDefinition.KnownRelease items for EAP 7.2

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3997?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-3997: ------------------------------- Priority: Blocker (was: Major) > Add HostExcludeResourceDefinition.KnownRelease items for EAP 7.2 > ---------------------------------------------------------------- > > Key: WFCORE-3997 > URL: https://issues.jboss.org/browse/WFCORE-3997 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Martin Simka > Priority: Blocker > Fix For: 7.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3999) Allow registering a custom HTTP handler for management interface

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3999?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFCORE-3999: ------------------------------------- [~bstansberry] fiy, this RFE solves issues encountered when providing the HTTP endpoint for the microprofile health check, including: * undesired redirection (/health/ -> /healht/index.html) * undesired cache info * hack to represent the HTTP endpoint as a static resource > Allow registering a custom HTTP handler for management interface > ---------------------------------------------------------------- > > Key: WFCORE-3999 > URL: https://issues.jboss.org/browse/WFCORE-3999 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > With WFCORE-1742, it is possible to add "resources" to the HTTP management interface through the ExtensibleHttpManagement interface. > However this requires to provide a io.undertow.server.handlers.resource.ResourceManager object that represents the resource. This interface is meant to represent static resources (such as file) and does not map well to exposing a "REST" kind of API. > It does not allow to distinguish between HTTP verbs (GET, POST, DELETE) or inspect HTTP header. > It requires to provide cache metadata (etag, cache) that may not be relevant for a HTTP API. > It also automatically enables redirection (e.g. / to /index.html) without possibility to disable it. > For some HTTP API such as the one required by MicroProfile Health Check (a GET on /management/health), it would be better to be able to pass a io.undertow.server.HttpHandler instead of a io.undertow.server.handlers.resource.ResourceManager to have more flexibility/simplicity to provide management HTTP API. > One of the concern when WFCORE-1742 was created was that this API exposes Undertow API. This is already the case with ResourceManager and this RFE would add another such exposition to io.undertow.server.HttpHandler. > Proposed API: > in org.jboss.as.server.mgmt.domain.ExtensibleHttpManagement > {code} > /** > * Add a context for a HTTP management handler. > * @param contextName the name of the context. Cannot be {@code null} or empty > * @param managementHandler HTTP management handler. Cannot be {@code null} > * > * @throws IllegalArgumentException if either parameter is invalid > * @throws IllegalStateException if there is already a context present named the same as {@code contextName}, either > * added via this interface or otherwise > */ > void addManagementHandler(String contextName, HttpHandler managementHandler); > {code} > (this is in addition to the existing addStaticContext(String contextName, ResourceManager resourceManager)). > There is no need to add a corresponding remove method as the existing one removeContext(String contextName) can be used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3999) Allow registering a custom HTTP handler for management interface

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3999?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3999: -------------------------------- Description: With WFCORE-1742, it is possible to add "resources" to the HTTP management interface through the ExtensibleHttpManagement interface. However this requires to provide a io.undertow.server.handlers.resource.ResourceManager object that represents the resource. This interface is meant to represent static resources (such as file) and does not map well to exposing a "REST" kind of API. It does not allow to distinguish between HTTP verbs (GET, POST, DELETE) or inspect HTTP header. It requires to provide cache metadata (etag, cache) that may not be relevant for a HTTP API. It also automatically enables redirection (e.g. / to /index.html) without possibility to disable it. For some HTTP API such as the one required by MicroProfile Health Check (a GET on /management/health), it would be better to be able to pass a io.undertow.server.HttpHandler instead of a io.undertow.server.handlers.resource.ResourceManager to have more flexibility/simplicity to provide management HTTP API. One of the concern when WFCORE-1742 was created was that this API exposes Undertow API. This is already the case with ResourceManager and this RFE would add another such exposition to io.undertow.server.HttpHandler. Proposed API: in org.jboss.as.server.mgmt.domain.ExtensibleHttpManagement {code} /** * Add a context for a HTTP management handler. * @param contextName the name of the context. Cannot be {@code null} or empty * @param managementHandler HTTP management handler. Cannot be {@code null} * * @throws IllegalArgumentException if either parameter is invalid * @throws IllegalStateException if there is already a context present named the same as {@code contextName}, either * added via this interface or otherwise */ void addManagementHandler(String contextName, HttpHandler managementHandler); {code} (this is in addition to the existing addStaticContext(String contextName, ResourceManager resourceManager)). There is no need to add a corresponding remove method as the existing one removeContext(String contextName) can be used. was:With > Allow registering a custom HTTP handler for management interface > ---------------------------------------------------------------- > > Key: WFCORE-3999 > URL: https://issues.jboss.org/browse/WFCORE-3999 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > With WFCORE-1742, it is possible to add "resources" to the HTTP management interface through the ExtensibleHttpManagement interface. > However this requires to provide a io.undertow.server.handlers.resource.ResourceManager object that represents the resource. This interface is meant to represent static resources (such as file) and does not map well to exposing a "REST" kind of API. > It does not allow to distinguish between HTTP verbs (GET, POST, DELETE) or inspect HTTP header. > It requires to provide cache metadata (etag, cache) that may not be relevant for a HTTP API. > It also automatically enables redirection (e.g. / to /index.html) without possibility to disable it. > For some HTTP API such as the one required by MicroProfile Health Check (a GET on /management/health), it would be better to be able to pass a io.undertow.server.HttpHandler instead of a io.undertow.server.handlers.resource.ResourceManager to have more flexibility/simplicity to provide management HTTP API. > One of the concern when WFCORE-1742 was created was that this API exposes Undertow API. This is already the case with ResourceManager and this RFE would add another such exposition to io.undertow.server.HttpHandler. > Proposed API: > in org.jboss.as.server.mgmt.domain.ExtensibleHttpManagement > {code} > /** > * Add a context for a HTTP management handler. > * @param contextName the name of the context. Cannot be {@code null} or empty > * @param managementHandler HTTP management handler. Cannot be {@code null} > * > * @throws IllegalArgumentException if either parameter is invalid > * @throws IllegalStateException if there is already a context present named the same as {@code contextName}, either > * added via this interface or otherwise > */ > void addManagementHandler(String contextName, HttpHandler managementHandler); > {code} > (this is in addition to the existing addStaticContext(String contextName, ResourceManager resourceManager)). > There is no need to add a corresponding remove method as the existing one removeContext(String contextName) can be used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10752) NPE on deploy, when Email validation annotation present

by d3coder d3coder (JIRA)

[ https://issues.jboss.org/browse/WFLY-10752?page=com.atlassian.jira.plugin... ] d3coder d3coder updated WFLY-10752: ----------------------------------- Attachment: bvbug-1.0-SNAPSHOT.war > NPE on deploy, when Email validation annotation present > ------------------------------------------------------- > > Key: WFLY-10752 > URL: https://issues.jboss.org/browse/WFLY-10752 > Project: WildFly > Issue Type: Bug > Components: Bean Validation > Affects Versions: 13.0.0.Final > Environment: Arch linux, openjdk 8, Wildfly 13.0.0.Final > Reporter: d3coder d3coder > Assignee: Jason Greene > Attachments: bvbug-1.0-SNAPSHOT.war, bvbug-1.0-SNAPSHOT.war, bvbug-1.0-SNAPSHOT.war, bvbug.zip > > > I'm making simple app. In one of my DTO's i have field with `javax.validation.constraints.Email` annotation. When this annotation present, wildfly fails to deploy my app with this exception: > https://gist.github.com/XakepSDK/daa2531203b365ad1969e01b4466b8a1 > My DTO class: > https://gist.github.com/XakepSDK/a78245b262315437d2800be524018d2e > CrossField annotation: > https://gist.github.com/XakepSDK/fde1553339c18bc442820868f573a53a > CrossField validator: > https://gist.github.com/XakepSDK/391783e3b79f839a93a8f45c886b38e0 > java -version > openjdk version "1.8.0_172" > OpenJDK Runtime Environment (build 1.8.0_172-b11) > OpenJDK 64-Bit Server VM (build 25.172-b11, mixed mode) > <------------------ UPD: ------------------> > I got it, this happens if @Size present with @Email. > Simple test class: > https://gist.github.com/XakepSDK/892ec3d886ec2cac7f44d93faa0868c1 > UPD: this happens if field annotated with Email and any other validation annotation. > It failed with Email and NotNull. > UPD: Maven project and WAR with [^bvbug-1.0-SNAPSHOT.war] minimal repro. code > Actually, this project doesn't show issue like my first app, but Email validation doesn't work too. > Make a POST request to `/` with this: > `{"email":"test"}` or {"email":"test(a)test.test"}` > `Content-Type: application/json` > You will get `NullPointerException` in response, without any extended message.(i made special mapper for that, but seems it doesn't work with that exception) > In another project, wilfdly refuses to start with NullPointerException, here it work only for request. I don't know, how to make it work like in another project. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10752) NPE on deploy, when Email validation annotation present

by d3coder d3coder (JIRA)

[ https://issues.jboss.org/browse/WFLY-10752?page=com.atlassian.jira.plugin... ] d3coder d3coder commented on WFLY-10752: ---------------------------------------- Forgot about it, check it now. Should be uploaded. > NPE on deploy, when Email validation annotation present > ------------------------------------------------------- > > Key: WFLY-10752 > URL: https://issues.jboss.org/browse/WFLY-10752 > Project: WildFly > Issue Type: Bug > Components: Bean Validation > Affects Versions: 13.0.0.Final > Environment: Arch linux, openjdk 8, Wildfly 13.0.0.Final > Reporter: d3coder d3coder > Assignee: Jason Greene > Attachments: bvbug-1.0-SNAPSHOT.war, bvbug-1.0-SNAPSHOT.war, bvbug-1.0-SNAPSHOT.war, bvbug.zip > > > I'm making simple app. In one of my DTO's i have field with `javax.validation.constraints.Email` annotation. When this annotation present, wildfly fails to deploy my app with this exception: > https://gist.github.com/XakepSDK/daa2531203b365ad1969e01b4466b8a1 > My DTO class: > https://gist.github.com/XakepSDK/a78245b262315437d2800be524018d2e > CrossField annotation: > https://gist.github.com/XakepSDK/fde1553339c18bc442820868f573a53a > CrossField validator: > https://gist.github.com/XakepSDK/391783e3b79f839a93a8f45c886b38e0 > java -version > openjdk version "1.8.0_172" > OpenJDK Runtime Environment (build 1.8.0_172-b11) > OpenJDK 64-Bit Server VM (build 25.172-b11, mixed mode) > <------------------ UPD: ------------------> > I got it, this happens if @Size present with @Email. > Simple test class: > https://gist.github.com/XakepSDK/892ec3d886ec2cac7f44d93faa0868c1 > UPD: this happens if field annotated with Email and any other validation annotation. > It failed with Email and NotNull. > UPD: Maven project and WAR with [^bvbug-1.0-SNAPSHOT.war] minimal repro. code > Actually, this project doesn't show issue like my first app, but Email validation doesn't work too. > Make a POST request to `/` with this: > `{"email":"test"}` or {"email":"test(a)test.test"}` > `Content-Type: application/json` > You will get `NullPointerException` in response, without any extended message.(i made special mapper for that, but seems it doesn't work with that exception) > In another project, wilfdly refuses to start with NullPointerException, here it work only for request. I don't know, how to make it work like in another project. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018