Well Ted, Craig certainly wasn't singing that tune, although that doesn't mean you are wrong either.
As you and I discussed back when we tried to solve the problem of opening existing Struts applications to Axis/SOAP with Axis4Struts so a SOAP Actor can be just another View into Struts Applications, it would seem natural for Shale to have at least some vestige of interoperability, be that some interfaces or some "gateway" Actions, so the baby of existing production Struts Applications can take advantage of JSF/Shale without being thrown out with the bathwater. Michael Oliver CTO Alarius Systems LLC 3325 N. Nellis Blvd, #1 Las Vegas, NV 89115 Phone:(702)643-7425 Fax:(520)844-1036 *Note new email changed from [EMAIL PROTECTED] -----Original Message----- From: Ted Husted [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 01, 2005 10:41 AM To: Struts Users Mailing List Subject: Re: Shale <--> Struts 1.n On Tue, 01 Feb 2005 09:44:43 -0800, Michael Oliver wrote: > What are the plans for migration and/or interoperation for Shale > and Struts 1.n? There's been some talk on the dev list about using both frameworks together, on a temporary basis, but it's not recommended. It's a lot like asking what are "our plans for migration and/or interoperation for Tapestry and Struts 1.n?" They are two different frameworks, and there really isn't much reason for them to interoperate. Eventually, after Struts Shale ships, I'm sure people who migrate applications from other frameworks will beat a path and document some tips. But, right now, Shale is seen as a tool for new development for teams standardizing on JavaSererFaces, not as a successor to Struts 1.x. Like everyone else, most of the committers have significant Struts 1.x applications in production and see no reason to migrate them anytime soon. -Ted. > Michael Oliver > CTO > Alarius Systems LLC > 3325 N. Nellis Blvd, #1 > Las Vegas, NV 89115 > Phone:(702)643-7425 > Fax:(520)844-1036 > *Note new email changed from [EMAIL PROTECTED] > > > -------------------------------------------------------------------- > - 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
