Hi All;
I am new in tapestry and trying to write my first application, I am
utilizing httpclient in my application so that I can http request to
other with xml content, all works okay in my localhost, but after
deploying it to development server I am getting the below error:
"An unexpected
Thanks a lot Thiago H de Paula Figueiredo. It worked for me :-)
Regards,
Mahendra
-Original Message-
From: Thiago H de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: Thursday, June 20, 2013 2:32 AM
To: Tapestry users
Subject: Re: default focus issue in tml page
On Wed, 19 Jun 2013
Yes, that's exactly why I created the LazyTreeModel.
The DefaultTreeModel works best when the entire model is loaded into memory
and the model is stored between requests (in the session or as a
singleton). The first time a node is expanded, it must be found by
traversing from the root which has co
I will try it out, however my current implementation works for me. I guess
what I like about using encoder is that it allows me to easily override
findById (since it is using encoders) and then I can prevent loading of the
nodes that cant possible be the one a user clicked...
Cheer
On Wed, Jun 1
FYI I've just added a database backed demo of the LazyTreeModel to
tapestry-stitch
http://tapestry-stitch.uklance.cloudbees.net/lazytreedemo
Note: The documentation is lacking, the demo is ugly and the sample data is
very sparse... the code could probably do with a refactor too!!
I'll tidy it up w
On Wed, 19 Jun 2013 08:56:57 -0300, Athneria, Mahendra
wrote:
Hi,
Hi!
Have you tried using autofocus="false" in the Form component?
I am facing weird issue on my tapestry page.
On page I have three fields.
1st - select box -> tabindex is 1 and t:validate="required"
2nd - textfield ->
Hi,
I am facing weird issue on my tapestry page.
On page I have three fields.
1st - select box -> tabindex is 1 and t:validate="required"
2nd - textfield -> tabindex is 2 and t:validate="required"
3rd - textfield -> tabindex is 3 and t:validate="required"
When my page gets load default focus is
There is the ParallelExecutor which is backed by a thread pool. Be warned,
the pool size is 3 by default (configurable via a symbol). The
ParallelExecutor will invoke PerThreadManager.cleanup() once your Runnable
completes to clean up the hibernate session and any PerThreadValue
instances.
On Wed, Jun 19, 2013 at 12:04 AM, Rural Hunter wrote:
> yes, that's what I thought of. But I would like to see if there is any
> other option in Tapestry.
>
There's a tool for each use case. I can not imagine a much better tool for
this case than a simple thread if the thread's lifetime is the sa
yes, that's what I thought of. But I would like to see if there is any
other option in Tapestry.
δΊ 2013/6/19 14:53, Kalle Korhonen ει:
Create a thread?
Kalle
On Tue, Jun 18, 2013 at 11:42 PM, Rural Hunter wrote:
Hi,
Is there a "best practice" to implement continuously/long-run background
10 matches
Mail list logo