I'm just beginning with Tapestry and referring to Tapestry 5, Building Web
Applications by Alexander Kolesnikov. But I'm using version 5.3.7.
I have a page with a property annotated with @Persist and a default value
of an enum.
t:radiogroup t:value=gender
input type=radio t:type=radio
I think that
private String gender = F;
is suspect, you should probably not initialize it to F, instead you can
use onActivate or setupRender to default it, if it is null.
--
Chris
On Thu, Oct 23, 2014 at 2:45 PM, Deepak mn.dee...@gmail.com wrote:
I'm just beginning with Tapestry and
t:radiogroup t:value=gender
input type=radio t:type=radio
t:value=literal:M / Male
input type=radio t:type=radio
t:value=literal:F/ Female
/t:radiogroup
@Property
@Persist
private String gender;
void onActivate() {
gender = F;
}
or
void onSetupRender() {
gender = F;
}
On Thu, Oct
On Thu, 23 Oct 2014 10:45:00 -0200, Deepak mn.dee...@gmail.com wrote:
@Property
@Persist
private String gender = F;
As Chris and George already said, never, never ever initialize a page,
component or field in its initialization. Their suggestion of using
setupRender() or onActivate() to
Great, that worked !!! As a general rule of thumb, does this mean that i
should initialize variables in these methods rather than during declaration
?
On Thu, Oct 23, 2014 at 6:54 PM, Chris Poulsen mailingl...@nesluop.dk
wrote:
I think that
private String gender = F;
is suspect, you should
Please ignore my 2nd question. I did not notice the rest of the
conversation in my inbox..sorry, my apologies.
On Thu, Oct 23, 2014 at 10:06 PM, Deepak mn.dee...@gmail.com wrote:
Great, that worked !!! As a general rule of thumb, does this mean that i
should initialize variables in these
I'm noticing that the exception raised by my tapestry application do not
appear as a stack track and not at all colored and highlighted as shown in
various posts and blogs. The exception is just displayed in a single
sentence paragraph. Am i missing any jar for the decoration ? The jars I've
used
On Thu, 23 Oct 2014 14:56:40 -0200, Deepak mn.dee...@gmail.com wrote:
I'm noticing that the exception raised by my tapestry application do not
appear as a stack track and not at all colored and highlighted as shown
in various posts and blogs. The exception is just displayed in a single
Hi, Thiago.
No, I've not created log4j.properties file but I've set the app to run in
development mode under web.xml as
context-param
param-nametapestry.execution-mode/param-name
param-valuedevelopment/param-value
/context-param
I've attached the screen shot of how exception is
On Thu, 23 Oct 2014 17:01:42 -0200, Deepak mn.dee...@gmail.com wrote:
Hi, Thiago.
Hi!
No, I've not created log4j.properties file but I've set the app to run
in development mode under web.xml as
context-param param-nametapestry.execution-mode/param-name
Thanks a lot for the pointer. With the setting of tapestry.production-mode
the stack trace is now displayed in its full glory :)
On Fri, Oct 24, 2014 at 1:02 AM, Thiago H de Paula Figueiredo
thiag...@gmail.com wrote:
On Thu, 23 Oct 2014 17:01:42 -0200, Deepak mn.dee...@gmail.com wrote:
Hi,
This might help you further.
http://jumpstart.doublenegative.com.au/jumpstart7/examples/infrastructure/exceptionreport
Cheers,
Geoff
On 24 Oct 2014, at 2:30 pm, Deepak mn.dee...@gmail.com wrote:
Thanks a lot for the pointer. With the setting of tapestry.production-mode
the stack
12 matches
Mail list logo
