Hi there -- Extending what Andy is talking about - the reason I like the Tacos solution is:
1. Developers can refactor without breaking bookmarks 2. Managers can let developers refactor without having to *worry* that the (junior) developers are going to break bookmarks. 3. A meaningful name for the developers may be confusing to the end user. For example, "EditWebsiteMessageEndPoints" v. "EditMyPages" On Wed, Jun 25, 2008 at 10:53 AM, Andreas Andreou <[EMAIL PROTECTED]> wrote: > Yep, uses a tiny annotation scanner lib that only scans > WEB-INF/classes (by default) at app startup time. > > Can't really tell how this messes up with synthetic pages > cause i don't quite know what you have in mind... in our > current T4 project, we've been using synthetic components > though which (i believe) is an equally powerful concept and > has the benefit of not messing with page names. > > -- Patrick Moore Amplafi 650-207-9792 "copy/paste" blog : http://www.sworddance.com/blog
