RE: Struts Validator: 'fatal' and 'non-fatal' validations

yes and no...(errors are fatal...) you might want to signal the user that some field is filled with a bad value that would just be ignored... Or you have errors you want to emphasize in a different way than others (warnings and errors) Maybe you want to allow the user to press a special submit-bu

DO NOT REPLY [Bug 5274] New: - OutOfMemoryError when uploading big files

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Nesting Tags. v2... Now it's truly happenin'

Peoples, More sleepless ones later, I think that I have the nested extension as far as it needs to be for true adoption. All the tags that were applicable (logic and bean), little house cleaning, a bug fix (that cropped up with the new tags), new example, testing JSP for the new tags, tidier

Re: Proposal for form-based security

** Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ** : Hi Matt, It seems to me it is too much business logic

RE: Multiple controller servlets

Ted, I can see that. However, some of those collections are directly FastHashMaps, and some are wrappers like ActionFormBeans. I've thought that perhaps wrappers should be made for all of them to be consistent, and then ActionResources would be as you say - a means for accessing a reference which

Re: Struts Validator: 'fatal' and 'non-fatal' validations

Alan and I already talked offline, but I told him this might be a good place to get other opinions. I think that all validation errors are fatal. If it isn't fatal it is really a message, so you could use ActionMessages instead of ActionErrors. The equivalents of all the error methods could be

DO NOT REPLY [Bug 5271] New: - bad taglib directive examples

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Declarative Exception Handling

Yes, something like that is definately going to find its way into the distribution. But -- there are advantages with the exceptions being handled at the ActionServlet level. Perform really should have just thrown Exception to begin with. And so we're just noodling ways to get there from here. T

RE: Declarative Exception Handling

Can't you just make a default implementation of execute in the base Action class that calls perform? -- Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW/ 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 > -Original Message- > From: Dimitr

DO NOT REPLY [Bug 5263] New: - Can't build Struts WorkFlow component

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: General model question ?

Arron - fantastic extension! I've just started to use struts and have a question about how to pass the nested objects back to a data layer. I've setup a form with 1 simple property and a list property. All of my forms up to now have included specific properties and I'm trying to add a List

Re: Declarative Exception Handling

>I was thinking that anopther method, like execute() could just throw >exception and be called by the ActionServlet, and the perform() form >would not be called at all. So, like, deprecate perform() in favor of >execute() (or something), if we can get the controller to gracefully >choose between