John, While your last comment is extremely snide and unnecessary, I'll still engage in conversation with you.
I do not find it obvious. While I can see that a string array can't be 'custom', I do NOT see how a properly formatted object allows a 'get' of an attribute but not a 'set' of an attribute. While I'm running through this API, this is the first occurrence if this that I have come across. No matter the style of the list of objects, I must use the 'getValues()' method to return a List<EnumItem>....if they wanted to differentiate a regular from accustom by specifying one of them is a array of strings, and the other was a List<EnumItem>, then they should have two different get methods. While we could debate the merit of this approach, I'll thank you for the information you provided (minus the snarky comments) and move on. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of John Baker Sent: Monday, December 12, 2011 1:31 AM To: arslist@ARSLIST.ORG Subject: Java API Help - SelectionFieldLimit LJ, If you use the constructor or set method that takes an array of Strings, you get a regular list. If you use the constructor or set method that takes a list of EnumItems, you get a custom list. I'll leave it to you for feedback on how obvious this seems :-) John ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
