aven't been
> following this conversation very closely, so, if I'm missing
> something, fill me in).
>
> Robert
>
--
View this message in context:
http://n2.nabble.com/-T5--Struggling-With-Concepts-tp2324920p2348257.html
Sent from the Tapestry Users mailing list arch
n), and thats
it.
component A (shared)
/ \
page 1 (@parameter site = A) page 2 (@parameter site=B)
cheers,
Peter
--
View this message in context:
http://n2.nabble.com/-T5--Struggling-With-Concepts-tp2324920p2348095.html
Sent fro
whose value
corresponds with the containing page (your site /sub-section), and
thats
it.
component A (shared)
/ \
page 1 (@parameter site = A) page 2 (@parameter site=B)
cheers,
Peter
--
View this message in conte
thats
> it.
>
> component A (shared)
> / \
> page 1 (@parameter site = A) page 2 (@parameter site=B)
>
> cheers,
> Peter
>
--
View this message in context:
http://n2.nabble.com/-T5--Struggling-With-Conce
component A (shared)
/ \
page 1 (@parameter site = A) page 2 (@parameter site=B)
cheers,
Peter
- Original Message -
From: "xfile80303"
To: users@tapestry.apache.org
Sent: Wednesday, 18 February, 2009 02:35:03 GMT +02:00 Athens, Beirut,
Bucharest, Istanbul
Subject: Re
you taking the time.
--
View this message in context:
http://n2.nabble.com/-T5--Struggling-With-Concepts-tp2324920p2344202.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
-
To unsubscribe, e-
Ok, here is an example.. hope it's legible. :) The meat of the code is
the ContextFilterRequest below. If you create a normal J2EE filter that
determines what part of the path to rip out, then if can do:
doFilter(...) {
String path = getCleanPath( request ); // helper method
boolean hasV
Em Tue, 17 Feb 2009 13:47:16 -0300, xfile80303 escreveu:
I know this was sort of a "tongue-in-cheek" comment, but how can I use
Tapestry to solve this dilemma?
Not very much tongue-in-cheek, I guess. A Tapestry Dispatcher is the
analogous to a servlet, and a Tapestry RequestFilter is analog
Levi
--
View this message in context:
http://n2.nabble.com/-T5--Struggling-With-Concepts-tp2324920p2341894.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry
Tapestry and Apache HiveMind
>
--
View this message in context:
http://n2.nabble.com/-T5--Struggling-With-Concepts-tp2324920p2341876.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
-
To unsu
its a good idea to use a convention for a home page for each
> virtual site. (i.e.: /home) That way in your request filter you can
> redirect without having to think about building links or doing page
> lookups, just build up a URL: /site/home.
>
> Cheers,
> Peter
>
>
>
be:
>>
>> http://mysite.com/blah/blah/blah?site=foosite
>>
>> or
>>
>> http://mysite.com/blah/blah/blah/foosite
>>
>> if that makes achieving this with Tapestry any easier.
>>
>> I feel that Tapestry has the potential to be very useful and a great
>> platform to develop
request filter you can redirect
without having to think about building links or doing page lookups, just build
up a URL: /site/home.
Cheers,
Peter
- Original Message -
From: "Howard Lewis Ship"
To: "Tapestry users"
Sent: Sunday, 15 February, 2009 21:20:46 GMT +02:0
Why would you use other filters or servlets when you have Tapestry? :-)
On Sun, Feb 15, 2009 at 11:13 AM, Fernando Padilla wrote:
> Fair, but then the knowledge of "virtual host" would only be within
> tapestry, and not be usable for any other filters, servlets, etc etc.. just
> get to pick your
Fair, but then the knowledge of "virtual host" would only be within
tapestry, and not be usable for any other filters, servlets, etc etc..
just get to pick your poison :)
Howard Lewis Ship wrote:
Acutally, there's no real reason Tapestry 5.1 can't support this
scheme, once we make a few more
Acutally, there's no real reason Tapestry 5.1 can't support this
scheme, once we make a few more of the Link-generating and
Request-path-parsing services public and overridable.
On Sat, Feb 14, 2009 at 6:48 PM, Fernando Padilla wrote:
> I'm sorry, but this is not quite what Tapestry is meant to s
I'm sorry, but this is not quite what Tapestry is meant to solve for..
It solves nicely for state within a page.. or within a user's session,
etc etc.
Since what you're trying to do is have your code support a form of
"virtual hosting", it might be easier if you deal with it using normal
J2EE
> Specifically, I am trying to create an application which will be "site
> aware" (where "site" is a made-up term which implies different
> configurations/access/etc.). The "site" will need to be present in the URL
> in some form.
I don't know how many sites you are offering, but have you thoug
te
>
> or
>
> http://mysite.com/blah/blah/blah/foosite
>
> if that makes achieving this with Tapestry any easier.
>
> I feel that Tapestry has the potential to be very useful and a great
> platform to develop on, but I'm really struggling to understand how to do
> this
ad:
http://n2.nabble.com/-T5--URL-Manipulation-tt2276010.html
--
View this message in context:
http://n2.nabble.com/-T5--Struggling-With-Concepts-tp2324920p2324920.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
-
20 matches
Mail list logo
