can then query it to know
what to show)
Is this a job for a custom Service Encoder (friendly URL)?
Any suggestions are welcome...
(sadly, i think i'll be able to hear a pin drop...)
DP
--
View this message in context:
http://www.nabble.com/How-to-parse-and-map-URLs--tp22730051p22730051.html
Sent
so that assets can then query it to know
what to show)
Is this a job for a custom Service Encoder (friendly URL)?
Any suggestions are welcome...
(sadly, i think i'll be able to hear a pin drop...)
DP
--
View this message in context:
http://www.nabble.com/How-to-parse-and-map-URLs
On Thu, Mar 26, 2009 at 4:04 PM, dpark dp...@exchangesolutions.com wrote:
Is this a job for a custom Service Encoder (friendly URL)?
This is presumably Tapestry 4.X, based on this reference (and past Exchange
Solutions experience)?
My guess is that you're better off with something like
Thiago has checked some code into 5.1.0.2 that gives you greater
control over how URLs are generated and interpreted.
On Thu, Mar 26, 2009 at 2:17 PM, Geoffrey Wiseman
geoffrey.wise...@gmail.com wrote:
On Thu, Mar 26, 2009 at 4:04 PM, dpark dp...@exchangesolutions.com wrote:
Is this a job for
be able to hear a pin drop...)
DP
--
View this message in context:
http://www.nabble.com/How-to-parse-and-map-URLs--tp22730051p22730051.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail