Re: Re: The future of XWork with the merger

"Chris Custine" <[email protected]>
Newsgroups gmane.comp.java.open-symphony.webwork
Message-ID <[email protected]>
One thing that I worry about is losing the distinction between XWork
vs. WebWork and I think keeping XWork  where it is would make it
easier to keep that distinction.  I am using XWork command pattern
impl as the basis for several projects that are not web based at all
(middleware, back end processing, etc.), so I worry a bit about
opening up XWork to a crowd that may only see it as the command
processing for web apps.  I am sure this topic has come up amongst
Jason and Patrick et al, but I wanted to voice it here in case it
hasn't come up.

Chris

On 4/18/06, Jason Carreira <[email protected]> wrote:
> I'd rather make the Struts committers interested in working on XWork committers here too. Keeping XWork here maintains our heritage / relationship with OpenSymphony and has probably positive effects for the visibility of OpenSymphony, etc.
> ---------------------------------------------------------------------
> Posted via Jive Forums
> http://forums.opensymphony.com/thread.jspa?threadID=26295&messageID=51878#51878
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.