I use (as does Jira) the same action served by both ServletDispatcher and also WebWorkExecutor (part of OSWorkflow).
-Pat ----- Original Message ----- From: "Rickard Öberg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, January 11, 2003 12:29 AM Subject: Re: [OS-webwork] XWork: core concepts > Peter Kelley wrote: > > Good to have you back > > I'm not back. I'm trying to see whether it's any point in me restarting > the XWork. > > > Are views a core concept ? > > Tricky one. Yes, I guess they should be, somehow. > > > The other thing we might want to address is > > whether or not XWork will be somewhat seperated at the core from the > > web. > > This is a very difficult question. Separating it from the javax.servlet > API should be possible, but overall I have the feeling that trying to > make a *too* generic solution might be crippling. > > A little poll: > *) How many have actions that are used with more than one kind of > dispatcher? > *) How many are using WebWork in Swing apps? > *) How many are using WebWork for RPC style stuff? (the > ClientServletDispatcher and friends) > > /Rickard > > -- > Rickard Öberg > [EMAIL PROTECTED] > Senselogic > > Got blog? I do. http://dreambean.com > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld http://www.vasoftware.com > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- 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
