February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1457) Guided rules editor function field does not perform semantic validation

by Kalyan gogineni (JIRA)

Kalyan gogineni created DROOLS-1457: --------------------------------------- Summary: Guided rules editor function field does not perform semantic validation Key: DROOLS-1457 URL: https://issues.jboss.org/browse/DROOLS-1457 Project: Drools Issue Type: Feature Request Components: build Reporter: Kalyan gogineni Assignee: Petr Široký guided rules editor function field does not perform semantic validation. For example: when you define rules like below When number 1 is not null And number 2 is not null Then number 3 = number5/number1 Note: Where number5 is not defined. Then when you compile or build and deploy then drools does not throw error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1456) Improve error messages and error handling on DMN compilation and execution

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1456: ------------------------------------- Summary: Improve error messages and error handling on DMN compilation and execution Key: DROOLS-1456 URL: https://issues.jboss.org/browse/DROOLS-1456 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.0.0.Beta6 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.0.0.Final This is a placeholder ticket for several small improvements on the error messages and error handling. 1. When a decision or a BKM has no expression, it raises the message “No expression defined for node ‘_guid’”. Would it be possible to put the node name when one is defined instead? 2. etc -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8254) Changing sasl-authentication-factory in management interface ends in reload-required state

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8254?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-8254: ---------------------------------------- Please file bugs against kernel resources in WFCORE. > Changing sasl-authentication-factory in management interface ends in reload-required state > ------------------------------------------------------------------------------------------ > > Key: WFLY-8254 > URL: https://issues.jboss.org/browse/WFLY-8254 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Darran Lofthouse > > Attribute sasl-authentication-factory is described as follows > {code} > "sasl-authentication-factory" => { > "type" => STRING, > "description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "capability-reference" => "org.wildfly.security.sasl-authentication-factory", > "min-length" => 1L, > "max-length" => 2147483647L > } > {code} > Documenation [1] says: > no-services – Applying the operation to the runtime does not require the restart of any services. This value is the default if the restart-required descriptor is not present. > But when I try to change it I get: > {code} > [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=application-sasl-authentication) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} > Probably some proper value for "restart-required" should be used. "restart-required" => "all-services" ? > [1] https://docs.jboss.org/author/display/WFLY/Description+of+the+Management+... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2345) Changing sasl-authentication-factory in management interface ends in reload-required state

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2345?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-8254 to WFCORE-2345: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2345 (was: WFLY-8254) Component/s: Domain Management Security (was: Security) > Changing sasl-authentication-factory in management interface ends in reload-required state > ------------------------------------------------------------------------------------------ > > Key: WFCORE-2345 > URL: https://issues.jboss.org/browse/WFCORE-2345 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Martin Choma > Assignee: Darran Lofthouse > > Attribute sasl-authentication-factory is described as follows > {code} > "sasl-authentication-factory" => { > "type" => STRING, > "description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "capability-reference" => "org.wildfly.security.sasl-authentication-factory", > "min-length" => 1L, > "max-length" => 2147483647L > } > {code} > Documenation [1] says: > no-services – Applying the operation to the runtime does not require the restart of any services. This value is the default if the restart-required descriptor is not present. > But when I try to change it I get: > {code} > [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=application-sasl-authentication) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} > Probably some proper value for "restart-required" should be used. "restart-required" => "all-services" ? > [1] https://docs.jboss.org/author/display/WFLY/Description+of+the+Management+... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2345) Changing sasl-authentication-factory in management interface ends in reload-required state

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2345?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2345: ---------------------------------------- Assignee: Brian Stansberry (was: Darran Lofthouse) > Changing sasl-authentication-factory in management interface ends in reload-required state > ------------------------------------------------------------------------------------------ > > Key: WFCORE-2345 > URL: https://issues.jboss.org/browse/WFCORE-2345 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Martin Choma > Assignee: Brian Stansberry > > Attribute sasl-authentication-factory is described as follows > {code} > "sasl-authentication-factory" => { > "type" => STRING, > "description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "capability-reference" => "org.wildfly.security.sasl-authentication-factory", > "min-length" => 1L, > "max-length" => 2147483647L > } > {code} > Documenation [1] says: > no-services – Applying the operation to the runtime does not require the restart of any services. This value is the default if the restart-required descriptor is not present. > But when I try to change it I get: > {code} > [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=application-sasl-authentication) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} > Probably some proper value for "restart-required" should be used. "restart-required" => "all-services" ? > [1] https://docs.jboss.org/author/display/WFLY/Description+of+the+Management+... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2344) Changing management interface with allow-resource-service-restart ends in reload-required state

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2344?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-8244 to WFCORE-2344: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2344 (was: WFLY-8244) Component/s: Domain Management Security (was: Security) > Changing management interface with allow-resource-service-restart ends in reload-required state > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-2344 > URL: https://issues.jboss.org/browse/WFCORE-2344 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Martin Choma > Assignee: Darran Lofthouse > > If I try to change elytron authentication for management interface with header {{allow-resource-service-restart=true}} server ends in {{reload-required}} state. > {code} > [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:write-attribute(name=http-authentication-factory, value=application-http-authentication){allow-resource-service-restart=true} > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} > Using header {{allow-resource-service-restart=true}} should restart necessary services. > If it can't be implemented for some reason, rather throw UnsupportedOperationException - it seems to me to be more fair. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2344) Changing management interface with allow-resource-service-restart ends in reload-required state

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2344?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2344: ---------------------------------------- Assignee: Brian Stansberry (was: Darran Lofthouse) > Changing management interface with allow-resource-service-restart ends in reload-required state > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-2344 > URL: https://issues.jboss.org/browse/WFCORE-2344 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Martin Choma > Assignee: Brian Stansberry > > If I try to change elytron authentication for management interface with header {{allow-resource-service-restart=true}} server ends in {{reload-required}} state. > {code} > [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:write-attribute(name=http-authentication-factory, value=application-http-authentication){allow-resource-service-restart=true} > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} > Using header {{allow-resource-service-restart=true}} should restart necessary services. > If it can't be implemented for some reason, rather throw UnsupportedOperationException - it seems to me to be more fair. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8263) mod_cluster does not work with EJB/JNDI/Transactions over HTTP

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8263?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-8263: ------------------------------------ Assignee: Stuart Douglas (was: Jason Greene) > mod_cluster does not work with EJB/JNDI/Transactions over HTTP > -------------------------------------------------------------- > > Key: WFLY-8263 > URL: https://issues.jboss.org/browse/WFLY-8263 > Project: WildFly > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8263) mod_cluster does not work with EJB/JNDI/Transactions over HTTP

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-8263: ------------------------------------ Summary: mod_cluster does not work with EJB/JNDI/Transactions over HTTP Key: WFLY-8263 URL: https://issues.jboss.org/browse/WFLY-8263 Project: WildFly Issue Type: Bug Reporter: Stuart Douglas Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8263) mod_cluster does not work with EJB/JNDI/Transactions over HTTP

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8263?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-8263: --------------------------------- Component/s: mod_cluster Web (Undertow) > mod_cluster does not work with EJB/JNDI/Transactions over HTTP > -------------------------------------------------------------- > > Key: WFLY-8263 > URL: https://issues.jboss.org/browse/WFLY-8263 > Project: WildFly > Issue Type: Bug > Components: mod_cluster, Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2017