[JBoss JIRA] (WFLY-6048) jboss-webservices.xml descriptor doesn't override @WebContext annotation
by Dmitrii Tikhomirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-6048?page=com.atlassian.jira.plugin.... ]
Dmitrii Tikhomirov updated WFLY-6048:
-------------------------------------
Git Pull Request: (was: https://github.com/apache/activemq-artemis/pull/376)
> jboss-webservices.xml descriptor doesn't override @WebContext annotation
> ------------------------------------------------------------------------
>
> Key: WFLY-6048
> URL: https://issues.jboss.org/browse/WFLY-6048
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 9.0.2.Final
> Environment: ubuntu 14.04, Java 7
> Reporter: Wojciech Oczkowski
> Assignee: Dmitrii Tikhomirov
> Priority: Minor
> Attachments: ws-xml-override.zip
>
>
> It seems that annotation WebConfig takes precedence over jboss-webservices.xml descriptor values. It doesn't seem right as you cannot override annotation values for test purposes for example.
> Problematic code seems to be:
> org.jboss.as.webservices.metadata.AbstractMetaDataBuilderEJB:159
> (should prefer JBossPortComponentMetaData over EJBEndpoint)
> and
> org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect:177
> (should prefer EJBSecurityMetaData over annotation value)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (DROOLS-1053) Change date formats for JSON representations used in the REST API
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1053?page=com.atlassian.jira.plugi... ]
Edson Tirelli reassigned DROOLS-1053:
-------------------------------------
Assignee: Maciej Swiderski (was: Edson Tirelli)
> Change date formats for JSON representations used in the REST API
> -----------------------------------------------------------------
>
> Key: DROOLS-1053
> URL: https://issues.jboss.org/browse/DROOLS-1053
> Project: Drools
> Issue Type: Feature Request
> Components: kie server
> Affects Versions: 6.3.0.Final
> Environment: jBPM 6.3 running on Wildfly 8.2
> Reporter: William Siqueira
> Assignee: Maciej Swiderski
>
> The format for dates are are using milliseconds form, for example:
> {code:javascript}
> {
> "request-instance-id" : 4,
> "request-status" : "QUEUED",
> "request-message" : "Ready to execute",
> "request-retries" : 3,
> "request-executions" : 0,
> "request-command" : "org.jbpm.executor.commands.PrintOutCommand",
> "request-scheduled-date" : 1455069600000
> }
> {code}
> The problem with this format is that it is not readable and might confuse users using other ways to communicate with the kie server than using its REST API.
> The suggested solution is use a Jackson object mapper to configure the desired date format. This is better explained in this article:
> http://wiki.fasterxml.com/JacksonFAQDateHandling
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6140) Error response handling from bean validation ignores Accept header
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-6140?page=com.atlassian.jira.plugin.... ]
Marek Kopecký closed WFLY-6140.
-------------------------------
Resolution: Duplicate Issue
> Error response handling from bean validation ignores Accept header
> ------------------------------------------------------------------
>
> Key: WFLY-6140
> URL: https://issues.jboss.org/browse/WFLY-6140
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 10.0.0.Final
> Environment: Mac OS X El Captain
> java version "1.8.0_66"
> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> Reporter: Marek Kopecký
> Assignee: Weinan Li
>
> Basically I have a very simple application that has request validation in the REST endpoints.
> According to the documentation of RESTEasy, I should get a JSON error response if I put "application/json" in Accept header in the request.
> https://docs.jboss.org/resteasy/docs/3.0.13.Final/userguide/html/Validati...
> The mentioned feature worked just fine in Wildfly 9.0.2.Final. Now, however, it doesn't.
> I have tried to upgrade the dependencies in the pom.xml to use dependencies from Wildfly 10.0.0.Final, but still no luck. Though the attached application deploys just fine in Wildfly 9.0.2.Final and Wildfly 10.0.0.Final.
> In WF 9.0.2.Final I used to get the below error *JSON*
> {code:json}
> {
> "exception": null,
> "fieldViolations": [],
> "propertyViolations": [],
> "classViolations": [],
> "parameterViolations": [{
> "constraintType": "PARAMETER",
> "path": "registerLogisticsNetwork.arg0.name",
> "message": "may not be null",
> "value": ""
> }],
> "returnValueViolations": []
> }
> {code}
> In WF 10.0.0.Final I get this:
> {code}
> [PARAMETER]
> [registerLogisticsNetwork.arg0.name]
> [may not be null]
> []
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6140) Error response handling from bean validation ignores Accept header
by Marek Kopecký (JIRA)
Marek Kopecký created WFLY-6140:
-----------------------------------
Summary: Error response handling from bean validation ignores Accept header
Key: WFLY-6140
URL: https://issues.jboss.org/browse/WFLY-6140
Project: WildFly
Issue Type: Bug
Components: REST
Affects Versions: 10.0.0.Final
Environment: Mac OS X El Captain
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
Reporter: Marek Kopecký
Assignee: Weinan Li
Basically I have a very simple application that has request validation in the REST endpoints.
According to the documentation of RESTEasy, I should get a JSON error response if I put "application/json" in Accept header in the request.
https://docs.jboss.org/resteasy/docs/3.0.13.Final/userguide/html/Validati...
The mentioned feature worked just fine in Wildfly 9.0.2.Final. Now, however, it doesn't.
I have tried to upgrade the dependencies in the pom.xml to use dependencies from Wildfly 10.0.0.Final, but still no luck. Though the attached application deploys just fine in Wildfly 9.0.2.Final and Wildfly 10.0.0.Final.
In WF 9.0.2.Final I used to get the below error *JSON*
{code:json}
{
"exception": null,
"fieldViolations": [],
"propertyViolations": [],
"classViolations": [],
"parameterViolations": [{
"constraintType": "PARAMETER",
"path": "registerLogisticsNetwork.arg0.name",
"message": "may not be null",
"value": ""
}],
"returnValueViolations": []
}
{code}
In WF 10.0.0.Final I get this:
{code}
[PARAMETER]
[registerLogisticsNetwork.arg0.name]
[may not be null]
[]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6097) Error response handling from bean validation ignores Accept header
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-6097?page=com.atlassian.jira.plugin.... ]
Marek Kopecký reassigned WFLY-6097:
-----------------------------------
Assignee: Weinan Li (was: Jason Greene)
> Error response handling from bean validation ignores Accept header
> ------------------------------------------------------------------
>
> Key: WFLY-6097
> URL: https://issues.jboss.org/browse/WFLY-6097
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 10.0.0.Final
> Environment: Mac OS X El Captain
> java version "1.8.0_66"
> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> Reporter: Renann Prado
> Assignee: Weinan Li
> Attachments: delivery-optimization-ear-1.0.Final.ear
>
>
> Basically I have a very simple application that has request validation in the REST endpoints.
> According to the documentation of RESTEasy, I should get a JSON error response if I put "application/json" in Accept header in the request.
> https://docs.jboss.org/resteasy/docs/3.0.13.Final/userguide/html/Validati...
> The mentioned feature worked just fine in Wildfly 9.0.2.Final. Now, however, it doesn't.
> I have tried to upgrade the dependencies in the pom.xml to use dependencies from Wildfly 10.0.0.Final, but still no luck. Though the attached application deploys just fine in Wildfly 9.0.2.Final and Wildfly 10.0.0.Final.
> In WF 9.0.2.Final I used to get the below error *JSON*
> {code:json}
> {
> "exception": null,
> "fieldViolations": [],
> "propertyViolations": [],
> "classViolations": [],
> "parameterViolations": [{
> "constraintType": "PARAMETER",
> "path": "registerLogisticsNetwork.arg0.name",
> "message": "may not be null",
> "value": ""
> }],
> "returnValueViolations": []
> }
> {code}
> In WF 10.0.0.Final I get this:
> {code}
> [PARAMETER]
> [registerLogisticsNetwork.arg0.name]
> [may not be null]
> []
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6097) Error response handling from bean validation ignores Accept header
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-6097?page=com.atlassian.jira.plugin.... ]
Marek Kopecký updated WFLY-6097:
--------------------------------
Component/s: REST
> Error response handling from bean validation ignores Accept header
> ------------------------------------------------------------------
>
> Key: WFLY-6097
> URL: https://issues.jboss.org/browse/WFLY-6097
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 10.0.0.Final
> Environment: Mac OS X El Captain
> java version "1.8.0_66"
> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> Reporter: Renann Prado
> Assignee: Jason Greene
> Attachments: delivery-optimization-ear-1.0.Final.ear
>
>
> Basically I have a very simple application that has request validation in the REST endpoints.
> According to the documentation of RESTEasy, I should get a JSON error response if I put "application/json" in Accept header in the request.
> https://docs.jboss.org/resteasy/docs/3.0.13.Final/userguide/html/Validati...
> The mentioned feature worked just fine in Wildfly 9.0.2.Final. Now, however, it doesn't.
> I have tried to upgrade the dependencies in the pom.xml to use dependencies from Wildfly 10.0.0.Final, but still no luck. Though the attached application deploys just fine in Wildfly 9.0.2.Final and Wildfly 10.0.0.Final.
> In WF 9.0.2.Final I used to get the below error *JSON*
> {code:json}
> {
> "exception": null,
> "fieldViolations": [],
> "propertyViolations": [],
> "classViolations": [],
> "parameterViolations": [{
> "constraintType": "PARAMETER",
> "path": "registerLogisticsNetwork.arg0.name",
> "message": "may not be null",
> "value": ""
> }],
> "returnValueViolations": []
> }
> {code}
> In WF 10.0.0.Final I get this:
> {code}
> [PARAMETER]
> [registerLogisticsNetwork.arg0.name]
> [may not be null]
> []
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6139) Starting server with EAP 6.4 standalone-full-ha.xml in --admin-only doesn't list "web" as legacy
by Ladislav Thon (JIRA)
[ https://issues.jboss.org/browse/WFLY-6139?page=com.atlassian.jira.plugin.... ]
Ladislav Thon updated WFLY-6139:
--------------------------------
Description:
{code}
unzip jboss-eap-6.4.0.zip
unzip wildfly-10.0.0.Final.zip
cp jboss-eap-6.4/standalone/configuration/standalone-full-ha.xml jboss-eap-7.0/standalone/configuration/
./wildfly-10.0.0.Final/bin/standalone.sh -c standalone-full-ha.xml --admin-only
{code}
During boot, the server lists {{threads}}, {{cmp}}, {{jaxr}}, {{messaging}} and {{jacorb}} as legacy:
{code}
11:26:55,792 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 5) WFLYCTL0402: Subsystems [jacorb] provided by legacy extension 'org.jboss.as.jacorb' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
11:26:55,795 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 8) WFLYCTL0402: Subsystems [cmp] provided by legacy extension 'org.jboss.as.cmp' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
11:26:55,793 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 12) WFLYCTL0402: Subsystems [threads] provided by legacy extension 'org.jboss.as.threads' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
11:26:55,800 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 18) WFLYCTL0402: Subsystems [messaging] provided by legacy extension 'org.jboss.as.messaging' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
11:26:55,800 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 9) WFLYCTL0402: Subsystems [jaxr] provided by legacy extension 'org.jboss.as.jaxr' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
{code}
However, {{web}} is missing. IMHO it should be there.
was:
{code}
unzip jboss-eap-6.4.0.zip
unzip jboss-eap-7.0.0.ER5.zip
cp jboss-eap-6.4/standalone/configuration/standalone-full-ha.xml jboss-eap-7.0/standalone/configuration/
./jboss-eap-7.0/bin/standalone.sh -c standalone-full-ha.xml --admin-only
{code}
During boot, the server lists {{threads}}, {{cmp}}, {{jaxr}}, {{messaging}} and {{jacorb}} as legacy:
{code}
11:26:55,792 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 5) WFLYCTL0402: Subsystems [jacorb] provided by legacy extension 'org.jboss.as.jacorb' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
11:26:55,795 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 8) WFLYCTL0402: Subsystems [cmp] provided by legacy extension 'org.jboss.as.cmp' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
11:26:55,793 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 12) WFLYCTL0402: Subsystems [threads] provided by legacy extension 'org.jboss.as.threads' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
11:26:55,800 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 18) WFLYCTL0402: Subsystems [messaging] provided by legacy extension 'org.jboss.as.messaging' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
11:26:55,800 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 9) WFLYCTL0402: Subsystems [jaxr] provided by legacy extension 'org.jboss.as.jaxr' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
{code}
However, {{web}} is missing. IMHO it should be there.
> Starting server with EAP 6.4 standalone-full-ha.xml in --admin-only doesn't list "web" as legacy
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-6139
> URL: https://issues.jboss.org/browse/WFLY-6139
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 10.0.0.Final
> Reporter: Ladislav Thon
> Assignee: Brian Stansberry
>
> {code}
> unzip jboss-eap-6.4.0.zip
> unzip wildfly-10.0.0.Final.zip
> cp jboss-eap-6.4/standalone/configuration/standalone-full-ha.xml jboss-eap-7.0/standalone/configuration/
> ./wildfly-10.0.0.Final/bin/standalone.sh -c standalone-full-ha.xml --admin-only
> {code}
> During boot, the server lists {{threads}}, {{cmp}}, {{jaxr}}, {{messaging}} and {{jacorb}} as legacy:
> {code}
> 11:26:55,792 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 5) WFLYCTL0402: Subsystems [jacorb] provided by legacy extension 'org.jboss.as.jacorb' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
> 11:26:55,795 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 8) WFLYCTL0402: Subsystems [cmp] provided by legacy extension 'org.jboss.as.cmp' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
> 11:26:55,793 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 12) WFLYCTL0402: Subsystems [threads] provided by legacy extension 'org.jboss.as.threads' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
> 11:26:55,800 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 18) WFLYCTL0402: Subsystems [messaging] provided by legacy extension 'org.jboss.as.messaging' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
> 11:26:55,800 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 9) WFLYCTL0402: Subsystems [jaxr] provided by legacy extension 'org.jboss.as.jaxr' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
> {code}
> However, {{web}} is missing. IMHO it should be there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6139) Starting server with EAP 6.4 standalone-full-ha.xml in --admin-only doesn't list "web" as legacy
by Ladislav Thon (JIRA)
Ladislav Thon created WFLY-6139:
-----------------------------------
Summary: Starting server with EAP 6.4 standalone-full-ha.xml in --admin-only doesn't list "web" as legacy
Key: WFLY-6139
URL: https://issues.jboss.org/browse/WFLY-6139
Project: WildFly
Issue Type: Bug
Components: Domain Management
Reporter: Ladislav Thon
Assignee: Brian Stansberry
{code}
unzip jboss-eap-6.4.0.zip
unzip jboss-eap-7.0.0.ER5.zip
cp jboss-eap-6.4/standalone/configuration/standalone-full-ha.xml jboss-eap-7.0/standalone/configuration/
./jboss-eap-7.0/bin/standalone.sh -c standalone-full-ha.xml --admin-only
{code}
During boot, the server lists {{threads}}, {{cmp}}, {{jaxr}}, {{messaging}} and {{jacorb}} as legacy:
{code}
11:26:55,792 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 5) WFLYCTL0402: Subsystems [jacorb] provided by legacy extension 'org.jboss.as.jacorb' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
11:26:55,795 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 8) WFLYCTL0402: Subsystems [cmp] provided by legacy extension 'org.jboss.as.cmp' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
11:26:55,793 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 12) WFLYCTL0402: Subsystems [threads] provided by legacy extension 'org.jboss.as.threads' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
11:26:55,800 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 18) WFLYCTL0402: Subsystems [messaging] provided by legacy extension 'org.jboss.as.messaging' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
11:26:55,800 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 9) WFLYCTL0402: Subsystems [jaxr] provided by legacy extension 'org.jboss.as.jaxr' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
{code}
However, {{web}} is missing. IMHO it should be there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6139) Starting server with EAP 6.4 standalone-full-ha.xml in --admin-only doesn't list "web" as legacy
by Ladislav Thon (JIRA)
[ https://issues.jboss.org/browse/WFLY-6139?page=com.atlassian.jira.plugin.... ]
Ladislav Thon updated WFLY-6139:
--------------------------------
Affects Version/s: 10.0.0.Final
> Starting server with EAP 6.4 standalone-full-ha.xml in --admin-only doesn't list "web" as legacy
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-6139
> URL: https://issues.jboss.org/browse/WFLY-6139
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 10.0.0.Final
> Reporter: Ladislav Thon
> Assignee: Brian Stansberry
>
> {code}
> unzip jboss-eap-6.4.0.zip
> unzip jboss-eap-7.0.0.ER5.zip
> cp jboss-eap-6.4/standalone/configuration/standalone-full-ha.xml jboss-eap-7.0/standalone/configuration/
> ./jboss-eap-7.0/bin/standalone.sh -c standalone-full-ha.xml --admin-only
> {code}
> During boot, the server lists {{threads}}, {{cmp}}, {{jaxr}}, {{messaging}} and {{jacorb}} as legacy:
> {code}
> 11:26:55,792 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 5) WFLYCTL0402: Subsystems [jacorb] provided by legacy extension 'org.jboss.as.jacorb' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
> 11:26:55,795 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 8) WFLYCTL0402: Subsystems [cmp] provided by legacy extension 'org.jboss.as.cmp' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
> 11:26:55,793 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 12) WFLYCTL0402: Subsystems [threads] provided by legacy extension 'org.jboss.as.threads' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
> 11:26:55,800 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 18) WFLYCTL0402: Subsystems [messaging] provided by legacy extension 'org.jboss.as.messaging' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
> 11:26:55,800 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 9) WFLYCTL0402: Subsystems [jaxr] provided by legacy extension 'org.jboss.as.jaxr' are not supported on servers running this version. Both the subsystem and the extension must be removed or migrated before the server will function.
> {code}
> However, {{web}} is missing. IMHO it should be there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months