You might try setting validate=false in the action mapping.
Mikkel Bruun wrote:
>
> Hi Craig,
>
> A blast from the past...I believe this post is a month old...
>
> Anyways...I see your point, but consider this...
>
> If I only refered to the functionaly (pages, actions whatever), I would have
> the following problem...
>
> myForm.do forwards to myAction which is validated to myForm...
>
> So if I linked to myForm.do, my GET would be validated and myForm would
> return errormessages...
>
> So I need an URL that doesn't trigger any logic, but just shows the form to
> the user...(or have a hidden init field in the form)...
>
> Mikkel
>
> -----Original Message-----
> From: Craig R. McClanahan
> To: '[EMAIL PROTECTED] '
> Sent: 02-06-2001 05:14
> Subject: Re: Hidding .jsp files
>
> On Tue, 15 May 2001, Mikkel Bruun wrote:
>
> > Hi Guys,
> >
> > Is it possible to make some sort of virtual path, enabling one to hide
> the
> > actual .jsp pages???
> >
> > Example,
> >
> > i want to avoid a link like /logon/logonform.jsp
> > replacing it with perhaps /logon (which in turn will point to
> > /logon/logonform.jsp)
> >
> > I tried looking at the globalforwards, but i find the documentation
> quite
> > lacking (there's an error in the code, btw)...but is this how its
> done???
> >
> > Another solution would be to make "empty" action classes that just
> returns
> > the succes mapping, but that would be going over the top imho...
> >
> >
> > Can anybody give an answer???
> >
> > thanks
> > Mikkel Bruun
> >
> >
> >
>
> One thing to keep in mind is that, in a typical Struts application, the
> names of the JSP pages are obscured anyway -- because the form submits
> go
> to the controller servlet. For example, walk your way through the
> Struts
> example application, and note how many of the locations actually shown
> have "*.do" extensions on them ...
>
> As a more radical way to hide things (but more for the purpose of
> discouraging users from setting bookmarks in the middle of an
> application), I've also resorted on occasion to more radical approaches:
>
> * Open the application in a window that doesn't have a location bar
>
> * Create a frameset with only one frame in it (so the location bar
> never changes at all).
>
> Craig McClanahan