Why would you need to call the DB three separate times? If you're already
returning a JSP why wouldn't you build everything you needed from the action
that processes the original submit? All you're doing is composing the
results of a few services--no need to call actions to do that, call the same
s
I have an application that I need to develop that requires the following:
Following selection by the user of the item of interest plus up and
downstream padding, report the locations and characteristics of features of
interest found in the region and display the data graphically with clickable
lin
Hi, does anyone know of a validation method in struts that can use your JPA
(or other usage agnostic) annotations to validate the values on form fields?
For example, if I have specified a max length on an entity property and a
mandatory option on another then when updating / creating that entity vi
I'm not familiar with the tag; does that auto-include the script
defining the validateForm() function?
If not, I'd suggest a missing
What happens? What do you expect to happen? What's your validation config?
We need something beyond "it doesn't work".
Dave
On Sep 2, 2011 3:47 AM, "RajasekharReddy" wrote:
> I am trying to implement Client-Side Validations using struts 1.3
>
> But server Side validations are working properly, b
I am trying to implement Client-Side Validations using struts 1.3
But server Side validations are working properly, but Client-Side
Validations are not working properly.
My code is as follows
<%@ taglib prefix="html" uri="/WEB-INF/struts-html.tld" %>
<%@ taglib prefix="bean" uri="/WEB-INF
6 matches
Mail list logo
