Re: [wildfly-dev] Proposal for improving handling complex types in CLI
I've already commented on the gist, but for the record here's my point if view:
+1 on the custom operation for list/map modifications.
But I am against the write-attribute changes and generic complex attributes . IMO we'd
better be explicit about complex attributes and limit it to certain usecases:
write-attribute is for simple attributes only and yields an error for complex types
no support for generic complex attributes. these should become (child) resources
themselves
introduce an explicit ModelType.LIST and ModelType.MAP (i think the former already
exists)
/Heiko
On 14 Aug 2014, at 18:31, Tomaž Cerar <tomaz.cerar(a)gmail.com> wrote:
Hi guys,
there ware some discussions on how we should improve handling complex types of attribute
bit better in CLI.
For most part that was about Map & List types.
After some discussions with few of you I came up with plan / ideas what all options are
there for us to improve on.
you can see current state of proposed enhancements at
https://gist.github.com/ctomc/91055a6f4e7502dcd130
In short, I propose to add set of map-* and list-* global operations and improve
:read-attribute & :write-attribute
with EL like syntax for reading / updating map, list and generic complex attributes.
Let me know what you think about it, especially Console & CLI folks.
--
tomaz
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Attachments:
- attachment.html (text/html — 3.2 KB)