Freddy Daoud <[EMAIL PROTECTED]> writes: > > FWIW, the exception message in LinkTagSupport when the beanclass > attribute points to an action bean that does not (yet) exist is: > > "The value supplied for the 'beanclass' attribute " > + "does not represent a valid ActionBean. The value supplied was '" > + this.beanclass + "'. If you're prototyping, or your bean isn't ready > yet " > + "and you want this exception to go away, just use 'href' for now > instead." > > Indeed, the solution is to use href instead of beanclass until > the beanclass is written. IMHO, you shouldn't have just a warning when > beanclass doesn't point to a valid action bean, because when you are > refactoring an existing application and moving action beans around, you > want to know loud and clear if one of your beanclass attributes is now > invalid. >
I'm in agreement actually; but I'm defending Stripes and critiquing the arguments made about Incremental Development at the same time. However, using the HREF attribute will only work if you abandon the "pre-action" pattern, directly accessing the JSP call to the action class, correct? ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
