This post originated from an RSS feed registered with Java Buzz by Jason Carreira. Original Post: RE: WebWork Fun Feed Title: Jason Carreira Feed URL: http://sedoparking.com/search/registrar.php?domain=®istrar=sedopark Feed Description: Personal Aggrandizement Latest Java Buzz Posts Latest Java Buzz Posts by Jason Carreira Latest Posts From Jason Carreira

Been spending the last few days exploring WebWork2... having great fun and deeper apprecation for their work done. And makes my job so much easier. Now, to evangalise the framework to the rest of my team... For those who have not tried it, I say give it a go. It's still a little scratchy now, but do remember it's still a beta. I might come up with a simple example later on, one concern is that I might document some mistakes. But hey, no embarassment, no gain. I've been having some problems, but somehow they ended up being my design problems. So far, I've misused the interceptors, misused the components, did a "dispatcher" when I should have done a "chain"....

Currently facing one killer, apparently errors do not propogate across the action chains.

For example, I have ActionA and ActionB. ActionA returns INPUT which chains to ActionB. From ActionA, the errors are still visible, but when in ActionB, they seem to be cleared, and the result is rendered without displaying the errors. Not sure why... will have to take a deeper look into it. However, anyone who might have a clue to what I've done wrongly, please do help. Thanks in advance.

The errors are not lost, but probably hidden. If the next Action also implements ValidationAware, then it will have its own error properties, so when you check the ValueStack for fieldErrors (using the Ognl expression language), it looks at the ones in your current action. I think what you can / should do is apply the ActionChainInterceptor to the Interceptors for the Action you're chaining to... This will copy all of the properties from the first Action to the next... I need to put this on the Wiki.