[jboss-jira] [JBoss JIRA] (WFLY-1316) Missing operation description for the "composite" operation prevents its use in CLI
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Fri May 3 18:20:53 EDT 2013
[ https://issues.jboss.org/browse/WFLY-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry updated WFLY-1316:
-----------------------------------
Summary: Missing operation description for the "composite" operation prevents its use in CLI (was: Provide an operation description for the "composite" operation)
Issue Type: Bug (was: Task)
> Missing operation description for the "composite" operation prevents its use in CLI
> -----------------------------------------------------------------------------------
>
> Key: WFLY-1316
> URL: https://issues.jboss.org/browse/WFLY-1316
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.0.Alpha1
>
>
> When the "composite" operation registration was converted to OperationDefinition, the outputting of the operation description was lost. This is because the operation is registered as EntryType.PRIVATE and we don't produce descriptions for those operations. Without such a description, any attempt to use the low-level op directly via the CLI will fail:
> [standalone at localhost:9999 /] /:composite(steps=[{"operation"=>"read-resource"}])
> Operation 'composite' does not expect any property.
> See WFLY-1315 for the task of perhaps making this operation EntryType.PUBLIC.
> The task here is to hack in something so a description gets published even though the operation is EntryType.PRIVATE. This is a conservative approach to restore the behavior we had in EAP 6.0.x and can be backported to EAP 6.1.0.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list