August 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7006) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.ejb3.jsr77

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7006?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-7006: ----------------------------------- Component/s: EE (was: EJB) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.ejb3.jsr77 > --------------------------------------------------------------------------------------------------- > > Key: WFLY-7006 > URL: https://issues.jboss.org/browse/WFLY-7006 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: Brian Stansberry > Assignee: Paul Ferraro > > $subject says it all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7006) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.ejb3.jsr77

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7006?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-7006: -------------------------------------- Assignee: Brian Stansberry (was: Paul Ferraro) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.ejb3.jsr77 > --------------------------------------------------------------------------------------------------- > > Key: WFLY-7006 > URL: https://issues.jboss.org/browse/WFLY-7006 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > $subject says it all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7006) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.ejb3.jsr77

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-7006: -------------------------------------- Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.ejb3.jsr77 Key: WFLY-7006 URL: https://issues.jboss.org/browse/WFLY-7006 Project: WildFly Issue Type: Bug Components: EJB Reporter: Brian Stansberry Assignee: Paul Ferraro $subject says it all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7005) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.ejb3.clustered.singleton

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7005?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-7005: -------------------------------------- Component/s: EJB (was: Batch) Assignee: Paul Ferraro (was: James Perkins) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.ejb3.clustered.singleton > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7005 > URL: https://issues.jboss.org/browse/WFLY-7005 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Brian Stansberry > Assignee: Paul Ferraro > > $subject says it all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7005) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.ejb3.clustered.singleton

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-7005: -------------------------------------- Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.ejb3.clustered.singleton Key: WFLY-7005 URL: https://issues.jboss.org/browse/WFLY-7005 Project: WildFly Issue Type: Bug Components: Batch Reporter: Brian Stansberry Assignee: James Perkins $subject says it all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7004) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.batch.configuration

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-7004: -------------------------------------- Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.batch.configuration Key: WFLY-7004 URL: https://issues.jboss.org/browse/WFLY-7004 Project: WildFly Issue Type: Bug Components: Batch Reporter: Brian Stansberry Assignee: James Perkins $subject says it all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1733) SynchServerOperationHandler doesn't check ops for REQUIRE_RESTART properly

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1733?page=com.atlassian.jira.plugi... ] Ken Wills commented on WFCORE-1733: ----------------------------------- Ah, good to know, thanks. I've added that one. > SynchServerOperationHandler doesn't check ops for REQUIRE_RESTART properly > -------------------------------------------------------------------------- > > Key: WFCORE-1733 > URL: https://issues.jboss.org/browse/WFCORE-1733 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 3.0.0.Alpha6 > > > Currently, SyncServerStateOperationHandler makes a simple check to determine if the result of an op should put a server into restart-required. This should be fixed to check the AttributeDefinition for the target of a write-attribute for restart-required, and the OperationDefinition of all other ops. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1733) SynchServerOperationHandler doesn't check ops for REQUIRE_RESTART properly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1733?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1733: ------------------------------------------ Treat "undefine-attribute" the same as "write-attribute". We had some bug this year in this general area of logic where the op generation was generating "undefine-attribute" instead of "write-attribute" and the bug was that op didn't get handled properly. It may be possible to limit added checks to addresses in the profile=* tree. That may not be worth it though. > SynchServerOperationHandler doesn't check ops for REQUIRE_RESTART properly > -------------------------------------------------------------------------- > > Key: WFCORE-1733 > URL: https://issues.jboss.org/browse/WFCORE-1733 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 3.0.0.Alpha6 > > > Currently, SyncServerStateOperationHandler makes a simple check to determine if the result of an op should put a server into restart-required. This should be fixed to check the AttributeDefinition for the target of a write-attribute for restart-required, and the OperationDefinition of all other ops. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-181) Review JACC in Servlet and EJB subsystems

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-181?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-181: --------------------------------- Fix Version/s: 1.1.0.Beta9 (was: 1.1.0.Beta8) > Review JACC in Servlet and EJB subsystems > ----------------------------------------- > > Key: ELY-181 > URL: https://issues.jboss.org/browse/ELY-181 > Project: WildFly Elytron > Issue Type: Sub-task > Components: API / SPI > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta9 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1726) CLI support for response attachments

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1726?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-1726: ---------------------------------------------- Ok, on this basis, I can continue my POC :). Thanks! > CLI support for response attachments > ------------------------------------ > > Key: WFCORE-1726 > URL: https://issues.jboss.org/browse/WFCORE-1726 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > CLI doesn't support the streams attached to a response. Incremental deployment support offers today the ability to read the content of a deployment. It would be interesting to operate it from the CLI. Some resource (such as the log file) expose some attributes as stream. > The following operations are returning streams: > /subsystem=logging/log-file=server.log:read-attribute(name=stream) > /subsystem=logging/log-file=server.log:read-resource(include-runtime) > /deployment=toto:read-content(path=index.html) > As we can see, streams can be located in attributes, as operation response, inside a resource. > The CLI offers 2 way to approach the problem: > 1) Extend the Low level operation support with a way to save/display attached streams. This would require some XML configuration and possibly UI workflow to prompt user for the right action. Making from stream to file path would be not ideal and far from being user friendly. The good side is tha tit would work in any case (batch, non batch). The XML configuration can be a bit complex and prompting user is not an ideal workflow. > 2) Define a new high level command that would cope with any operation. > Such command would look like: > attachment save --operation=/subsystem=logging/log-file=server.log:read-attribute(name=stream) --file=/my/local/path/to/file > attachment display --operation=/subsystem=logging/log-file=server.log:read-attribute(name=stream) > - No risk to impact existing scripts. This is a new feature, so people would have to update their scripts to add the command. > - The challenge is located in mapping a Stream to a file name. The user provides the name he wants. Furthermore, in interactive mode, the user can use completion to complete this target file. > - No more prompting, the user knows ahead of time what he wants to do. > - Problem is that batch mode doesn't re-dispatch each step response to each input command. So some logic should be needed to properly handle streams in batch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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