Hi,
 
during browsing the tapestry-page i often come over 1 point: portlet support
 
on the tapestry page its even a major markup, but i dont see the benefits it
should bring... i mean with tapestry everything is just a component... so
why do we need portlets? - as far as i understood, a portlet just needs a
portlet server in wich we have a config and some portlets plugged
together... meaning it comes similar to lets say, 1 main layout and some
components plugged in togehter without the needed portlet server... 
 
would anyone please be so kind and tell me what the benefits from portlets
should be ? 

- and why it is important thet the page lists " The pattern of development
for Tapestry portlet applications is to create a (generally) small
application, consisting of just a few pages. Each Tapestry portlet within a
portal page will be a completely separate instance of not just the portlet,
but all the Tapestry services behind it. "  - where is the point of having
components/ portlets not talking to each other???

Regards,

Korbinian


 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to