On Thu, 18 Aug 2016 17:43:07 -0300, Juan M Garrido de Paz
<juanm.garrido....@gmail.com> wrote:
Hello...
Hi!
how do you organize the packages/folders in your projects? (I mean other
than pages, components, mixins, services).
Due to tapestry force us to have separate pakages for pages, components,
etc... I guess we cannot (or shouldn't) organize the whole root package
by "features" of business layer. For example, for "employee" feature, I
cannot
put a EmployeeGridDataSource in the page package with the pages of that
feature, because it is not a page.
That's correct. Tapestry applies bytecode transformation to pages,
components, mixins and classes in the 'base' packages, so it needs to know
exactly in what packages these classes are.
One thing you haven't thought is that you don't need to have a single root
package, so you can organize your sources, packages and classes by
feature. You just need to treat each one as a separate component library,
even if they're in the same project/source tree.
https://tapestry.apache.org/component-libraries.html tells you how.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
