Ah, I see. So you'd extend Transfer's generated getUserProperty method with your own, adding a check to make sure that the argument passed in matches one of the keys in the map? Neat idea.
On Tue, Mar 10, 2009 at 10:17 AM, John Whish <[email protected]> wrote: > Hi Bob, > Thanks for the repy. Using a struct instead of an array definitely makes > sense. > I've been reading my Heads First Design Patterns and they make heavy use of > Java Enums to define the properties. What I want to do is use > a MapFactoryBean to create my constants as a struct to avoid typos and also > anyone else (or myself in the future) can quickly see what properties the > User can have. > - John > > > -- Bob Silverberg www.silverwareconsulting.com --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
