I'm fine with calling them tags. I think how this is used will ultimately
determine what they are called. What do the others think?
On Tue, Mar 3, 2015 at 11:48 PM, Ondrej Zizka <ozizka(a)redhat.com> wrote:
I started working on selection. WINDUP-523
Multi-categories PR works (tests passed).
https://github.com/windup/windup/pull/485
WRT metadata API, I suggest it simply copies the structure of the proposed
XML at
https://docs.google.com/document/d/1F07dzjkAwupZ7-FusBP6OQXDkQzwwKqnqL7gE...
Note that I don't mean copying in terms of data classes, only the API, and
take the "Javascript prototypal inheritance" approach - bubble up through
Rule, RuleProvider, Ruleset, [user defaults, Windup defaults?] until a
value is found.
One note on possible necessity for a hashmap of random uncontrolled values
of unknown type: If there's such need, how about simply putting it inside
of the metadata - i.e. .getMetadata().getCustomData() or such?
Lastly, are we going to stay with "category" or change the naming to tags?
I would prefer tags - it's more general and I think users will use this
feature to more than just categories.
Ondra
On 3.3.2015 21:04, Lincoln Baxter, III wrote:
I checked the project calendar and we are on schedule for a 17/Mar/2015
release of 2.2.0.Final
The primary goal of this release (among other things), is enablement of
rule-set storage, categorization, and selection.
More updates tomorrow during the weekly meeting.
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
windup-dev mailing
listwindup-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev