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 code in general.
So it's a matter of our code checking what team it's currently handling
and rendering based on that. For us most of the functionality is the
same except what labels we print up, or what team we associate new
records, etc etc. So not too bad.
The filter to change the Servlet Context Path isn't too big, if someone
is thinking of changing the app's context path as we are..
any other questions?
Harald Geritzer wrote:
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 sounds very interesting as i have similar needs. in the background,
do you have one tapestry
app at all or one for each sports team?
would you share some more information on how you are doing it?
thanks
harald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
