Further digging finds that if StackA includes ResourceA and PageB or any
of its components import ResourceA then StackA will be included.
org.apache.tapestry5.internal.services.ajax.JavaScriptSupportImpl.importJavaScriptLibrary(String)
line 240
I haven't played around with stacks to this degree before however I find
this alarming and am going to have to abandon my usage of stacks because
of this.
I am assuming there is no configuration switch to disable the
auto-inclusion of stacks unless specifically imported?
thanks, p.
On 19/11/2014 3:25 PM, Paul Stanton wrote:
Hi,
I have PageA for which I have created StackA of all the the js it
includes by the virtue of its self and its components (for production
efficiency).
I have PageB for which I have not created a stack, and it does not
import StackA.
However when I request PageB, StackA is being included and as a result
I have scripting errors.
Why?
It is likely that StackA and PageB share some assets however that
shouldn't be a reason to include the whole of StackA!
Thanks, p.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
