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
there are lots of weird customizations we have to do, and we serve up a
semi-unique application per sports team ( all from the single webapp ).
So in one way or another, I bet we employ the techniques you would
want to employ.
- not sure what you mean by multiple clients but:
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.
- as for the JSON casting, you're saying that any url would have a
normal html representation and a json representation, but how different
are they?
1) You can easily create a Tapestry Dispatcher that matches and handles
any url ending with "/JSON/". You can implement all json as unique
services that the primary dispatcher would call depending on the
incoming url ( you could configure it using some sort of map)..
Or you can even copy what the PageDispatcher does and render another
unique page (maybe /json/PAGENAME), if you want to use tapestry pages to
generate the json. This page could then return a JSON object back to
the dispatcher somehow ( maybe setting a request attribute ), which the
dispatcher can pickup and spit out to the client...
Ryan.Bergman 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 cost of a new
platform for our product. Tapestry seems like a perfect fit for the UI level
but a couple of things are holding me back from serving up the Kool-Aid :).
I'm not looking for technical handouts, just an assurance that tapestry will
not bind me and maybe a point in the right direction.
Our product runs as a SAAS but maintains the ability to "feel" different
for different clients and so serves as a portal. We also need to keep costs
down on things like SSL certs domain names. You can think of each client as
being in a Silo. So the URL standard embeds the "silo" name as the first
directory in the path:
http://www.SaaS.com/<ClientsName>/TapestryStartsHere.html
It's not apparent to me that tapestry will allow me to do this within it.
I might be able to do it with a Apache mod but I would rather not do that.
THe <ClientName> would need to exist for every request and would tie into
just about everything.
The other piece I need that's somewhat related is that I want to be able
to expose RESTful web services as part of the same system. So while right
now I can go to:
http://www.SaaS.com/<ClientsName>/CreateUser/
to get a user form I also want
http://www.SaaS.com/<ClientsName>/CreateUser/JSON/
to access the same service as a REST web service using JSON or XML or just
GET and POST params. Would this just require some custom components? and can
I access and manipulate HTTP state and return codes from within Tapestry?
Thats it! Thank you all so much for your time I really like tapestry so far
and would love to put my mind at ease and get to coding.
Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
