Hi everyone,
can someone confirm whether in struts's validator
(which if i'm not mistaken, rely on commons-validator),
we can or we can not
use non-standard bundle (i.e ApplicationResources.properties)?
If not, what's the usual workaround that you do?
I've tried using Struts 1.2, downloaded fro
20 different sets of input/view forms). Now we are
> >going to migrate an application which we wrote in our own framework to
> >Struts. This contains about 300 separate input/view forms (a lot will be
> >reduced down due to re-usability of Struts over our own framework). As
>
Hi all,
Struts-validator, or I guess it has become common-validator (?) is very cool,
a lot of thanks for making life easier.
Because there are lots of entities in application that I'm developing, more than 80,
the validation.xml file will be so big, roughly more than two thousands line.
For such
ss you've got a
simpler description than my guess above) unless you have tens or hundreds of
JSP's to make and have no layout you require (as it would require nearly
equivalent amounts of cutting & pasting).
Regards,
David
-Original Message-
From: Dionisius Purba [mailto:[EM
way around.
Now that I'm using Xdoclet, I have no further need for those extension
tools.
Regards,
David
-Original Message-
From: Dionisius Purba [mailto:[EMAIL PROTECTED]
Sent: Friday, April 23, 2004 1:21 AM
To: 'Struts Users Mailing List'
Subject: generate struts ActionFor
Altough my question is related to hibernate, I hope it's still relevant.
Is anyone aware of tools, open source is better, that can generate
ActionForm and the JSP's (containing struts's HTML Input tag)
based on a hibernate's mapping (i.e. *.hmb.xml)?
cheers,
dion
---
about large numbers of classes,
and yes, that can happen, but as long as you're organised and make judicious
use of Java packages, it's not a problem.
--
Martin Cooper
"Dionisius Purba" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
One Action for each Use Case
DispatchAction is what exactly is meant for these kinds of situations.
Kulkarni.
> -Original Message-
> From: Dionisius Purba [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 22, 2004 10:43 AM
> To: 'Struts Users Mailing List'
Hi,
I was wondering what's the advantage and disadvantage of
creating one Action for each use case, i.e. creating
NewAccountAction.java
EditAccountAction.java
or even with NewAccountFormAction.java
vs
AccountAction.java
and inside the AccountAction we can check parameter from the JSP
then execut
9 matches
Mail list logo
