[JBoss JIRA] (WFCORE-2936) CLI parse blank string in command as undefined
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2936?page=com.atlassian.jira.plugi... ]
Jan Kalina updated WFCORE-2936:
-------------------------------
Description:
CLI parse following command:
{code}
/subsystem=elytron/constant-permission-mapper=test2:add(permissions=[{class-name="abc",action="",target-name=""}])
{code}
as:
{code}
{
"address" => [
("subsystem" => "elytron"),
("constant-permission-mapper" => "test2")
],
"operation" => "add",
"permissions" => [{
"class-name" => "abc",
"action" => undefined, <=== should be ""
"target-name" => undefined <=== should be ""
}]
}
{code}
*Blank strings are interpreted as undefined value by CLI parser.*
Problem is somewhere in *wildfly-core/cli*
was:
CLI parse following command:
{code}
/subsystem=elytron/constant-permission-mapper=test2:add(permissions=[{class-name="abc",action="",target-name=""}])
{code}
as:
{code}
{
"address" => [
("subsystem" => "elytron"),
("constant-permission-mapper" => "test2")
],
"operation" => "add",
"permissions" => [{
"class-name" => "abc",
"action" => undefined, <=== should be ""
"target-name" => undefined <=== should be ""
}]
}
{code}
*Blank strings are interpreted as undefined value by CLI parser.*
> CLI parse blank string in command as undefined
> ----------------------------------------------
>
> Key: WFCORE-2936
> URL: https://issues.jboss.org/browse/WFCORE-2936
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Beta25
> Reporter: Jan Kalina
>
> CLI parse following command:
> {code}
> /subsystem=elytron/constant-permission-mapper=test2:add(permissions=[{class-name="abc",action="",target-name=""}])
> {code}
> as:
> {code}
> {
> "address" => [
> ("subsystem" => "elytron"),
> ("constant-permission-mapper" => "test2")
> ],
> "operation" => "add",
> "permissions" => [{
> "class-name" => "abc",
> "action" => undefined, <=== should be ""
> "target-name" => undefined <=== should be ""
> }]
> }
> {code}
> *Blank strings are interpreted as undefined value by CLI parser.*
> Problem is somewhere in *wildfly-core/cli*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2936) CLI parse blank string in command as undefined
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2936?page=com.atlassian.jira.plugi... ]
Jan Kalina updated WFCORE-2936:
-------------------------------
Description:
CLI parse following command:
{code}
/subsystem=elytron/constant-permission-mapper=test2:add(permissions=[{class-name="abc",action="",target-name=""}])
{code}
as:
{code}
{
"address" => [
("subsystem" => "elytron"),
("constant-permission-mapper" => "test2")
],
"operation" => "add",
"permissions" => [{
"class-name" => "abc",
"action" => undefined, <=== should be ""
"target-name" => undefined <=== should be ""
}]
}
{code}
*Blank strings are interpreted as undefined value by CLI parser.*
was:
CLI parse following command:
{code}
/subsystem=elytron/constant-permission-mapper=test2:add(permissions=[{class-name="abc",action="",target-name=""}])
{code}
as:
{code}
{
"address" => [
("subsystem" => "elytron"),
("constant-permission-mapper" => "test2")
],
"operation" => "add",
"permissions" => [{
"class-name" => "abc",
"action" => undefined,
"target-name" => undefined
}]
}
{code}
*Blank strings are interpreted as undefined value by CLI parser.*
> CLI parse blank string in command as undefined
> ----------------------------------------------
>
> Key: WFCORE-2936
> URL: https://issues.jboss.org/browse/WFCORE-2936
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Beta25
> Reporter: Jan Kalina
>
> CLI parse following command:
> {code}
> /subsystem=elytron/constant-permission-mapper=test2:add(permissions=[{class-name="abc",action="",target-name=""}])
> {code}
> as:
> {code}
> {
> "address" => [
> ("subsystem" => "elytron"),
> ("constant-permission-mapper" => "test2")
> ],
> "operation" => "add",
> "permissions" => [{
> "class-name" => "abc",
> "action" => undefined, <=== should be ""
> "target-name" => undefined <=== should be ""
> }]
> }
> {code}
> *Blank strings are interpreted as undefined value by CLI parser.*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2936) CLI parse "" as undefined
by Jan Kalina (JIRA)
Jan Kalina created WFCORE-2936:
----------------------------------
Summary: CLI parse "" as undefined
Key: WFCORE-2936
URL: https://issues.jboss.org/browse/WFCORE-2936
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 3.0.0.Beta25
Reporter: Jan Kalina
CLI parse following command:
{code}
/subsystem=elytron/constant-permission-mapper=test2:add(permissions=[{class-name="abc",action="",target-name=""}])
{code}
as:
{code}
{
"address" => [
("subsystem" => "elytron"),
("constant-permission-mapper" => "test2")
],
"operation" => "add",
"permissions" => [{
"class-name" => "abc",
"action" => undefined,
"target-name" => undefined
}]
}
{code}
*Blank strings are interpreted as undefined value by CLI parser.*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2936) CLI parse blank string in command as undefined
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2936?page=com.atlassian.jira.plugi... ]
Jan Kalina updated WFCORE-2936:
-------------------------------
Summary: CLI parse blank string in command as undefined (was: CLI parse "" as undefined)
> CLI parse blank string in command as undefined
> ----------------------------------------------
>
> Key: WFCORE-2936
> URL: https://issues.jboss.org/browse/WFCORE-2936
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Beta25
> Reporter: Jan Kalina
>
> CLI parse following command:
> {code}
> /subsystem=elytron/constant-permission-mapper=test2:add(permissions=[{class-name="abc",action="",target-name=""}])
> {code}
> as:
> {code}
> {
> "address" => [
> ("subsystem" => "elytron"),
> ("constant-permission-mapper" => "test2")
> ],
> "operation" => "add",
> "permissions" => [{
> "class-name" => "abc",
> "action" => undefined,
> "target-name" => undefined
> }]
> }
> {code}
> *Blank strings are interpreted as undefined value by CLI parser.*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2730) empty target-name in constant-permission-mapper is not allowed
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2730?page=com.atlassian.jira.plugi... ]
Jan Kalina resolved WFCORE-2730.
--------------------------------
Resolution: Done
Closing back - reported problem is CLI parsing problem - recommend to open new WFCORE issue for it.
> empty target-name in constant-permission-mapper is not allowed
> --------------------------------------------------------------
>
> Key: WFCORE-2730
> URL: https://issues.jboss.org/browse/WFCORE-2730
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Eva Jarkovská
> Assignee: Jan Kalina
> Fix For: 3.0.0.Beta22
>
>
> For some purposes there is need to construct permission with blank string as param (name/action) - for example *WebResourcePermission*.
> Such permission cannot be currently assigned using *constant-permission-mapper* because it requires at least one character to be not-null:
> If I try to assing permission with blank name ({{target-name=""}}) (example in steps to reproduce), parse error is thrown:
> {code}
> | > ParseError at [row,col]:[367,5]
> | > Message: "WFLYCTL0113: '' is an invalid value for parameter
> | > target-name. Values must have a minimum length of 1 characters"
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (LOGMGR-148) Support suppressed exceptions in log formatting
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-148?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on LOGMGR-148:
------------------------------------------------
Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1441890|https://bugzilla.redhat.com/show_bug.cgi?id=1441890] from ON_QA to VERIFIED
> Support suppressed exceptions in log formatting
> -----------------------------------------------
>
> Key: LOGMGR-148
> URL: https://issues.jboss.org/browse/LOGMGR-148
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Components: core
> Reporter: David Lloyd
> Assignee: James Perkins
> Fix For: 1.5.7.Final
>
>
> In JDK 7 and on, a Throwable bundles a list of suppressed exceptions. We should be logging these as part of our exception formatting... however we have to do so thoughtfully, because every caused-by and suppressed exception may in turn have more suppressed exceptions and caused-by.
> This JIRA was created to track a back port of the JDK 7 enhancement to support suppressed exceptions to the 1.5.x branch which requires JDK 6. This will introduce a new requirement that the 1.5 branch will require JDK 7 to compile, but will still work on JDK 6.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month