What if...
You take the JSP and morph it into a page specification using taglibs. The
tag would add a "JSP page" as a page in the application (if not already
there), and perhaps invoke the engine stuff that normally happens when a
page is invoked. You could then rewind the components on the page (if
required).
<tapestry:page name="HelloPage" specification-class="BaseJSPPage"/>
that way real Tapestry pages can say cycle.setPage("HelloPage") to forward
to a JSP. Behind the scenes Tapestry does a servlet-style forward to the
JSP.
then you could have another tag that performs a forward from a JSP to a real
Tapestry Page
<tapestry:forward page-name="Home"/>
Its been a long time since I wrote a taglib but I think it could be doable.
Geoff
Geoffrey Longman
Intelligent Works Inc.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer