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.

Cheers,
Freddy
http://www.stripesbook.com
 

On Mon, 13 Oct 2008 15:00:32 +0000 (UTC), "Timothy Stone"
<[EMAIL PROTECTED]> said:
> Ben Gunter <[EMAIL PROTECTED]> writes:
> 
> > 
> > AFAIK, this would not have worked in older versions of Stripes either. 
> > Have you tried using <s:link href="..." /> instead of beanclass?
> 
> Ahh... no, I have not tried the href attribute...
> But again, referring to the "Incremental Development" argument (which
> is now looking like it could have a touch of clarity lest it be over
> sold), the 
> *implied* benefit of using Stripes, and elements like <s:link ... > with
> or 
> without beanclass, is that the Stripes servlet will recognize the none
> existence 
> of the class and WARN, not FAIL. Thus allowing Incremental Development on 
> the front-end without the back-end in a "blocking state."
> 
> On Mon, Oct 13, 2008 at 10:30 AM, Timothy Stone  wrote:
> > One of the purported pros of Stripes in the "Stripes v. Struts" argument
> > is "Incremental Development."
> > However, last night, working through the code examples in the new title from
> > PragProg, /Stripes ... and Java web development is Fun again/ found me
> >  questioning this...
> > If you are not familiar with the "Pro" (as written on stripesframework.org),
> > it is copied here for reference:
> >   Incremental development
> >   Write a JSP with a Struts <html:form> tag on it and try to preview it in
> >   your container before you write your form-bean. Boom! You can't.
> >   Exception! Could not find form bean! Now write your form bean.
> >   Wait - that's still not good enough. Since everything is hooked
> >   together through the action stanza in the XML you better have an action,
> >   and edit that too.
> >   Maybe it's just me, but I like to be able to write my JSP, see if it looks
> >   ok, then go and write the back end components to go with it. It's not
> >   brain surgery, and Stripes lets you do it.
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------------------------
> 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

-------------------------------------------------------------------------
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

Reply via email to