Nathan Bubna wrote: [..] > > Tool 4) Action Messages > > ----------------------- > > > > Class: org.apache.velocity.tools.struts.MessagesTool > > > > Recommended name in context: msgs > > > > Methods: > > > > public boolean exists(); > > > > public int getSize(); > > > > public int getSize(String property); > > > > public HashMap getAll(); > > > > public HashMap get(String property); > > ok, now i'm confused. we can't have two classes named > org.apache.velocity.tools.struts.MessagesTool and i don't like the idea of > having both a $msg and $msgs in the context. that's just asking for trouble.
One of the remaining issues was to find a clever context name for Action messages to avoid confusion with the message resources (named $msg in the context). Some brainstorming yielded: $messages - easily confused with $msg $amessages $actionmessages - too long $amsg $amsgs $am $actionmsgs $actionmsg $actionm $meldungen - switching language adds a new dimension :-) $infos $notes I guess my favorite so far is $amessages. It's somewhat special, so people will take note. Once they get the meaning of the word it should be easy to remember. Few developers use action messages at the moment. The class name of the tool is not sensitive, because it's used once. So, I would propose: org.apache.velocity.tools.struts.ActionMessagesTool Any better ideas are highly welcome. Gabe -- Gabriel Sidler Software Engineer, Eivycom GmbH, Zurich, Switzerland -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
