It's probably six of one and half a dozen of the other, but I prefer
to keep those type of String constants external to the 'thing' to
which they refer -- vis a vis the page itself. The Page shouldn't
necessarily know it's path, besides which what you're really trying to
describe is the path to the spec (for all practical purposes anyway).
Plus, some pages may share the same page class (or not have one at
all) in which case this falls down.
Consider a statics class (or constants interface) that defines several
modules and pages within those modules.
public final class MyPages {
private static final String LOGIN_MODULE = "login";
public static final String LOGIN_PAGE = LOGIN_MODULE + '/' + "Login";
....
}
This gives good flexibility (both page name and module location are
easily modded) at the expense having to check out (or just modify) an
additional file whenever you refactor the pages.
-Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
