Hi everyone, what i'm asking here is a Best pratice question.
I read the documentation about templates, components, .page .html etc... and I
actually don't understand why Tapestry is build like this.
Well, In big project, it's mandatory I think to have many folders to organise
pages. Well, with Tapestry, far as I know, it's hard to do it without
hardcoding some path somewhere.
You can put the reference for your components in the .application, but In big
project, it will quickly be hard to maintain.
My question is: Did I miss something or that nothing to do for that right now?
little example of structure I will like to have :
WEB-INF/
- gestionContacts/
-components(Related to gestionContacts, not app specific)
-component1/
-.jwc .html
-component2/
-.jwc .html
- contactCrud.page .html
- contactList.page .html
- etc...
- gestionPartenaires/
- login/
- help/
If I understand, I must register all the path to .application or call the
folder by specifing the correct path from the root context.
Anyway.. Thanks for any suggestion or link to show that I'm in error.
Carl Pelletier
