Return-Path: Delivered-To: apmail-struts-user-archive@www.apache.org Received: (qmail 59547 invoked from network); 1 Feb 2005 19:43:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 1 Feb 2005 19:43:03 -0000 Received: (qmail 68129 invoked by uid 500); 1 Feb 2005 19:42:51 -0000 Delivered-To: apmail-struts-user-archive@struts.apache.org Received: (qmail 68104 invoked by uid 500); 1 Feb 2005 19:42:51 -0000 Mailing-List: contact user-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list user@struts.apache.org Received: (qmail 68086 invoked by uid 99); 1 Feb 2005 19:42:51 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of craigmcc@gmail.com designates 64.233.170.196 as permitted sender) Received: from rproxy.gmail.com (HELO rproxy.gmail.com) (64.233.170.196) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 01 Feb 2005 11:42:51 -0800 Received: by rproxy.gmail.com with SMTP id y7so382235rne for ; Tue, 01 Feb 2005 11:42:48 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=YiRgIL8HSzgFmR7aBOzj/vBpb6CO+mv/WbAD/55/K3LVLJMI97Io8HJbk9fHfwH/G1RoFxXpgo22rdn2bbWDg4m+kkdojavkYRZZjZqwSDwhroiU8GW3tZS3L6IX3AnbGkXGlAQFTlKnv9TMrNWxURpVcK7xFv1W5xw74ISk5Wk= Received: by 10.38.75.39 with SMTP id x39mr48922rna; Tue, 01 Feb 2005 11:42:48 -0800 (PST) Received: by 10.39.3.22 with HTTP; Tue, 1 Feb 2005 11:42:48 -0800 (PST) Message-ID: Date: Tue, 1 Feb 2005 11:42:48 -0800 From: Craig McClanahan Reply-To: craigmcc@apache.org To: oliverm@sourceonenet.com Subject: Re: Struts 2.0 or Struts 0.0? Cc: Struts Users Mailing List In-Reply-To: <001f01c50870$60953e00$6401a8c0@OllieXP> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <001f01c50870$60953e00$6401a8c0@OllieXP> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Tue, 1 Feb 2005 07:11:59 -0800, Michael Oliver wrote: > Ted and I started "Axis4Struts" a while ago, but...didn't get much > activity and it died a slow death. The goal was stated to be "allow > SOAP access to existing and new Struts Applications so the SOAP actor is > just another user of the View of the Struts MVC." > > So, given the Shale features, can Shale be interoperable with existing > Struts 1.n applications? That is to say can a Shale CoR include Struts > Actions? Can a Shale Action be a wrapper for an existing Struts Action, > etc. It would be technically feasible to make Shale's CoR chain know how to invoke a classic Struts Action ... in essence, that's where Struts 1.3 in its use of CoR for the request processor pipeline (there's one particular command that grabs the request/response/etc. out of the context, and calls the execute method). If one were to do this, however, it would be wise to emulate the rest of the classic Struts request processing semantics too. > > 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 > Craig --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@struts.apache.org For additional commands, e-mail: user-help@struts.apache.org