> Why is it more convenient than tying it to a result page? Or do you run > the action without a result?
I will run the action without a result a few times to start off to make sure it compiles and goes through to success and so forth. I also have some (very few) actions that don't actually have a view at all, but write directly to the servlet output stream. Yes I know it's ugly, I hate it too, but there are several cases where I am pretty much forced to do this, most notably when the output needs to be streaming in some way. There is another early development thing you can do to make initial development easier, but that includes a change to MakeIterator (my diff and source is attached) and a default mapping of success to a jsp that does: <ww:iterator> <ww:print value="value/propertyType" /> <ww:print value="key" /><br /> </ww:iterator> I find it very handy for initial debugging. Anders Hovmöller [EMAIL PROTECTED] http://boxed.killingar.net
MakeIterator.java
Description: Binary data
Index: src/main/webwork/util/MakeIterator.java
===================================================================
RCS file: /cvsroot/opensymphony/webwork/src/main/webwork/util/MakeIterator.java,v
retrieving revision 1.3
diff -r1.3 MakeIterator.java
13c13
<
---
>
15c15
<
---
>
46c46
< else
---
> else if (value instanceof Iterator)
49a50,54
> else
> {
> value =
>(BeanUtil.buildFieldMap(value.getClass())).entrySet();
> iterator = ((Collection)value).iterator();
> }
52c57
<
---
>
