Thanks for the response. Surely appreciate your comment.
-Original Message-
From: Filip S. Adamsen [mailto:[EMAIL PROTECTED]
Sent: Friday, July 11, 2008 7:45 PM
To: Tapestry users
Subject: Re: Routing and REST
Hi,
Please start a new thread to ask a new question.
That said, Tapestry 3
We have one webapp (implemented using tapestry). During the step #2 i
stated below we create another object called FandomContext, this object
maintains the team specific information (teamId, rivalId, etc etc) and
put that object into the request attributes, making it available to the
webapp co
Hi,
Please start a new thread to ask a new question.
That said, Tapestry 3 is rather old by now - if at all possible I'd
advice you to move to Tapestry 5.
And unfortunately, I don't know how to solve your problem. Maybe someone
else knows.
-Filip
Henry Remigio C. Osorio II skrev:
I am ne
I am new to tapestry, and currently using Tapestry 3.0 for our development.
I keep on experiencing the problem "Page Recorder for page X locked after a
commit", I would like to confer if it still exist within Tapestry 4?
Thanks
-
1) We map the webapp to the root ("/") context.
2) We use a normal Webapp Filter to pull out the first directory path
from the url and make that the new context (request.getContextPath()..
etc etc ), and capture that to determine which sports team we're going
to be serving up.
hi fernando,
This request sounds a little open ended, and I think you can do
everything you need with Webapp Filters and Tapestry Filters/Services,
you just have to spend the time to learn them and think outside the box
a little bit.
Our project is using T5 for Facebook and OpenSocial applications so
ther
Currently the logic necessary to do what you want is part of Tapestry
internals (non public, subject to change). I would approach this
problem using an override of the LinkFactory service (internal)
combined with an in-Tapestry filter to extract the client name from
the URL and perhaps a little ex
On Thu, Jul 10, 2008 at 6:10 PM, <[EMAIL PROTECTED]> wrote:
> Is there a routing class in tapestry that can be manipulated? like routs.rb
> in RoR? Which would allow me to manipulate the URL->tapestry bindings?
Not at all. You have other paths to reach the same (maybe similar) goal.
--
Massim
On Thu, Jul 10, 2008 at 3:33 PM, Ryan.Bergman <[EMAIL PROTECTED]> wrote:
>
> Greetings,
>
> I am new to tapestry and I have a few questions about what is and is
> not possible within the Tapestry framework. Im helping to spearhead a new
> project for my company to determine the feasability and
ng.
Ryan
--
View this message in context:
http://www.nabble.com/Routing-and-REST-tp18382935p18382935.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
10 matches
Mail list logo
