Hi there
Tapestry 4 has native (!) JSR 168 support. If you hadn't had a look at
the spec, you better do, because I think all your requirements are
fullfilled there.
See e.g.
http://developers.sun.com/prodtech/portalserver/reference/techart/jsr168/.
Tapestry portlet pages are here:
http://jakarta.apache.org/tapestry/tapestry-portlet/index.html
Just for clarification (I hope I get it right):
There are portlet/portal containers which implement jsr 168, several of
them are opensource and seem to be quite up to it (e.g. liferay,
exoplatform, jboss portal , jetspeed2 ....).
And then there is IBM, Sun, Redhat, whatever with commercial solutions.
Those are containers (like tomcat is a servlet container) which
guarantee the correct execution of JSR 168 compliant portlets.
Since Tapestry 4 has native support for JSR168 (which basically means
that all tapestry portlets should run in all above mentioned
containers), you should be ready to go...
Please anyone correct me if I am wrong...
Cheers
cs.
Michael van Oers schrieb:
Hi,
I have been researching Tapestry for use in our project. We allow users
to design a website using buildingblocks we provide (like portlets).
We would like to use Tapestry for this project, but have a technical
problem...(I have not used Tapestry before).
We want to design our blocks as portlets (like the example for Tapestry
4 on the website) or as normal Tapestry components.
Each user will design his own page layout and decide which
components/portlets are displayed where on the page.
Now....
1) Can I do this with Tapestry?
I looked into using 'RenderBlock', but I don't want to include all
possible blocks at design time.
2) Should I use a portal component (like Jetspeed) if I design my
components as portlets, or can I use the portlets from within Tapestry
templates? (and decide which ones to use at runtime)
Any insight into this is greatly appreciated!
Cheers,
Edwin van der Elst
DISCLAIMER:
Dit bericht (met bijlagen) is met grote zorgvuldigheid samengesteld. Voor
mogelijke onjuistheid en/of onvolledigheid van de hierin verstrekte informatie
kan Kennisnet geen aansprakelijkheid aanvaarden, evenmin kunnen aan de inhoud
van dit bericht (met bijlagen) rechten worden ontleend. De inhoud van dit
bericht (met bijlagen) kan vertrouwelijke informatie bevatten en is uitsluitend
bestemd voor de geadresseerde van dit bericht. Indien u niet de beoogde
ontvanger van dit bericht bent, verzoekt Kennisnet u dit bericht te
verwijderen, eventuele bijlagen niet te openen en wijst Kennisnet u op de
onrechtmatigheid van het gebruiken, kopiëren of verspreiden van de inhoud van
dit bericht (met bijlagen).
This message (with attachments) is given in good faith. Kennisnet cannot assume
any responsibility for the accuracy or reliability of the information contained
in this message (with attachments), nor shall the information be construed as
constituting any obligation on the part of Kennisnet. The information contained
in this message (with attachments) may be confidential or privileged and is
only intended for the use of the named addressee. If you are not the intended
recipient, you are requested by Kennisnet to delete this message (with
attachments) without opening it and you are notified by Kennisnet that any
disclosure, copying or distribution of the information contained in this
message (with attachments) is strictly prohibited and unlawful.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
