I proposed the ability to associate URL's with actions. When the URL is
requested the action is executed and the association is removed. This
removes the need for any Javascript solution or any hidden fields or any
such tricks.
Would the result of this execution be stored so that the second
boxed wrote:
I proposed the ability to associate URL's with actions. When the URL is
requested the action is executed and the association is removed. This
removes the need for any Javascript solution or any hidden fields or any
such tricks.
Would the result of this execution be stored so that
On Thu, Jan 16, 2003 at 08:45:53AM +0100, Rickard Öberg wrote:
Jason Carreira wrote:
I remember Rickard was talking about something to prevent 2 submits, but
I'm not sure what it was...
I proposed the ability to associate URL's with actions. When the URL is
requested the action is executed
There would be no hidden field. When the URL is generated that URL is
associated with the actions to be run. There's no way to figure out from
the URL what actions will be executed.
So you get URLs like:
http://www.myhost.com/some/path/wfjIFEOwijofOEIWjfIOWEkaAIoqjklnfoSyEj?foo=bar
And then a
Erik Beeson wrote:
There would be no hidden field. When the URL is generated that URL is
associated with the actions to be run. There's no way to figure out from
the URL what actions will be executed.
So you get URLs like:
On Thu, Jan 16, 2003 at 11:06:58AM +0100, Rickard Öberg wrote:
Philipp Meier wrote:
Hmmm, doest this mean, the jsp tag does sth. like
session.getTokenStack().push(new RandomToken()) and the action compares
the value passed in the hidden field to getTokenStack().pop()?
There would be no
Philipp Meier wrote:
Does this mean that when I use the ww:form tag, the target url will be
pushed / popped?
Not sure what you mean by pushed/popped. XWork would have an
association between user/URL and actions. When that user hits a URL the
association is used, and then removed.
/Rickard
On Thu, Jan 16, 2003 at 11:52:16AM +0100, Rickard Öberg wrote:
Philipp Meier wrote:
Does this mean that when I use the ww:form tag, the target url will be
pushed / popped?
Not sure what you mean by pushed/popped. XWork would have an
association between user/URL and actions. When that user
Hi all,
I like to develop [kind of] portal application with
some kind of portlets which could be minimized
/maximized
/ shuffled around etc.
( www.bejug.org is a good visual example of what I
like to achive )
So I'm curenlty diging around to solutions that are
already there.
I looked in
So we had our Webwork vs. Struts talk today, and I was able to convince
people here that there was sufficiently enough better about WW to make
us use it instead of Struts, even though Struts is the standard, of
sorts! Cool.
Off to catch a plane home...
--
Jason Carreira
Technical Architect,
For people using orion, or any other appserver that doesn't
automatically reload non-servlet classes in WEB-INF/classes, I've
written an action reloader that reloads action classes if they're
modified.
More details at: http://www.opensymphony.com:8668/space/fate
Feedback appreciated!
Hani
The way this is typically done is that as the form is generated a token
is placed into
the session and a hidden field is generated that matches this token.
When the action
is executed it is valid when the two tokens match. After the first
execution the session
token is removed. Therefore on
Can you summarize the points of that presentation?
On Thursday, January 16, 2003, at 09:12 PM, Jason Carreira wrote:
So we had our Webwork vs. Struts talk today, and I was able to convince
people here that there was sufficiently enough better about WW to make
us use it instead of Struts, even
Does that field also put the token into the session? Where's the code
that
adds the token to the session?
On Thursday, January 16, 2003, at 01:23 AM, matt baldree wrote:
no just added a hidden input field. this really isn't a ui tag.
- Original Message -
From: Jason Carreira [EMAIL
I have the code ;). I can add it if it is what people want but Rickard has a
point in trying to make this more automatic without adding a manual field. I
guess we could have the old fashion way and if/when the portlet framework
develops we can use it.
-Matt
- Original Message -
From:
Joseph Ottinger wrote:
I'd prefer adding it to the wiki or the current release of WW, since there
are some users who actually use what's there now as opposed to vapourware,
even though the vapourware is promising.
Didn't you resign from OpenSymphony? Or was it just that you stopped
doing
16 matches
Mail list logo
