- Original Message -
From: Patrick Lightbody [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, February 24, 2004 1:06 AM
Subject: RE: [OS-webwork] Security again
Well, I'm not sure if you know, but method calls are disabled during
ParametersInterceptor, so I think that went a
Title: Message
- Original Message -
From:
Jason Carreira
To: [EMAIL PROTECTED]
Sent: Friday, October 24, 2003 5:37
PM
Subject: RE: [OS-webwork] JSP page
exceptions
I
think this may be JSP implementation specific... where are the errors occuring
and
[...]
Is it correct that the main difference between
using the Action tag and the Include tag for 'componentising' a page is that
the Action tag uses the same value stack?
It seems include includes servlet's output
(copying stream data) and it's really not related to actions at
This of course wouldn't work for JSP tags, but I think it'd be possible
in the velocity tags. Open a jira issue and we'll get to it.
I don't know how it works for velocity tags, but it _is_ possible for JSP
Tags in case of JSP 2.0 spec where there is a notion of DynamicAttributes
tags.
Not
- Original Message -
From: Dick Zetterberg [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 10:07 AM
Subject: Re: [OS-webwork] Bug catching contest...
Can't you just fix this by using a ConcurrentHashMap or a
ConcurrentReaderHashMap from the
From: Jason Carreira [EMAIL PROTECTED]
I reset it back to the Xwork/WebWork notification scheme (it had been
turned off altogether)... I think it's valuable for new issues to come
here, so everyone can see what the issues are and might see that they're
not the only one seeing this... Only
[...]Sooo... Possible
solution: Have the ActionTag go back to the way it apparently worked in WW1,
nesting around the contents of the JSP. Move the functionality in the
doEndTag() to the doStartTag(). Split the functionality in
DefaultActionProxy.execute() into an invoke() method and a
Title: Message
- Wiadomo oryginalna -
Od: Jason
Carreira
Do: [EMAIL PROTECTED]
Wysano: 28 wrzenia 03 16:43
Temat: RE: [OS-webwork] ActionTag wipes
out own ActionContext
Ok,
what don't you like about the ActionTag/ActionProxy/ActionInvocation I'm
[...]
I know I should know this (it's late, so I have an excuse) but I don't
think
we have a a way for a Model (or Action, but Model is more important here)
to
be kept across a session. Formbeans have a nice property in Struts that
you
can do a wizard type UI with little effort because the
[...]
Of course that's just example that not necessarily happens.
The bottom line is that you have to be able to put a firewall
against input parameters before they get into action properties.
Again, why?
To prevent exposing random properties to be maliciously overwritten.
That's
[...]
I'm not sure how possible that would be... Actually, I'm relatively
certain that it would be difficult... It might be a feature we could add
with Xwork 1.1 when we rewrite the configuration API to actually be
runtime programmatically changeable...
- Wiadomosc oryginalna -
Od: Jason Carreira [EMAIL PROTECTED]
Do: [EMAIL PROTECTED]
Wyslano: 18 wrzesnia 03 18:37
Temat: RE: [OS-webwork] formbean vs. action
That's true, but you could check the param map and see if there's
anything not allowed in there and add errors... Which, with
[...]
I can't resolve the following issue - is this assumed that
invoke() may only be called once per instance, or multiple
times (I mean single request)?
Invoke on ActionInvocation? It is executed multiple times. Each call
moves it forward in the Interceptor chain, so each Interceptor
13 matches
Mail list logo
