Tapestry ignores static fields when performing instrumentation. I often use
static final fields. If you make them public, you can access them from the
template as if they were a property.
On Wed, Jan 9, 2013 at 11:34 PM, bhorvat wrote:
> Is there any reason not to use static final something in
Is there any reason not to use static final something in the page classes?
I want to introduce some const field that is only needed in the page class
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Reason-not-to-use-static-final-tp5719227.html
Sent from the Tapestry - Us
Just as a hint, are you familiar with contributeFactoryDefaults vs.
contributeApplicationDefaults?I believe the way to do this is to have one
symbol per module and chain it somehow.I realize I am vague here but I don't
have a clear solution for you.Muhammad Gelbana wrote:> I have multiple
modu
Any ideas in which version will this be included?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry5-JQuery-mixin-jScrollPane-tp5719224.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
I have multiple modules overriding the home page application-defaults
value. Some modules "override" that value but there is a case when the
module that overrides the home page value, is the only module loaded so
"overriding" the value throws an exception and the application fails to
start, because
Simple answer to both of your questions - yes.
Saying that, There are some things that can be handled better out of the box,
Which are actually fixed in the FlowLogix library
http://code.google.com/p/flowlogix/wiki/TapestryLibrary
On Jan 8, 2013, at 3:38 PM, sthomps wrote:
> I'm currently eva
Hello,
I couldn't make it work. Does anyone use this?
There's something wrong with the javascript function "one". I had to comment
it and call "tapestryFieldEventManager" directly.
Also, when I submit the form, these ajax-validated fields are not validated.
Tapestry only validates the built in v
I'm currently evaluating component based frameworks, as we are currently
using Wicket, and one of the problems we encounter is Ajax interactions
after the http session has expired.
If a user clicks on a component that is Ajax enabled - the framework throws
a PageExpiration exception.
For most app
