On Wed, 19 Nov 2014 07:57:19 -0200, Geoff Callender
<geoff.callender.jumpst...@gmail.com> wrote:
I've never seen this but I probably don't have any stacks that include a
resource that I also reference outside of the stack.
If it's true then it sounds like a bug.
I'm not sure it is. I guess the reasoning behind this is to not have the
user browser download and process the same asset being downloaded from two
or more different URLs: one for the asset itself, plus another for each
stack in which the asset is included. If there wasn't this behavior and,
for example, a component imports one .js file directly and a page using it
includes a stack which includes this .js, it would be downloaded and
executed twice, probably causing bugs.
This way, I believe we should consider each stack as an unit in which its
components don't work unless the other ones are included too. If a given
file is used in one stack but can also be referenced directly or in
another stack, the stack(s) should be refactored.
--
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
