You don't even need the div - just set the style attribute directly
on the input tag itself.
We too have been using this approach instead of hidden fields for
storing internal data.
- Navin
On 17-Jan-07, at 6:35 PM, Mika Tammilehto wrote:
Well, I found a workaround - in case somebody else
A Tapestry-Spring-Hibernate stack is good - although it may take some
time to get it right (depending on the complexity of your app).
We use this stack in our project and one of the prime factors for
including Spring here is its convenient transaction-management
support. It gets much better
Hi Firas,
I think, what Karthik meant by point 2 is something like below:
Here you can see that the content of the block has a binding to a
property "testValue". So, which page will this binding be pointing to?
- Navin
On 09-Nov-06, at 2:32 PM, Firas Adiler wrote:
Hi Karthik,
Hi,
I am adding a custom enhancement worker to my application, which
enhances the PropertySelection to intialize a default model.
As part of this, I needed to get a reference to the
OGNLBindingFactory service (from HiveMind), so that I can create an
OGNL binding. The normal approach to th
Hi Ken,
You can use a base class. Just make your base class extend BasePage.
In my project too, we use a custom base class, which does exactly
what you described - abstract common code out. Using such a class,
also helps when you may need to add some hooks into your processing
(as many cal
In your case, you want a method to be called after Tapestry calls
setDay(), setYear() and setMonth() during rewind.
You can do it in the cleanupAfterRender() method (As Daniel
suggested), or you can use the http://tapestry.apache.org/tapestry4/
tapestry/ComponentReference/InvokeListener.html
Hi Matt,
You can use templates for components too (similar to page templates),
by extending the component class from "BaseComponent". Then you just
add an HTML with the same name as the component and that's all.
And you can use the "InvokeListener" component part of the core
Tapestry fram
'll poke Howard real quick about it too, sounds like a
delicate area
to mess with ;) )
On 9/28/06, B.S.Navin <[EMAIL PROTECTED]> wrote:
Hi,
I was going through the Persistence mechanism implementations in
Tapestry 4.0.2 and came across the following behaviour:
-
Hi,
I was going through the Persistence mechanism implementations in
Tapestry 4.0.2 and came across the following behaviour:
--
For properties marked as @Persist("session"), the mutator(setter)
stores the value in a instance variable and also puts it into session
using
