RE: Re: From the online docs
Actually I think you were referring to servlet Tapestry rather than portlet. And for servlets, you are correct. Tapestry 3 did not, however, support portlets (at least not directly). And for the portlets one doesn't actually specify page names, rather they are implicit. The sub-folder idea does sound promising. I'll see if I can take that approach. Anyone got Tapestry working to host multiple *portlets* in a single war file? Thanks, Ezra Epstein -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of hv @ Fashion Content Sent: Monday, July 10, 2006 5:29 PM To: users@tapestry.apache.org Subject: Re: From the online docs While I have never needed more than one Tapestry app per .war, I have seen documentation covering much of what you would need in the old manuals for version 3. In web.xml you define multiple servlets. The .application is named after the servlet and lists the .page files. So if you put the .page files in separate sub directories you can get it nicely separated. I don't think it is terribly difficult. Henrik "Epstein, Ezra" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] Do you have a working example that provides multiple portlets from a single .war? Thanks, Ezra Epstein -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, July 08, 2006 8:41 AM To: Tapestry users Subject: Re: From the online docs Why does this imply one portlet per war?? There is clearly no such limitation. See http://tapestry.apache.org/tapestry4/tapestry-portlet/configuration.html for more... >From "Epstein, Ezra" <[EMAIL PROTECTED]>: > From http://tapestry.apache.org/tapestry4/tapestry-portlet/index.html > > "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. > " > > So if that's true it does indeed imply one portlet per war. This > makes Tapestry a non-starter for us. > > Can someone confirm or deny this limitation? > > Thanks, > > Ezra Epstein > > > -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: From the online docs
While I have never needed more than one Tapestry app per .war, I have seen documentation covering much of what you would need in the old manuals for version 3. In web.xml you define multiple servlets. The .application is named after the servlet and lists the .page files. So if you put the .page files in separate sub directories you can get it nicely separated. I don't think it is terribly difficult. Henrik "Epstein, Ezra" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] Do you have a working example that provides multiple portlets from a single .war? Thanks, Ezra Epstein -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, July 08, 2006 8:41 AM To: Tapestry users Subject: Re: From the online docs Why does this imply one portlet per war?? There is clearly no such limitation. See http://tapestry.apache.org/tapestry4/tapestry-portlet/configuration.html for more... >From "Epstein, Ezra" <[EMAIL PROTECTED]>: > From http://tapestry.apache.org/tapestry4/tapestry-portlet/index.html > > "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. > " > > So if that's true it does indeed imply one portlet per war. This > makes Tapestry a non-starter for us. > > Can someone confirm or deny this limitation? > > Thanks, > > Ezra Epstein > > > -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: From the online docs
Do you have a working example that provides multiple portlets from a single .war? Thanks, Ezra Epstein -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, July 08, 2006 8:41 AM To: Tapestry users Subject: Re: From the online docs Why does this imply one portlet per war?? There is clearly no such limitation. See http://tapestry.apache.org/tapestry4/tapestry-portlet/configuration.html for more... >From "Epstein, Ezra" <[EMAIL PROTECTED]>: > From http://tapestry.apache.org/tapestry4/tapestry-portlet/index.html > > "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. " > > So if that's true it does indeed imply one portlet per war. This > makes Tapestry a non-starter for us. > > Can someone confirm or deny this limitation? > > Thanks, > > Ezra Epstein > > > -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: From the online docs
Why does this imply one portlet per war?? There is clearly no such limitation. See http://tapestry.apache.org/tapestry4/tapestry-portlet/configuration.html for more... >From "Epstein, Ezra" <[EMAIL PROTECTED]>: > From http://tapestry.apache.org/tapestry4/tapestry-portlet/index.html > > "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. " > > So if that's true it does indeed imply one portlet per war. This makes > Tapestry a non-starter for us. > > Can someone confirm or deny this limitation? > > Thanks, > > Ezra Epstein > > > -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
From the online docs
>From http://tapestry.apache.org/tapestry4/tapestry-portlet/index.html "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. " So if that's true it does indeed imply one portlet per war. This makes Tapestry a non-starter for us. Can someone confirm or deny this limitation? Thanks, Ezra Epstein
