Hi Rick,Actually you can quite easily. Have a base validator class that is called by both the controller and the external. The validator takes in the parameters passed in by the request context. If the validation fails then the controller should return null (if it passes continue with the ForwardAction redirect). The external will also use the validator class and on validation failure you can return the document with the appropriate error codes. You can then map the error codes to friendly messages by the business user.Say hi to Dan M. for me!
The foundation.jar provides the ValidationError and ValidationResult classes. There's sample usage in the sample user profile externals.[PHP]/iwadmin/main/spars/WORKAREA/Installed/foundation/toolkit_src/ls_runtime_srccom.interwoven.livesite.component.foundation.util.ValidationResultcom.interwoven.livesite.component.foundation.external.p13n.ProfileUtils#processProfileForm(RequestContext, UserProfile, String)com.interwoven.livesite.component.foundation.external.p13n.SelfRegistration#doSaveProfile(RequestContext)com.interwoven.livesite.component.foundation.external.p13n.UserAdministration#doSaveProfile(RequestContext)[/PHP]There's more out there in the wild, though obviously not all can be integrated with LiveSite. A quick search of stackoverflow.com for "java form validation" should get you some ideas.