Joe Germuska wrote:
Well, the difference between extending PopulateForm and putting a command after it which re-populates in the case of a SOAP request is small; the only caveat being that in the add-a-command-after model you must do it after or the existing PopulateForm action would clobber your efforts -- subclassing eliminates any questions about the ordering of events.

Yeah, I see your point. I'm coming at it from a purely gut instinct perspective... when I stop and think about it, I agree, the different is fairly small.


How does the strutsws kit respond to form validation failures? Is the "input" path overwritten when you clone the ActionMapping? You could keep doing that, or you could use the same model described for the forward, that is indicate the failed-validation-path in a property set in the ActionMapping.

That's exactly how. Just like there is a default response template, there is a default error template, or you can define your own in webservices-config.xml to do something more. The input is overridden with whichever one applies.


I don't know nothing about properness ;-)

It's interesting to have some more complex use cases to test the chain model against...

Absolutely. One thing that would be nice, and maybe it already is and I just don't know enough yet, is to be able to essentially restart the chain at any given point. That of course introduces the possibility of endless loops, but it makes it so that I could just do like restartChain() instead of forwarding back through tbe whole RP cycle.


Well, as I've said all along, I need to get up to speed on chain and 1.3's use of it before I can do more than stick my foot in my mouth here :)

I have to get beta2 of AjaxTags out the door first, and I also want to get my file manager app put up on Sruts Apps. After that I'll circle back around and really get in to StrutsWS on 1.3, unless Marco beats me to the punch of course! :)

Joe

Frank


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to