Return-Path: 
 <users-return-77503-apmail-cocoon-users-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-users-archive@www.apache.org
Received: (qmail 85179 invoked from network); 2 Mar 2005 16:54:13 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 2 Mar 2005 16:54:13 -0000
Received: (qmail 64247 invoked by uid 500); 2 Mar 2005 16:54:07 -0000
Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org
Received: (qmail 64203 invoked by uid 500); 2 Mar 2005 16:54:07 -0000
Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:users-help@cocoon.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@cocoon.apache.org>
List-Post: <mailto:users@cocoon.apache.org>
Reply-To: users@cocoon.apache.org
Delivered-To: mailing list users@cocoon.apache.org
Received: (qmail 64189 invoked by uid 99); 2 Mar 2005 16:54:07 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from bb0eb005.schwab.com (HELO bb0eb005.cdc.schwab.com)
 (162.93.195.149)
  by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 02 Mar 2005 08:54:06 -0800
Received: from s0743cdc.schwab.com (s0743cdc.schwab.com [162.93.239.70])
	by bb0eb005.cdc.schwab.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
 j22Gs49R021189
	for <users@cocoon.apache.org>; Wed, 2 Mar 2005 11:54:04 -0500
Received: (from root@localhost) by sendmail.cf s0743cdc  id j22Gs3Li032493 for
 users@cocoon.apache.org; Wed, 2 Mar 2005 11:54:03 -0500
Received: ( Schwab Email )
	by copymail.cf s0743cdc  with SMTP id j22Gs14n032440;
	for <users@cocoon.apache.org>; Wed, 2 Mar 2005 11:54:01 -0500
Received: From n2121pmx.nt.schwab.com ([10.100.85.232]) by
 n2110pmx.nt.schwab.com (WebShield SMTP v4.5 MR1a P0803.345);
	id 110978242560; Wed, 2 Mar 2005 09:53:45 -0700
Received: by n2121pmx.nt.schwab.com with Internet Mail Service (5.5.2657.72)
	id <THNGCTWR>; Wed, 2 Mar 2005 09:54:01 -0700
Message-ID: 
 <C02FC0734B54A441B624894D59D355B501197C85@nex1131sfo.us.global.schwab.com>
From: "Gawde, Kiran" <Kiran.Gawde@schwab.com>
To: users@cocoon.apache.org
Subject: RE: Using patterns for map:act elements ??
Date: Wed, 2 Mar 2005 09:53:41 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Not sure, but you may be able to use XSP actions.
<map:match pattern="*.do">
	<map:act type="xsp-action" src="action/{1}.xsp"> 
	</map:act>
    .......
</map:match>
-Kiran
(Object Edge Inc)

-----Original Message-----
From: Eric Shannon [mailto:eshannon@careersite.com] 
Sent: Tuesday, March 01, 2005 2:30 PM
To: users@cocoon.apache.org
Subject: Using patterns for map:act elements ??

In an effort to reduce the number of match patterns in my sitemap, I have a
desire to dynamically set the action handler.

I had hopped to find that map:act types support variable  substitution, but
that appears to not be the case.


For example, I would want a URL like: 
http://localhost:8080/myApp/form1.do  to use a generic match pattern 
like below.

Define:   <map:action name="process-form1" src="ProcessForm"/>

Then have a generic match pattern like so:
<map:match pattern="*.do">
    <map:act type="process-{1}">  //It would appear that this is NOT an 
option.
    .......
</map:match>

Any ideas on how generalize 100+ specific actions?

I could have a factory that creates/manages the actions internally and 
basically define one action handler in the pipeline that utilizes my 
factory.  I would think that this isn't a unique use case.

Input is appreciated.

-Eric



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org