Tapestry can forward to a JSP or HTML to render a response, instead of rendering a Tapestry page.
With difficulty, you can have a servlet generate a URL to a Tapestry service. It should be possible to create a JSP tag that simplifies this. Tapestry was always positioned as an alternative to JSPs, not a companion. I've never made any effort to make it "compatible". There's been some talk of trying to "graft" Tapestry components into a JSP, or allow a JSP to be a Tapestry page somehow. I could figure out some kind of kludge if I could work on it full time for a bit. We'll see if that happens at WebCT, since the current WebCT application is Struts. -- [EMAIL PROTECTED] http://tapestry.sf.net > >> What new features for Tapestry are necessary to > >implement in order to > >> get a broader acceptation? > > > >I would like to see: > >- More contributed components (especially now that 2.2 > >is stable and we have libraries) > >- More documentation (I'm working on The Book, but > >there's also the Tutorial) > >- More success stories > > - J2EE integration. AFAIK Tapestry is a world of its own: You > cannot make use of already existing servlets from a Tapestry > application, and you cannot integrate Tapestry components into > a servlet. > > That's at least my impression from the documentation. Please > correct my if I am wrong! > > Best regards > Rainer Klute > > Rainer Klute IT-Consulting GmbH > Dipl.-Inform. > Rainer Klute E-Mail: [EMAIL PROTECTED] > Körner Grund 24 Telefon: +49 172 2324824 > D-44143 Dortmund Telefax: +49 231 5349423 > ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
