>
>What is the easiest way of defining a view that is available for every
>action.
>In this example I have kind of hard coded 'commonview' into every
>action:
>
>action1=Action1
>action1.success=action1.jsp
>action1.commonview=commonview.jsp
>
>action2=Action2
>action2.success=action2.jsp
>actio
I handle that with a trick! :)
if you create a 0 byte file in the webapp root, such as index.action , and
specify that as your welcome file, then it will work :)
Cheers,
/V
>From: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>CC: [EMAIL PROTECTED]
>Subject: Re: [Webwork-user] index.action vs ind
>
>When was this introduced? I must've missed it...argh..
>
>What does this give that the above solution doesn't give? It seems as
>though this is a serious security issue since a user can tweak the URI to
>get to data which should usually not be possible. Not good.
>
I don't think that behavio
Title: Message
Try
success.jsp
error.jsp
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of G.L.
GrobeSent: Monday, February 18, 2002 12:31 AMTo:
[EMAIL PROTECTED]Subject: [Webwork-user] command
driven
Afte
make you do things
their way which might not always be how you want them. WebWork gives you the
opportunity to at least have all that control and do it the way you want.
I understand this might seem overwhelming at first, but it's great... you'll
;
> ...
>
>
>
>Then webwork.config.XMLActionConfiguration should be modified to read the
>new "login-required" attribute and to map the actions to ".action" or to
>".s_action" depending on the "login-required"
I wrote such a beat a little while back. WARNING: Danger ahead :)
Anyways, it works the following way... you need to use the xml action
configuration (e.g. actions.xml). For any resource you want to protect, just
stick the attribute login-required='true' ... This works for action names
and ali
>
>On Fri, Feb 01, 2002 at 01:41:40PM +0100, Christoph Sturm wrote:
> > MH> I'm running Orion.
> >
>
Actually you said Orion + Sitemesh hmm.. unless you're using the latest
CVS, you have just spelled a formula for memory disaster. There was a HUGE
HUGE HUGE memory leak every time a page wa
>
>Well, that's not true. You can call "isCommand()" to determine
>which command is being invoked.
>
Hmm... this must me something new, as this was not in there originally. This
being the case, I see no problem in automatically calling validate from
execute in all cases (cda/non cda).
>
>>I ha
>
>
>The current code only calls validation if no command is set. Hm.. maybe
>this should be changed... what do ya'll think?
>
>
-1 ... Each command could require different validations, and given the fact
that you can't call something like getCommand, there would no way to detect
from where are
10 matches
Mail list logo
