[JBoss JIRA] (WFCORE-2786) Improve the composition operation output
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2786?page=com.atlassian.jira.plugi... ]
Filippe Spolti updated WFCORE-2786:
-----------------------------------
Component/s: Domain Management
(was: CLI)
> Improve the composition operation output
> ----------------------------------------
>
> Key: WFCORE-2786
> URL: https://issues.jboss.org/browse/WFCORE-2786
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Filippe Spolti
>
> When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
> I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
> {code:title=Payload}
> {
> "address": [],
> "json.pretty": 1,
> "operation": "composite",
> "steps": [
> {
> "name": "server-state",
> "operation": "read-attribute"
> },
> {
> "address": {
> "deployment": "*"
> },
> "name": "status",
> "operation": "read-attribute"
> }
> ]
> }
> {code}
> {code:title=Response}
> {
> "outcome": "success",
> "result": {
> "step-1": {
> "outcome": "success",
> "result": "running"
> },
> "step-2": {
> "outcome": "success",
> "result": []
> }
> }
> }
> {code}
> If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
> It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
> {code}
> {
> "outcome": "success",
> "result": {
> "step-1": {
> "operation-name": "server-state",
> "outcome": "success",
> "result": "running"
> },
> "step-2": {
> "operation-name": "deployment-info",
> "outcome": "success",
> "result": []
> }
> }
> }
> {code}
> Or
> {code}
> {
> "outcome": "success",
> "result": {
> "server-state": {
> "outcome": "success",
> "result": "running"
> },
> "deployment-info": {
> "outcome": "success",
> "result": []
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2786) Improve the composition operation output
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2786?page=com.atlassian.jira.plugi... ]
Filippe Spolti updated WFCORE-2786:
-----------------------------------
Description:
When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
{code:title=Payload}
{
"address": [],
"json.pretty": 1,
"operation": "composite",
"steps": [
{
"name": "server-state",
"operation": "read-attribute"
},
{
"address": {
"deployment": "*"
},
"name": "status",
"operation": "read-attribute"
}
]
}
{code}
Response:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"outcome": "success",
"result": "running"
},
"step-2": {
"outcome": "success",
"result": []
}
}
}
{quote}
If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"operation-name": "server-state",
"outcome": "success",
"result": "running"
},
"step-2": {
"operation-name": "deployment-info",
"outcome": "success",
"result": []
}
}
}
{quote}
Or
{quote}
{
"outcome": "success",
"result": {
"server-state": {
"outcome": "success",
"result": "running"
},
"deployment-info": {
"outcome": "success",
"result": []
}
}
}
{quote}
was:
When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
Payload:
{code:title=Payload|borderStyle=solid}
{
"address": [],
"json.pretty": 1,
"operation": "composite",
"steps": [
{
"name": "server-state",
"operation": "read-attribute"
},
{
"address": {
"deployment": "*"
},
"name": "status",
"operation": "read-attribute"
}
]
}
{quote}
Response:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"outcome": "success",
"result": "running"
},
"step-2": {
"outcome": "success",
"result": []
}
}
}
{quote}
If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"operation-name": "server-state",
"outcome": "success",
"result": "running"
},
"step-2": {
"operation-name": "deployment-info",
"outcome": "success",
"result": []
}
}
}
{quote}
Or
{quote}
{
"outcome": "success",
"result": {
"server-state": {
"outcome": "success",
"result": "running"
},
"deployment-info": {
"outcome": "success",
"result": []
}
}
}
{quote}
> Improve the composition operation output
> ----------------------------------------
>
> Key: WFCORE-2786
> URL: https://issues.jboss.org/browse/WFCORE-2786
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Reporter: Filippe Spolti
>
> When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
> I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
> {code:title=Payload}
> {
> "address": [],
> "json.pretty": 1,
> "operation": "composite",
> "steps": [
> {
> "name": "server-state",
> "operation": "read-attribute"
> },
> {
> "address": {
> "deployment": "*"
> },
> "name": "status",
> "operation": "read-attribute"
> }
> ]
> }
> {code}
> Response:
> {quote}
> {
> "outcome": "success",
> "result": {
> "step-1": {
> "outcome": "success",
> "result": "running"
> },
> "step-2": {
> "outcome": "success",
> "result": []
> }
> }
> }
> {quote}
> If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
> It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
> {quote}
> {
> "outcome": "success",
> "result": {
> "step-1": {
> "operation-name": "server-state",
> "outcome": "success",
> "result": "running"
> },
> "step-2": {
> "operation-name": "deployment-info",
> "outcome": "success",
> "result": []
> }
> }
> }
> {quote}
> Or
> {quote}
> {
> "outcome": "success",
> "result": {
> "server-state": {
> "outcome": "success",
> "result": "running"
> },
> "deployment-info": {
> "outcome": "success",
> "result": []
> }
> }
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2786) Improve the composition operation output
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2786?page=com.atlassian.jira.plugi... ]
Filippe Spolti updated WFCORE-2786:
-----------------------------------
Description:
When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
{code:title=Payload}
{
"address": [],
"json.pretty": 1,
"operation": "composite",
"steps": [
{
"name": "server-state",
"operation": "read-attribute"
},
{
"address": {
"deployment": "*"
},
"name": "status",
"operation": "read-attribute"
}
]
}
{code}
{code:title=Response}
{
"outcome": "success",
"result": {
"step-1": {
"outcome": "success",
"result": "running"
},
"step-2": {
"outcome": "success",
"result": []
}
}
}
{code}
If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
{code}
{
"outcome": "success",
"result": {
"step-1": {
"operation-name": "server-state",
"outcome": "success",
"result": "running"
},
"step-2": {
"operation-name": "deployment-info",
"outcome": "success",
"result": []
}
}
}
{code}
Or
{code}
{
"outcome": "success",
"result": {
"server-state": {
"outcome": "success",
"result": "running"
},
"deployment-info": {
"outcome": "success",
"result": []
}
}
}
{code}
was:
When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
{code:title=Payload}
{
"address": [],
"json.pretty": 1,
"operation": "composite",
"steps": [
{
"name": "server-state",
"operation": "read-attribute"
},
{
"address": {
"deployment": "*"
},
"name": "status",
"operation": "read-attribute"
}
]
}
{code}
Response:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"outcome": "success",
"result": "running"
},
"step-2": {
"outcome": "success",
"result": []
}
}
}
{quote}
If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"operation-name": "server-state",
"outcome": "success",
"result": "running"
},
"step-2": {
"operation-name": "deployment-info",
"outcome": "success",
"result": []
}
}
}
{quote}
Or
{quote}
{
"outcome": "success",
"result": {
"server-state": {
"outcome": "success",
"result": "running"
},
"deployment-info": {
"outcome": "success",
"result": []
}
}
}
{quote}
> Improve the composition operation output
> ----------------------------------------
>
> Key: WFCORE-2786
> URL: https://issues.jboss.org/browse/WFCORE-2786
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Reporter: Filippe Spolti
>
> When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
> I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
> {code:title=Payload}
> {
> "address": [],
> "json.pretty": 1,
> "operation": "composite",
> "steps": [
> {
> "name": "server-state",
> "operation": "read-attribute"
> },
> {
> "address": {
> "deployment": "*"
> },
> "name": "status",
> "operation": "read-attribute"
> }
> ]
> }
> {code}
> {code:title=Response}
> {
> "outcome": "success",
> "result": {
> "step-1": {
> "outcome": "success",
> "result": "running"
> },
> "step-2": {
> "outcome": "success",
> "result": []
> }
> }
> }
> {code}
> If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
> It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
> {code}
> {
> "outcome": "success",
> "result": {
> "step-1": {
> "operation-name": "server-state",
> "outcome": "success",
> "result": "running"
> },
> "step-2": {
> "operation-name": "deployment-info",
> "outcome": "success",
> "result": []
> }
> }
> }
> {code}
> Or
> {code}
> {
> "outcome": "success",
> "result": {
> "server-state": {
> "outcome": "success",
> "result": "running"
> },
> "deployment-info": {
> "outcome": "success",
> "result": []
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2786) Improve the composition operation output
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2786?page=com.atlassian.jira.plugi... ]
Filippe Spolti updated WFCORE-2786:
-----------------------------------
Description:
When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
Payload:
{code:title=Payload|borderStyle=solid}
{
"address": [],
"json.pretty": 1,
"operation": "composite",
"steps": [
{
"name": "server-state",
"operation": "read-attribute"
},
{
"address": {
"deployment": "*"
},
"name": "status",
"operation": "read-attribute"
}
]
}
{quote}
Response:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"outcome": "success",
"result": "running"
},
"step-2": {
"outcome": "success",
"result": []
}
}
}
{quote}
If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"operation-name": "server-state",
"outcome": "success",
"result": "running"
},
"step-2": {
"operation-name": "deployment-info",
"outcome": "success",
"result": []
}
}
}
{quote}
Or
{quote}
{
"outcome": "success",
"result": {
"server-state": {
"outcome": "success",
"result": "running"
},
"deployment-info": {
"outcome": "success",
"result": []
}
}
}
{quote}
was:
When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
Payload:
{code:title=Bar.java|borderStyle=solid}
{
"address": [],
"json.pretty": 1,
"operation": "composite",
"steps": [
{
"name": "server-state",
"operation": "read-attribute"
},
{
"address": {
"deployment": "*"
},
"name": "status",
"operation": "read-attribute"
}
]
}
{quote}
Response:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"outcome": "success",
"result": "running"
},
"step-2": {
"outcome": "success",
"result": []
}
}
}
{quote}
If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"operation-name": "server-state",
"outcome": "success",
"result": "running"
},
"step-2": {
"operation-name": "deployment-info",
"outcome": "success",
"result": []
}
}
}
{quote}
Or
{quote}
{
"outcome": "success",
"result": {
"server-state": {
"outcome": "success",
"result": "running"
},
"deployment-info": {
"outcome": "success",
"result": []
}
}
}
{quote}
> Improve the composition operation output
> ----------------------------------------
>
> Key: WFCORE-2786
> URL: https://issues.jboss.org/browse/WFCORE-2786
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Reporter: Filippe Spolti
>
> When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
> I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
> Payload:
> {code:title=Payload|borderStyle=solid}
> {
> "address": [],
> "json.pretty": 1,
> "operation": "composite",
> "steps": [
> {
> "name": "server-state",
> "operation": "read-attribute"
> },
> {
> "address": {
> "deployment": "*"
> },
> "name": "status",
> "operation": "read-attribute"
> }
> ]
> }
> {quote}
> Response:
> {quote}
> {
> "outcome": "success",
> "result": {
> "step-1": {
> "outcome": "success",
> "result": "running"
> },
> "step-2": {
> "outcome": "success",
> "result": []
> }
> }
> }
> {quote}
> If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
> It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
> {quote}
> {
> "outcome": "success",
> "result": {
> "step-1": {
> "operation-name": "server-state",
> "outcome": "success",
> "result": "running"
> },
> "step-2": {
> "operation-name": "deployment-info",
> "outcome": "success",
> "result": []
> }
> }
> }
> {quote}
> Or
> {quote}
> {
> "outcome": "success",
> "result": {
> "server-state": {
> "outcome": "success",
> "result": "running"
> },
> "deployment-info": {
> "outcome": "success",
> "result": []
> }
> }
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2786) Improve the composition operation output
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2786?page=com.atlassian.jira.plugi... ]
Filippe Spolti updated WFCORE-2786:
-----------------------------------
Description:
When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
Payload:
{code:title=Bar.java|borderStyle=solid}
{
"address": [],
"json.pretty": 1,
"operation": "composite",
"steps": [
{
"name": "server-state",
"operation": "read-attribute"
},
{
"address": {
"deployment": "*"
},
"name": "status",
"operation": "read-attribute"
}
]
}
{quote}
Response:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"outcome": "success",
"result": "running"
},
"step-2": {
"outcome": "success",
"result": []
}
}
}
{quote}
If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"operation-name": "server-state",
"outcome": "success",
"result": "running"
},
"step-2": {
"operation-name": "deployment-info",
"outcome": "success",
"result": []
}
}
}
{quote}
Or
{quote}
{
"outcome": "success",
"result": {
"server-state": {
"outcome": "success",
"result": "running"
},
"deployment-info": {
"outcome": "success",
"result": []
}
}
}
{quote}
was:
When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
Payload:
{quote}
{
"address": [],
"json.pretty": 1,
"operation": "composite",
"steps": [
{
"name": "server-state",
"operation": "read-attribute"
},
{
"address": {
"deployment": "*"
},
"name": "status",
"operation": "read-attribute"
}
]
}
{quote}
Response:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"outcome": "success",
"result": "running"
},
"step-2": {
"outcome": "success",
"result": []
}
}
}
{quote}
If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
{quote}
{
"outcome": "success",
"result": {
"step-1": {
"operation-name": "server-state",
"outcome": "success",
"result": "running"
},
"step-2": {
"operation-name": "deployment-info",
"outcome": "success",
"result": []
}
}
}
{quote}
Or
{quote}
{
"outcome": "success",
"result": {
"server-state": {
"outcome": "success",
"result": "running"
},
"deployment-info": {
"outcome": "success",
"result": []
}
}
}
{quote}
> Improve the composition operation output
> ----------------------------------------
>
> Key: WFCORE-2786
> URL: https://issues.jboss.org/browse/WFCORE-2786
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Reporter: Filippe Spolti
>
> When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N.
> I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example:
> Payload:
> {code:title=Bar.java|borderStyle=solid}
> {
> "address": [],
> "json.pretty": 1,
> "operation": "composite",
> "steps": [
> {
> "name": "server-state",
> "operation": "read-attribute"
> },
> {
> "address": {
> "deployment": "*"
> },
> "name": "status",
> "operation": "read-attribute"
> }
> ]
> }
> {quote}
> Response:
> {quote}
> {
> "outcome": "success",
> "result": {
> "step-1": {
> "outcome": "success",
> "result": "running"
> },
> "step-2": {
> "outcome": "success",
> "result": []
> }
> }
> }
> {quote}
> If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload.
> It will be great if we can add a extra field in the response or change the steps name to its operation name, for example:
> {quote}
> {
> "outcome": "success",
> "result": {
> "step-1": {
> "operation-name": "server-state",
> "outcome": "success",
> "result": "running"
> },
> "step-2": {
> "operation-name": "deployment-info",
> "outcome": "success",
> "result": []
> }
> }
> }
> {quote}
> Or
> {quote}
> {
> "outcome": "success",
> "result": {
> "server-state": {
> "outcome": "success",
> "result": "running"
> },
> "deployment-info": {
> "outcome": "success",
> "result": []
> }
> }
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-1282) Unable to create HTTPS connection using *ECDH_RSA* cipher suites / kECDHr cipher string
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1282?page=com.atlassian.jira.plugi... ]
Kabir Khan updated WFCORE-1282:
-------------------------------
Fix Version/s: 3.0.0.Beta21
(was: 3.0.0.Beta20)
> Unable to create HTTPS connection using *ECDH_RSA* cipher suites / kECDHr cipher string
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-1282
> URL: https://issues.jboss.org/browse/WFCORE-1282
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 1.0.2.Final
> Environment: Oracle Java
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 3.0.0.Beta21
>
> Attachments: client_debug_eap6.log, client_debug_eap7.log, server-cert-key-ec.jks, server_debug_eap6.log, server_debug_eap7.log
>
>
> User using these cipher suites / cipher name in EAP6 won't be able to use it in EAP7.
> Setting as critical as these cipher suites, are considered for strong and widely used in my opinion.
> In server log, error "no cipher suites in common" can be seen using -Djavax.net.debug=all.
> Note, that analogous configuration in EAP6 works fine.
> Issue can be seen on Oracle Java only, as on OpenJDK / IBM these suites are not provided by method getDefaultCipherSuites().
> Also is it possible to log "no cipher suites in common" and similar tls handshake errors without -Djavax.net.debug for better troubleshooting?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-887) "Deprecate" using an expression in model refs to interfaces
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-887?page=com.atlassian.jira.plugin... ]
Kabir Khan updated WFCORE-887:
------------------------------
Fix Version/s: 3.0.0.Beta21
(was: 3.0.0.Beta20)
> "Deprecate" using an expression in model refs to interfaces
> -----------------------------------------------------------
>
> Key: WFCORE-887
> URL: https://issues.jboss.org/browse/WFCORE-887
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 3.0.0.Beta21
>
>
> SocketBindingGroupResourceDefinition and OutboundSocketBindingResourceDefinition both have attributes that represent model refs to interface resources, but which also allow expressions.
> Model references should not allow expressions. These were "grandfathered in" when the large scale expression support roll out happened for AS 7.2 / EAP 6.1.
> There's no metadata facility to record that expression support is deprecated, but the add handler for these should log a WARN if they encounter an expression. Hopefully in EAP 8 we can then remove expression support.
> We should look for other cases like this too, although those changes should be separate JIRAs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years