://tapestry-users.832.n2.nabble.com/How-to-get-RESTful-hierarchical-URLs-tp4606241p5520575.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For
well you dont create new, view, delete, edit pages rather get, delete, post
and put method for customer service
pozdrawiam
Paweł Kamiński
kami...@gmail.com
pkaminski@gmail.com
__
My reading of REST is that it is about actions (GET, POST, PUT, DELETE, etc) on
resources, not the requesting of pages that invoke those actions. So the
question becomes what are appropriate URLs for *pages* that can invoke the
actions of create, view, edit, view, search, etc.?
I like the aim
On Sun, 21 Feb 2010 18:24:52 -0300, Alexander Kiel
wrote:
Hi Thiago,
Hi!
So is Tapestry SOA and can't speak REST?
Tapestry can speak rest: just use Tapestry's URL rewriting. It can be
improved, of course, but that's something built to care to the kind of
scenario you have.
--
Thia
Hi Thiago,
thanks, I know this. The block switching is only a bit better
if-then-else. Imagine, that I like to have more than one area customized
for the teams/team case. There, I will end up with multiple block
switchings.
And my page still has two times as much components plus the switchings
as
On Sun, 21 Feb 2010 16:19:58 -0300, Alexander Kiel
wrote:
ok this is possible. But than I have at least one big if-then-else
statement in my page and that page has both components loaded, a grid
and a beandisplay (if we stay simple). If I use two separate pages, I
have no if-then-else nightma
Hi Hilico,
ok this is possible. But than I have at least one big if-then-else
statement in my page and that page has both components loaded, a grid
and a beandisplay (if we stay simple). If I use two separate pages, I
have no if-then-else nightmare and my pages are much lighter.
Additionally I w
On 21 February 2010 02:11, Alexander Kiel wrote:
> * /articles/ list all articles available
> * /articles/{a-id}/ show one article
> * /customers/ list all customers
> * /customers/{c-id}/ show one customer
> * /custom
Hi based2,
thanks for the http://old.nabble.com/URL-Rewrite-ts27505806.html link. I
did not see this post during my research. Looks like some alternative
maybe better URL rewriting engine for Tapestry.
I already read all the other documents, you pointed me to. I'm also
interested in some solution
xt, but I don't like to missuse well
> thought out architectures.
>
>
> Thanks for your help
> Alex
>
>
> [1]: <http://www.useit.com/alertbox/990321.html>
>
> --
> e-mail: alexanderk...@gmx.
Hi Tapestry users and devs,
this is my first question here and I use Tapestry for only three days
now, so excuse my question if there is already a documented answer.
Suppose, I want to implement an online store with Tapestry. I like to
have the following URLs:
* /articles/
11 matches
Mail list logo
