> -----Original Message----- > From: Joel Cordonnier [mailto:[EMAIL PROTECTED]] > > I'm trying to port an application from IBM WPS. to Webwork. After looking the webwork java code, comes the following questions: > > - Actions are used after initilizing the ActionContext, context in with they are executed. Right ? HTTP request parameters, responses, session specific parameters are set with dispatcher at the moment, right ? This means that Action parameters are inconsistent when used before the dispatchers initialize their state. Right ?
Right. But the thread of execution won't come to the execute method of the Action until it is initialized. > Subclassing ActionSupport and adding some attributes to a this new subclass, is a possibility to save Action specific state: right or false ? How do you mean? You can save things into the Session, but Actions themselves are not persisted. > - the view for XSLT Action (i.e action with xml view) is pull with the help of XMLReaderAdapter class. What do you think about a new XMLAction class, subclass of ActionSupport, with just one new method "getXML(boolean)" with the boolean value saying: retrieve a shared XML content or a user specific XML stream ? I've never used the XSLT view, but I don't think it uses an actual XML text stream, I think it uses reflection to mimic the structure of an XML document. Jason ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
