September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1779) Remove /deployment-overlay=*/content=*:read-content

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1779: ---------------------------------------- Summary: Remove /deployment-overlay=*/content=*:read-content Key: WFCORE-1779 URL: https://issues.jboss.org/browse/WFCORE-1779 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Follow-on to WFCORE-1778. Not to be scheduled for a release prior to the release that will be used in EAP 8. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1778) Deprecate /deployment-overlay=*/content=*:read-content, replace with a response stream variant

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1778?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1778: ------------------------------------- Description: The /deployment-overlay=*/content=*:read-content op is returning file content as a DMR ModelNode of type STRING. We need to deprecate and eventually drop this operation. Reading these files should use the response attachment mechanism. Probably we should add a 'stream' attribute to the resource as the replacement. Perhaps other attributes to mirror /subsystem=logging/log-file=*. was: The /deployment-overlay=*/content=*:read-content op is returning file content as a DMR ModelNode of type STRING. We need to deprecate and eventually drop this operation. Reading these files should use the response attachment mechanism. Probably we should add a 'stream' attribute to the resource as the replacement. > Deprecate /deployment-overlay=*/content=*:read-content, replace with a response stream variant > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-1778 > URL: https://issues.jboss.org/browse/WFCORE-1778 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 3.0.0.Beta1 > > > The /deployment-overlay=*/content=*:read-content op is returning file content as a DMR ModelNode of type STRING. We need to deprecate and eventually drop this operation. Reading these files should use the response attachment mechanism. > Probably we should add a 'stream' attribute to the resource as the replacement. Perhaps other attributes to mirror /subsystem=logging/log-file=*. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1778) Deprecate /deployment-overlay=*/content=*:read-content, replace with a response stream variant

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1778?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1778: ---------------------------------------- Assignee: ehsavoie Hugonnet > Deprecate /deployment-overlay=*/content=*:read-content, replace with a response stream variant > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-1778 > URL: https://issues.jboss.org/browse/WFCORE-1778 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 3.0.0.Beta1 > > > The /deployment-overlay=*/content=*:read-content op is returning file content as a DMR ModelNode of type STRING. We need to deprecate and eventually drop this operation. Reading these files should use the response attachment mechanism. > Probably we should add a 'stream' attribute to the resource as the replacement. Perhaps other attributes to mirror /subsystem=logging/log-file=*. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1778) Deprecate /deployment-overlay=*/content=*:read-content, replace with a response stream variant

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1778: ---------------------------------------- Summary: Deprecate /deployment-overlay=*/content=*:read-content, replace with a response stream variant Key: WFCORE-1778 URL: https://issues.jboss.org/browse/WFCORE-1778 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Fix For: 3.0.0.Beta1 The /deployment-overlay=*/content=*:read-content op is returning file content as a DMR ModelNode of type STRING. We need to deprecate and eventually drop this operation. Reading these files should use the response attachment mechanism. Probably we should add a 'stream' attribute to the resource as the replacement. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1777) Use separate resources for GET requests involving useStreamAsResponse

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1777: ---------------------------------------- Summary: Use separate resources for GET requests involving useStreamAsResponse Key: WFCORE-1777 URL: https://issues.jboss.org/browse/WFCORE-1777 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.0.0.CR1 A request for streamed content can potentially involve a large amount of content, e.g. a very large log file. We should limit the amount of resources (e.g. threads) available for handling such HTTP requests over the /management context, particularly in the case of GET requests where we don't do the cross-origin checks that we do with POST. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7087) Deprecate internal, timer and oob thread pools with JGroups 4.x upgrade

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7087?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-7087: --------------------------------- Issue Type: Task (was: Feature Request) > Deprecate internal, timer and oob thread pools with JGroups 4.x upgrade > ----------------------------------------------------------------------- > > Key: WFLY-7087 > URL: https://issues.jboss.org/browse/WFLY-7087 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Radoslav Husar > Assignee: Paul Ferraro > > http://belaban.blogspot.cz/2016/09/removing-thread-pools-in-jgroups-40.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1775) CLI command for enabling tracking configuration changes act differently when host is specifiend and when it is not

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1775?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFCORE-1775. -------------------------------------- Resolution: Rejected > CLI command for enabling tracking configuration changes act differently when host is specifiend and when it is not > ------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1775 > URL: https://issues.jboss.org/browse/WFCORE-1775 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Ivan Straka > Assignee: Brian Stansberry > > If I execute > {code} > /host=slave/core-service=management/service=configuration-changes:add(history-size=10) > {code} > on host controller, everything is fine. > But, if > {code} > /core-service=management/service=configuration-changes:add(history-size=10) > {code} > is executed, > {code:json} > { > "outcome" => "failed", > "failure-description" => "WFLYDC0032: Operation add for address [ > (\"core-service\" => \"management\"), > (\"service\" => \"configuration-changes\") > ] can only be handled by the master Domain Controller; this host is not the master Domain Controller", > "rolled-back" => true > } > {code} > is returned. > I have discussed this with [~ehugonnet], and it has not been decided whether this is correct behavior. For some reason it is trying to route the request to the DC. > This jira is supposed to start a discussion about this - is it a bug, or correct behavior? > IMHO results of these two commands should should be the same. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1775) CLI command for enabling tracking configuration changes act differently when host is specifiend and when it is not

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1775?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1775: ------------------------------------------ This is correct behavior. Connecting to a non-master HC and trying to invoke any write operation for a resource not in the /host=* tree should produce that error. Not producing that error is a bug. > CLI command for enabling tracking configuration changes act differently when host is specifiend and when it is not > ------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1775 > URL: https://issues.jboss.org/browse/WFCORE-1775 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Ivan Straka > Assignee: Brian Stansberry > > If I execute > {code} > /host=slave/core-service=management/service=configuration-changes:add(history-size=10) > {code} > on host controller, everything is fine. > But, if > {code} > /core-service=management/service=configuration-changes:add(history-size=10) > {code} > is executed, > {code:json} > { > "outcome" => "failed", > "failure-description" => "WFLYDC0032: Operation add for address [ > (\"core-service\" => \"management\"), > (\"service\" => \"configuration-changes\") > ] can only be handled by the master Domain Controller; this host is not the master Domain Controller", > "rolled-back" => true > } > {code} > is returned. > I have discussed this with [~ehugonnet], and it has not been decided whether this is correct behavior. For some reason it is trying to route the request to the DC. > This jira is supposed to start a discussion about this - is it a bug, or correct behavior? > IMHO results of these two commands should should be the same. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7087) Deprecate internal, timer and oob thread pools with JGroups 4.x upgrade

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-7087: ------------------------------------ Summary: Deprecate internal, timer and oob thread pools with JGroups 4.x upgrade Key: WFLY-7087 URL: https://issues.jboss.org/browse/WFLY-7087 Project: WildFly Issue Type: Feature Request Components: Clustering Reporter: Radoslav Husar Assignee: Paul Ferraro http://belaban.blogspot.cz/2016/09/removing-thread-pools-in-jgroups-40.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7085) Server should verify EJB business methods during deployment and reject

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-7085?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink updated WFLY-7085: ----------------------------------- Summary: Server should verify EJB business methods during deployment and reject (was: By spec EJB business methods should not final but the deployment did not fail under any circumstances) > Server should verify EJB business methods during deployment and reject > ---------------------------------------------------------------------- > > Key: WFLY-7085 > URL: https://issues.jboss.org/browse/WFLY-7085 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > > The ejb 3.2 core specification state in chapter 4.9.6 that business methods should not be declared as final or static. > But a Bean with a business method declared in the local or remote interface can be correct deployed and is accesible under some circumstances. > To ensure that the Bean is according to the spec and avoid runtime or injection issues the methods should be checked and a VerifyError should be thrown at deployment time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 September 2016