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
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
affec
Ah. Now I've read the javadoc :). Sorry for the RTFM issue...
Am 23.05.2015 um 19:05 schrieb Veit Guna:
> 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:
>
>
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 == developme
Hi,
Can you try adding this argument:
-Dtapestry.execution-mode=development
Thanks,
Steve
On 23 May 2015 at 16:58, Veit Guna 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 de
Make sure you've disabled production mode
On Saturday, May 23, 2015, Veit Guna 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 t
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
Which component are we talking about here? Are you sure you're setting id
(not to be confused with t:id, the serverside component id).
Inside a zone this id gets overridden by an automatically generated one.
On Thu, May 21, 2015 at 7:45 PM, Lance Java
wrote:
> If you're solving it by explicitly setting a data attribute, why can't you
> just explicitly set the id?
>
--
Ilya Obshadko
