That is what I did. On Thu, Dec 4, 2008 at 4:57 PM, Jared Rypka-Hauer <[EMAIL PROTECTED]> wrote: > > I'll grant you that you'd have to add > decorator="my.path.to.my.Decorator" to each tag, but why can't you > just put this in one decorator and apply that to all the classes? > > Even a find/replace operation should do the trick... if you have > something that supports regex, find/replace <object (.*) /> with > <object $1 decorator="my.path.to.my.Decorator" />, if not, then do a > find/replace on <object and replace it with <object > decorator="my.path.to.my.Decorator"... should be functional (if a > little ugly) and you can reformat your tags as you touch them while > working on the app. > > Honestly? It's the best way to go that I can think of. > > J > > On Dec 4, 2008, at 6:56 PM, Matt Graf wrote: > >> >> Yes I agree in most cases what I am trying to is not the best idea >> but, in our system we have four fields that are the same in every >> table. Which are insOn insByFK updOn and updByFk. and the fk is the >> foregin key to the user table and the our keys are UUID's which make >> no sense to user so in my base decorator I have getcreatedby and >> getupdatedby which looks up the user first and last name so I can >> display the name on the record. ... > > > >
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
