Return-Path: 
 <users-return-1133-apmail-tiles-users-archive=tiles.apache.org@tiles.apache.org>
Delivered-To: apmail-tiles-users-archive@minotaur.apache.org
Received: (qmail 39571 invoked from network); 13 Mar 2009 00:56:42 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 13 Mar 2009 00:56:42 -0000
Received: (qmail 19542 invoked by uid 500); 13 Mar 2009 00:56:41 -0000
Delivered-To: apmail-tiles-users-archive@tiles.apache.org
Received: (qmail 19520 invoked by uid 500); 13 Mar 2009 00:56:41 -0000
Mailing-List: contact users-help@tiles.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tiles.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tiles.apache.org>
List-Post: <mailto:users@tiles.apache.org>
List-Id: <users.tiles.apache.org>
Reply-To: users@tiles.apache.org
Delivered-To: mailing list users@tiles.apache.org
Delivered-To: moderator for users@tiles.apache.org
Received: (qmail 82349 invoked by uid 99); 12 Mar 2009 23:48:07 -0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of ljs@mac.com designates
 17.148.16.92 as permitted sender)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Message-id: <7981369F-8E96-469A-AD4A-D3F75C498E94@mac.com>
From: Luke Scholefield <ljs@mac.com>
To: users@tiles.apache.org
Subject: Problems with "." character evaluation in Wild Cards
Date: Fri, 13 Mar 2009 10:17:35 +1030
X-Mailer: Apple Mail (2.930.3)
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,

I have been having some issues with the evaluation of wild cards.

The key part of my tiles definition is as follows:

	<definition name="app.*.*.*.*.*" extends="app.default">
		<put-attribute name="title"
			value="{1} --> {2} --> {3} --> {4} --> {5}" />
		<put-attribute name="body"
			value="/pages/{1}/{2}/{3}/{4}/{5}/index.jsp" />
	</definition>

	<definition name="app.*.*.*.*" extends="app.default">
		<put-attribute name="title" value="{1} --> {2} --> {3} --> {4}" />
		<put-attribute name="body"
			value="/pages/{1}/{2}/{3}/{4}/index.jsp" />
	</definition>

	<definition name="app.*.*.*" extends="app.default">
		<put-attribute name="title" value="{1} --> {2} --> {3}" />
		<put-attribute name="body" value="/pages/{1}/{2}/{3}/index.jsp" />
	</definition>


	<definition name="app.*.*" extends="app.default">
		<put-attribute name="title" value="{1} --> {2}" />
		<put-attribute name="body" value="/pages/{1}/{2}/index.jsp" />
	</definition>

	<definition name="app.*" extends="app.default">
		<put-attribute name="title" value="home --> {1}" />
		<put-attribute name="body" value="/pages/{1}/index.jsp" />
	</definition>

So basically, it splits the tiles path name up, and uses it to  
determine the appropriate path for the page file.  The value of  
'title' has is basically being used for debug at the moment, as I will  
shortly come to. There are other explicit definitions elsewhere.

So, ignoring the remapping stuff that would make this trick useful, if  
I just type into the browser,

app.test.subtest.tiles

The title appears as

home --> test.subtest

I have tried altering the definition order, but this does not seem to  
make a difference.

Annoyingly if I try:

app.test.subtest.foo.bar.tiles

I get:

test --> subtest --> foo --> bar

Which means the wildcards are handling the split correctly, in some  
cases.  It seems to be fine for all 4th level definitions.

And for

app.test.subtest.foo.bar.me.tiles

I get test --> subtest --> foo --> bar.me

So, in conclusion, the definitions work for 1st level path, 4th level  
path.  They half work for the 5th level path, and don't work at all  
for 2nd and 3rd.

Any ideas?  Maybe this feature would be a lot more useful if it worked  
with regular expressions.  Maybe something for 2.2?