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 statement is *enormously* appealing to me, a front end to back end Java
web developer leading a team of mostly front end web developers not interested
in a lot of framework specific details.
Yet, when working with the Stripes link element, I found that the attribute
beanclass was throwing an error, without having the beanclass actually
written yet. This seems to run counter to the argument presented in
"Incremental Development."
Here's the relevant part of the log (truncated and abridged for gmane)
Oct 12, 2008 10:26:30 PM net.sourceforge.stripes.util.Log info
INFO: Expression validation will be performed using:
net.sourceforge.stripes.validation.expression.Jsp21ExpressionExecutor
Oct 12, 2008 10:26:32 PM net.sourceforge.stripes.util.Log error
SEVERE: Could not find class of type: xxx.action.ViewSourceActionBean
java.lang.ClassNotFoundException: xxx.action.ViewSourceActionBean
at org.apache.catalina.loader.WebappClassLoader.loadClass
at org.apache.catalina.loader.WebappClassLoader.loadClass
at net.sourceforge.stripes.util.ReflectUtil.findClass
at net.sourceforge.stripes.tag.StripesTagSupport.getActionBeanType
at net.sourceforge.stripes.tag.StripesTagSupport.getActionBeanUrl
at net.sourceforge.stripes.tag.LinkTagSupport.getPreferredBaseUrl
at net.sourceforge.stripes.tag.LinkTagSupport.buildUrl
at net.sourceforge.stripes.tag.LinkTag.doEndTag
...
...
So, I guess I'm asking... is "Incremental Development" something lost in v1.5,
something configurable, or just something that works in some cases,
not in other cases?
Regards,
Tim
-------------------------------------------------------------------------
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
