rahulmohan wrote:
The page is correct. It supports only a single conversation as of now. I
have a modified version which supports multiple conversations. Couldn't
get around to committing it so far. Will be happy to share the code
informally.
Given that it's me who is bleating
Roger,
Can I simply mail the eclipse project to you? We can discuss the usage
over email and get it running. I am planning to work on this over the next
week and therefore we can actually release the plugin formally in a week
or two.
Regards,
Rahul
rahulmohan wrote:
The page is
Hi Rahul,
Please send it to rogerdotvarleyatgooglemaildotcom
Thanks
Roger
--
View this message in context:
http://old.nabble.com/Struts-2%2C-Session-Management-and-%22WorkFlow%22.-tp29726121p29736089.html
Sent from the Struts - User mailing list archive at Nabble.com.
Hi,
I have a use case, where after the user logs in to the application
(handled by Spring Security) I need to start a setup wizard comprising
three views and their associated actions. These must be processed in strict
sequence and the user must not be allowed to break out by either typing a
URL
Hi Roger,
i'm not familiar with SpringWebflow,
maybe some one who uses it can aswear if this can be achevied only by it,
but i would go fo my own custom interceptor in this case and
SpringWebflow only to support wizzard webflow.
Mainly because there are more things that needs to be addressed than
Paweł Wielgus wrote:
In an interceptor You can check if a user is logged in,
so it's easy to have wizzard immediate after login
and only login page if user is not logged in.
Then after user is logged in You can check if wizzard is completed and
if not redirect him at current wizzard
Hi Roger,
That would work in this case, but my interceptor would be specific to the
wizard. If I then introduced a second wizard, then I'd need another
interceptor to handle that one. I was hoping for something a little more
generic.
Won't You also add more bussiness logic if You add
Seam handles multiple conversations; you might see how it implements it.
Dave
On Thu, Sep 16, 2010 at 6:24 AM, RogerV roger.var...@googlemail.com wrote:
Paweł Wielgus wrote:
In an interceptor You can check if a user is logged in,
so it's easy to have wizzard immediate after login
and
Paweł Wielgus wrote:
Every form needs to have all necessary ids as hidden fields.
That way, posting a form will always update appropriate object with
appropriate data.
Agreed, but how do you check that the hidden ids that come back with the
submit are the ones that
you sent in the
Agreed, but how do you check that the hidden ids that come back with the
submit are the ones that
you sent in the first place? It's not that hard to use something like
HttpClient to send malicious POST's
Yes, it's possible but not likely, in general users use multiple tabs,
and they don't use
obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Thu, 16 Sep 2010 04:16:28 -0700
From: roger.var...@googlemail.com
To: user@struts.apache.org
Subject: Re: Struts 2, Session
On Thu, Sep 16, 2010 at 7:57 AM, Martin Gainty wrote:
com.opensymphony.xwork2.ValidationAware
/**
* Set the field error map of fieldname (String) to Collection of String
error messages.
* @param errorMap field error map
*/
void setFieldErrors(MapString, ListString
Hi Pawel,
Paweł Wielgus wrote:
Agreed, but how do you check that the hidden ids that come back with the
submit are the ones that
you sent in the first place? It's not that hard to use something like
HttpClient to send malicious POST's
Yes, it's possible but not likely, in general users
Correct--the essence of implementation is just a dual-layer context with
the additional key passed back and forth (I assume for every request).
On Thu, Sep 16, 2010 at 8:14 AM, RogerV roger.var...@googlemail.com wrote:
Hi Pawel,
Paweł Wielgus wrote:
Agreed, but how do you check that the
Dave Newton-6 wrote:
Correct--the essence of implementation is just a dual-layer context with
the additional key passed back and forth (I assume for every request).
Hi Dave,
Doesn't seem too complicated to implement :) - but given this conversation
from Jan 2009
RogerV wrote:
Dave Newton-6 wrote:
Correct--the essence of implementation is just a dual-layer context
with
the additional key passed back and forth (I assume for every request).
Hi Dave,
Doesn't seem too complicated to implement :) - but given this
conversation from Jan
Hi all,
i've just read about Seam,
and if i understand it wright,
creation of Conversation is made by annotation, so it's not an
automatic decision of the framework
but just a developer decision in action code to create a conversation.
Unlikely in an Intranet environment prehaps, but there are
Date:
16-09-2010 18:34
Subject:
Re: Struts 2, Session Management and WorkFlow.
RogerV wrote:
Dave Newton-6 wrote:
Correct--the essence of implementation is just a dual-layer context
with
the additional key passed back and forth (I assume for every request).
Hi Dave
rahulmohan wrote:
Exactly! I think scope plugin solves your problem. The conversation
support in scope plugin is not as rich as that in seam, but can serve as
the starting point. I have fixed a couple of bugs in the scope plugin and
I am working on some enhancements in scope plugin
I don't believe it allows multiple conversations yet, but I haven't checked
the source, either.
Dave
On Thu, Sep 16, 2010 at 9:56 AM, RogerV roger.var...@googlemail.com wrote:
rahulmohan wrote:
Exactly! I think scope plugin solves your problem. The conversation
support in scope
rahulmohan wrote:
Exactly! I think scope plugin solves your problem. The conversation
support in scope plugin is not as rich as that in seam, but can serve
as
the starting point. I have fixed a couple of bugs in the scope plugin
and
I am working on some enhancements in scope
21 matches
Mail list logo
