RE: Struts Dilemma

I think the best way to avoid this is to always use Strings and only Strings for all form values (except Collections). Then your action class can convert to/from the desired type when it creates the transfer object to pass to the business delegate. If you combine this approach with the struts

RE: Passing parameters between forms

This approach might work for a small system, but I would not encourage it for a large business app. If I follow you correctly, this assumes that subsequent pages will be served by the same container. This is infrequently (at least in systems I've seen) the case... -Original Message-

RE: validator

You have to play around with it a bit. Try something like this: field property=users.userDate depends=date arg0 key=user.date/ arg0 name=date key=The format of the user date resource=false / var

Validator, DynaForms, and Collections

Hi, I'm using the Struts Validator (version 1.1 release) on DynaValidatorForms. Everything seems to work just fine on forms that don't have collections on them. However, several of my forms have pull-down lists where I do something like: bean:define id=reasons name=MyFormName

RE: Tiles Definition problem

I don't think you want the slash when you reference your page. try this: global-forwards forward name=defaulttile redirect=true path=default.layout/ /global-forwards instead of: global-forwards forward name=defaulttile redirect=true path=/default.layout/