--- Adam Levine <[EMAIL PROTECTED]> wrote:
> Where exactly did you read that all jsps must be fronted by actions?
> I'm
> using 1.1, and assuredly have NOT (nor will I) front them all with
> actions.
Keep in mind that it's as simple as:
to front JSPs with *.do actions. The benefits far outwei
x27;t scared but if you
were in the middle of the forest and night started falling... You'd start
fronting those darn JSPs
:-)
-Original Message-
From: Adam Levine [mailto:[EMAIL PROTECTED]
Sent: Monday, August 11, 2003 5:19 PM
To: [EMAIL PROTECTED]
Subject: RE: struts 1.1 question
Where exactly did you read that all jsps must be fronted by actions? I'm
using 1.1, and assuredly have NOT (nor will I) front them all with actions.
From: e <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Subject:
A good starting point for all you antidisestablishmentarianist that don't
want to front your JSPs might be the use of the ForwardAction and
global-forwards. That just forwards to a view page without writing a new
class. This way, when you are ready to do the right thing, you can change
some of
MAIL PROTECTED]>
To: 'Struts Users Mailing List' <[EMAIL PROTECTED]>
Subject: RE: struts 1.1 question
Date: Mon, 11 Aug 2003 17:02:13 -0400
A good starting point for all you antidisestablishmentarianist that don't
want to front your JSPs might be the use of the ForwardAction and
g
Yup. It really isn't so bad.
A lot of pages of what? You need a lot of pages even without Struts if your
site has a lot of content. You don't have any extra JSP pages because of it
but it makes you Struts config file a little longer than if you didn't have
to map all your JSPs. But then that
From the article at link below
Direct Requests to JSPs
To take the full advantage of sub-application support, Struts 1.1
stipulates the requirement that all requests must flow through the
controller servlet, i.e. the ActionServlet. Effectively, this means all
JSPs must be fronted by Action
Users Mailing List" <[EMAIL PROTECTED]>
Subject: Re: struts 1.1 question
Date: Mon, 11 Aug 2003 16:56:54 -0400
From the article at link below
Direct Requests to JSPs
To take the full advantage of sub-application support, Struts 1.1 stipulates
the requirement that all requests mus
Can you attach a form bean to an action defined as such?
Brad Handy
> -Original Message-
> From: David Graham [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 11, 2003 4:53 PM
> To: Struts Users Mailing List
> Subject: Re: struts 1.1 question
>
> --- Adam Lev
ge-
> > From: David Graham [mailto:[EMAIL PROTECTED]
> > Sent: Monday, August 11, 2003 4:53 PM
> > To: Struts Users Mailing List
> > Subject: Re: struts 1.1 question
> >
> > --- Adam Levine <[EMAIL PROTECTED]> wrote:
> > > Where exactly did you
August 11, 2003 4:48 PM
To: [EMAIL PROTECTED]
Subject: Re: struts 1.1 question
Where exactly did you read that all jsps must be fronted by actions? I'm
using 1.1, and assuredly have NOT (nor will I) front them all with actions.
From: e <[EMAIL PROTECTED]>
Reply-To: "Struts U
In fact, you have to front JSPs only if you're using modules, because
requests have to go through struts controller to know which module they
belong. If you're not planning to use modules, I think you can keep your
struts-config file the way it is. And as tiles and modules are independant,
the
I guess it just seems like extra work that doesn't yield obvious benefits,
not unlike having to do all those getters/setters in 1.0,
but I guess if I had to choose between the two, I'd choose this.
I guess I'm also partial to the familiar file extensions like .jsp..do
never did it for me, th
13 matches
Mail list logo
