Hi,
Is there any way in tapestry 5.4 (*production mode) *where-in, I can fire
the tapestry compiling chain again ( so that my less file are compiled
again).
I am able to get this done in *development *mode, by adding a request
filter(which picks my dynamic changes on the file), by adding my
RequestHandler in AppModule class:-
public void contributeRequestHandler(
OrderedConfiguration<RequestFilter> configuration) {
configuration.addInstance("XYZRequestFilter",
XYZRequestFilter.class, "before:*");
But the same approach, doesn't work in production mode( since the caching
mechanism is different).
Any idea/suggestions would be of great help.
Regards,
Akshay
Is there any way in tapestry 5.4 (*production mode) *where-in, I can fire
the tapestry compiling chain again ( so that my less file are compiled
again).
I am able to get this done in *development *mode, by adding a request
filter(which picks my dynamic changes on the file), by adding my
RequestHandler in AppModule class:-
public void contributeRequestHandler(
OrderedConfiguration<RequestFilter> configuration) {
configuration.addInstance("XYZRequestFilter",
XYZRequestFilter.class, "before:*");
But the same approach, doesn't work in production mode( since the caching
mechanism is different).
Any idea/suggestions would be of great help.
Regards,
Akshay