I am leaning towards that conclusion. We'll leave this thread up here and see what others think. There isn't really any harm in including it in MyFaces. It would be another attribute that you could add to a tag and a few custom renderers. Not a big deal really.
On the other hand, if this is really something only I care about. Why subject anyone else to it ;-) On Tue, 18 Jan 2005 14:31:58 -0800, Travis Reeder <[EMAIL PROTECTED]> wrote: > I think you should just create your own custom components to add this, > definitely not something that should be in MyFaces. > > Travis > > > Sean Schofield wrote: > That's a bit difficult in my case. I have a perfectly functioning system > already with real data. Suppose I don't want to add fake data to my > production system. Also, the data is in a lot of different tables with > foreign keys, etc. Finally some of the data tables are not under our control > - we just read from them. On Tue, 18 Jan 2005 16:16:41 -0600, Heath > Borders <[EMAIL PROTECTED]> wrote: > You can't just create dummy data? On Tue, 18 Jan 2005 17:13:38 -0500, Sean > Schofield <[EMAIL PROTECTED]> wrote: > What do you think about this idea ... Our current application at work uses > very sensitive data. I've often wanted to show the application to other > clients but I don't want any of this data to be shown. Maybe we could > modify the ext tags to provide a "private" attribute (true/false.) Then > supply some custom renderers that could render a private version of the > data. So for example "Sean Schofield" could become "#### #########". Would > this be useful for anyone else besides myself? I'm thinking it could also be > used to generate screen shots for user guides. Thoughts? sean -- -Heath > Borders-Wing [EMAIL PROTECTED] > -- Travis Reeder Ecommstats Web Analytics www.ecommstats.com
