Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: softfail (hermes.apache.org: transitioning domain of
 oliverm@sourceonenet.com does not designate 68.230.241.37 as permitted
 sender)
Reply-To: <oliverm@sourceonenet.com>
From: "Michael Oliver" <oliverm@sourceonenet.com>
To: "'Struts Users Mailing List'" <user@struts.apache.org>,
	<oliverm@sourceonenet.com>
Subject: RE: Shale <--> Struts 1.n
Date: Tue, 1 Feb 2005 11:09:22 -0800
Organization: SourceOne Network
Message-ID: <009701c50891$89dbca10$6401a8c0@OllieXP>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <200521134119.286495@pc18>
Importance: Normal

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 oliverm@matrix-media.com

-----Original Message-----
From: Ted Husted [mailto:husted@apache.org]=20
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:
>=A0What are the plans for migration and/or interoperation for Shale
>=A0and 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.=20

Eventually, after Struts Shale ships, I'm sure people who migrate
applications from other frameworks will beat a path and document some
tips.=20

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.

>=A0Michael Oliver
>=A0CTO
>=A0Alarius Systems LLC
>=A03325 N. Nellis Blvd, #1
>=A0Las Vegas, NV 89115
>=A0Phone:(702)643-7425
>=A0Fax:(520)844-1036
>=A0*Note new email changed from oliverm@matrix-media.com
>
>
>=A0--------------------------------------------------------------------
>=A0- To unsubscribe, e-mail: user-unsubscribe@struts.apache.org For
>=A0additional commands, e-mail: user-help@struts.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org