Okay, so there is no way to make Tapestry aware of an entire module/subcontext and the location of its files? Only by hardcoding the relative path to the subdir in a link component or by specifying each page in the .application file to each module/subcontext? I'm mainly concerned about ease of maintenance...thanks for clarifying all this for me!
On 11/8/05, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > Yes, what he said. In our .application file we also reference the pages > thusly: > > <page name="Reporting" > specification-path="modules/reporting/Reporting.page"/> > > jesse > On 11/8/05, Andreas Andreou < [EMAIL PROTECTED]> wrote: > > In Tap4, if you have > > /WEB-INF/pages/admin/Login.html > > /WEB-INF/pages/admin/Login.page > > > > you can reference that page as "pages/admin/Login", i.e. > > <span jwcid="@PageLink" page="pages/admin/Login"/> > > > > Jason Suplizio wrote: > > > > >So, Jesse how did you do that? How were you able to configure Tapestry > to > > >look in your separate modules? > > > > > >Thanks! > > > > > > > > >On 11/8/05, Ron Piterman <[EMAIL PROTECTED]> wrote: > > > > > > > > >>ציטוט Jesse Kuhnert: > > >> > > >> > > >>>We've broken up all areas of our app into as many sub "module" and > > >>>component directories as we can, letting the .page/.html/.properties > > >>>files all live together. > > >>> > > >>> > > >>;-) We also did that but the .page files were not getting along with > the > > >>.html files taking their food and haressing their children, so we had > > >>to put them in different cages ;-) > > >> > > >> > > >> > > >> > > >>>Organization through directory structure has > > >>>been proven to be a sound approach so far, and we definitely have a > > >>>LOT of pages/components floating around. > > >>> > > >>> > > >>>On 11/7/05, Jason Suplizio <[EMAIL PROTECTED]> wrote: > > >>> > > >>> > > >>> > > >>>>Hi all, > > >>>>I've been combing the archives (and Kent's book) to see if its > possible > > >>>> > > >>>> > > >>to > > >> > > >> > > >>>>separate Tapestry files into separate directories. In short, I want > to > > >>>>configure my Tapestry app similar to: > > >>>> > > >>>>/WEB-INF/pages --> contains all the page files > > >>>>/WEB-INF/html --> contains all html files > > >>>> > > >>>>or even something like, > > >>>>/WEB-INF/templates --> containing both pages and html files > > >>>> > > >>>>I've seen an example of adding some configuration to the > > >>>><context>.application file: > > >>>><page name="Home" specification-path="/resources/Home.page"/> > > >>>> > > >>>>I'd like to do that for all the pages and html templates (not for > each > > >>>>file)), something like: > > >>>><pages name="*" specification-path="/pages" /> > > >>>><templates name="*.html" specification-path="/html" /> > > >>>> > > >>>>Is something (anything) like this possible? We're merely trying to > help > > >>>>organize our WEB-INF directory as this is an enormous enterprise app > and > > >>>>maintaining this is going to become unwieldy. > > >>>> > > >>>>Thanks! > > >>>>Jason > > >>>> > > >>>> > > >>>> > > >>>> > > >>>--------------------------------------------------------------------- > > >>>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] > > > > >
