Thanks for the detailed answer! Am 23.05.2015 um 22:35 schrieb Dmitry Gusev: > That's right, > > `tapestry.production-mode` is just a boolean value that may be used (and > usually do) in different tapestry modules to enable some optimizations for > production mode. It doesn't affect the list of modules that should be > loaded by your app. > > > The list of modules plugged during app start is defined by multiple > conditions (not a full list but close, RTFM): > > 1) Some modules plugged automatically when you put JARs with those modules > to classpath. > Tapestry scans manifests of all JARs in classpath to find modules > > 2) TapestryModule added by default via TapestryFilter > (TapestryAppInitializer that's referenced from filter to be more correct) > > 3) XXXModule added by default, where XXX is the name of the TapestryFilter > in web.xml, usually it's "app", hence AppModule > > 4) You may set value of `tapestry.execution-mode=YYY` (that's defaulted to > "production"). > Tapestry will use this value to get list of modules from servlet context > parameter with name `tapestry.YYY-modules` declared in web.xml -- you have > some predefined lists there when you create app from archetype, but you may > define as many as you want > > 5) Finally you may optionally specify system property `tapestry.modules` to > specify list of additional modules explicitly > > > Then modules may depend on another modules, this is defined via @SubModule > or @ImportModule (since 5.4) annotations declared on module's class. > Dependent modules also will be loaded. > > > > On Sat, May 23, 2015 at 8:11 PM, Stephen Nutbrown <steves...@gmail.com> > wrote: > >> Hi, >> >> I'm fairly new to Tapestry myself, so i'm sure Dmitry will correct me >> if i'm wrong. >> >> If you have no flags, it is set as production mode by default. The >> DevelopmentModule class is only used if you are in Development mode >> (which is set by that flag). So, changing things in that class won't >> affect anything unless you are in development mode. >> >> You also have an "AppModule" class, which I believe is for any mode. >> >> Please see the section titled "Setting Execution Modes": >> http://tapestry.apache.org/configuration.html >> >> "If the tapestry.execution-mode is not declared, Tapestry will >> automatically look for the tapestry.production-modules parameter, >> because “production” is the default tapestry.execution-mode value." >> >> Thanks, >> >> On 23 May 2015 at 18:05, Veit Guna <veit.g...@gmx.de> wrote: >>> Hi. >>> >>> That did the trick, thanks! >>> >>> But I'm wondering, why it wasn't enabled before. The archetype creates a >>> Class called DevelopmentModule. >>> In there one can find something like: >>> >>> configuration.add(SymbolConstants.PRODUCTION_MODE, false); >>> >>> So I pretended, that production is false == development mode is on :). >>> >>> But I'm glad it is working now. Thanks again! >>> >>> Regards, >>> Veit >>> >>> Am 23.05.2015 um 18:46 schrieb Stephen Nutbrown: >>>> Hi, >>>> >>>> Can you try adding this argument: >>>> >>>> -Dtapestry.execution-mode=development >>>> >>>> Thanks, >>>> Steve >>>> >>>> On 23 May 2015 at 16:58, Veit Guna <veit.g...@gmx.de> wrote: >>>>> Hi. >>>>> >>>>> I'm a new user of tapestry and struggling to get tml files reloaded >>>>> during development. >>>>> I'm using Tomcat 8 with JDK 7 and the tapestry archetype demo using >>>>> version 5.3.8. >>>>> >>>>> I've configured a tomcat server within Eclipse WTP and normally using >>>>> other web development >>>>> frameworks it's enough to save a file and it gets automatically >>>>> published to tomcat >>>>> without a redeployment. So it uses HCR unter the hood. Simply reloading >>>>> the page and >>>>> voila. That works with classes and resources (pages etc.). Tomcat is >>>>> started in Debug mode. >>>>> >>>>> With tapestry, the class reloading works, but not with the .tml files. >>>>> If I look at the >>>>> internal deployment location of WTP (under .metadata), I can see that >>>>> the resources >>>>> get replaced correctly by Eclipse. But tapestry doesn't pick them up. >>>>> >>>>> I've also tried -Dorg.apache.tapestry.disable-caching=true on container >>>>> start, but without >>>>> luck. >>>>> >>>>> I want to avoid deploying via maven, restarting tomcat or reloading the >>>>> context. >>>>> >>>>> Does anybody have a clue what I'm missing? >>>>> >>>>> Regards, >>>>> Veit >>>>> >>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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 >>>> >>> >>> --------------------------------------------------------------------- >>> 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 >> >> >
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
