[JBoss JIRA] (WFCORE-597) Where an ObjectTypeAttributeDefinition is in use respect the ResourceOnly setting on contained types for add operations.
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-597?page=com.atlassian.jira.plugin... ]
Kabir Khan updated WFCORE-597:
------------------------------
Fix Version/s: 1.0.0.CR1
(was: 1.0.0.Beta6)
> Where an ObjectTypeAttributeDefinition is in use respect the ResourceOnly setting on contained types for add operations.
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-597
> URL: https://issues.jboss.org/browse/WFCORE-597
> Project: WildFly Core
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Tomaz Cerar
> Labels: affects_elytron
> Fix For: 1.0.0.CR1
>
>
> If an ObjectTypeAttributeDefinition contains an attribute definition that has ResourceOnly set then it should be filtered from the automatically generated description for the add operation.
> This may be more related to lists, I currently have: -
> ObjectListAttributeDefinition, which contains ObjectTypeAttributeDefinition, which contains SimpleAttributeDefinition
> It is this final SimpleAttributeDefinition that has ResourceOnly set but it is still showing up in the operation description for add.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (WFCORE-602) Ability to view an objects index of it's position in a list.
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-602?page=com.atlassian.jira.plugin... ]
Kabir Khan updated WFCORE-602:
------------------------------
Fix Version/s: 1.0.0.CR1
(was: 1.0.0.Beta6)
> Ability to view an objects index of it's position in a list.
> ------------------------------------------------------------
>
> Key: WFCORE-602
> URL: https://issues.jboss.org/browse/WFCORE-602
> Project: WildFly Core
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Tomaz Cerar
> Labels: affects_elytron
> Fix For: 1.0.0.CR1
>
>
> General improvements are being made to the management model for more fine grained manipulation of complex attributes, amongst these changes will be the ability to insert items at a specific position in a list.
> This feature request is to ask for the ability to see an items index to identify it's position.
> i.e. an end user can call :read-recource and see an items position without needing to count how many items there are in order to identify the position of the next insert.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (WFCORE-642) ReadOperationDescriptionHandler doesn't handle multi-process wildcard addresses nicely
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-642?page=com.atlassian.jira.plugin... ]
Kabir Khan updated WFCORE-642:
------------------------------
Fix Version/s: 1.0.0.CR1
(was: 1.0.0.Beta6)
> ReadOperationDescriptionHandler doesn't handle multi-process wildcard addresses nicely
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-642
> URL: https://issues.jboss.org/browse/WFCORE-642
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 1.0.0.CR1
>
>
> Getting WFCORE-282 to work surfaces a problem with :read-operation-description handling, which will get invoked in the background by the CLI whenever the user inputs a wildcard read op.
> Problem is ReadOperationDescriptionHandler.getDescribedOp, which attempts to deal with cases where there is no resource registration for the target address. It checks if the request is for a wildcard address, and if so it sees if there are concrete registrations for that address, and if so whether they all use the same description. If yes, it provides the description.
> This is broken in a couple ways:
> 1) It assumes the wildcard applies to the last element in the address, which may not be the case with ops that support wildcard addressing schemes.
> 2) It looks vulnerable to problems with proxy resources, particularly the /host=* case on the DC where there can be a normal ConcreteResourceRegistration for the local host=master child, and then ProxyControllerRegistration instances for the various host=slave-x registrations. I suspect this might lead to false results.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years