Hai Geoff thanks a lot for trying :)
I try to explain it better. Basically I have a survey object, that contains
survey info and list of section object. The section object contains section
info and list of question object. What we want to do is give the user the
ability to fill the survey info, se
Sorry, I tried to draw a model of your page but I don't quite get it.
The techniques used in that JumpStart page's components may have a problem when
they're nested deeper. They're done better in the JumpStart preview for T5.4:
http://jumpstart.doublenegative.com.au/jumpstart7/together/
I think David may need to start from scratch...
First, render a page with no errors. The template can include a zone. Notice
that the zone is rendered too. It defines an area that the server can now
refresh - but only in response to an AJAX request.
You can set up the fields on before you rende
IMHO, you should not try to put logging config in your app. Logging is
something you'll want to configure differently in each environment (UAT, prod,
your dev, your mate's dev, etc) without changing the app.
So, since you mentioned you want to run in JBoss 7 (but you didn't mention
which one -
On Wed, 26 Mar 2014 10:44:05 -0300, Davide Vecchi wrote:
Anyway, maybe you should rethink the way you handle your exceptions.
Shouldn't they be treated inside the getter methods themselves?
I'm very confused about this suggestion. Am I not doing exactly that ? I
mean, treating the exception
As hinted earlier, our first T5.4 compatible module, tapestry-security is
released. This release is primarily for compatibility, although I threw in
one, non-backwards compatible enhancements for optimized rememberMe cookies
because I felt it was the right time. The source has moved to
Github
Or maybe someone has an example of a single page site made with tapestry.
I've tried jumpstart
http://jumpstart.doublenegative.com.au/jumpstart/together/ajaxcomponentscrud/personsit's
something similar but able to be nested 3-4 component deep.
Thanks for any clue.
Cheers.
On Tue, Mar 25, 2014 a
Thanks for the pointers about onException and @Cached, I didn't know either.
@Cached would allow me to avoid wrapping the getter body in an "if
(this.myValue == null)".
onException would help my case only if it was possible to update a zone from
that method even if the exception that triggered
On Wed, 26 Mar 2014 10:05:21 -0300, Vasili Petrenko
wrote:
Hi.
thank you. What I should do to control logging log4j in tapestry app.
The same as you would in a non-Tapestry application, hence the
off-topicness of your question.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hiberna
Hi.
thank you. What I should do to control logging log4j in tapestry app. I only
put log4j.properties file in resource folder and have no effect.
Must I do more?
-Ursprüngliche Nachricht-
Von: Thiago H de Paula Figueiredo [mailto:thiag...@gmail.com]
Gesendet: Mittwoch, 26. März 2014 12:
On Wed, 26 Mar 2014 08:25:40 -0300, Davide Vecchi wrote:
1) I have a getter that might cause an error.
2) This getter gets called for the first time by Tapestry, during page
rendering (because its value must already appear in the page, before any
possible user action).
3) If this getter
On Wed, 26 Mar 2014 07:59:58 -0300, Vasili Petrenko
wrote:
Hi.
Hi!
I'm using Tapestry 5.3.7 with JBOSS 7 application server. My log4j
configuration don*t work.
I'm sorry, but this question is related to log4j, not Tapestry, so it's
off-topic and shouldn't have been posted here. And yo
Nope, it looks like none of the methods executed during the Rendering Phases or
the Page Life Cycle can update a zone. Which makes sense considering what I
have been explained here about updating zones.
Considering that, I realized that my kind of problem is not that much about
zones. I would h
Hi.
I'm using Tapestry 5.3.7 with JBOSS 7 application server. My log4j
configuration don*t work.
I put the log4j.properties file to resource folder: src/main/resources
My file:
log4j.rootCategory=warn, A1
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=
Hi, thanks for the clarifications.
> If these values are used in the initial page rendering, as it's the case here,
> you don't need to @Persist them at all. The values of the fields will be kept
> until the request is finished.
(Just a detail) I was thinking @Persist because if I had to calculat
Could any of Tapestry developers roughly estimate the release date of
Tapestry 5.4 ? Something like this week, this month, in few months
Anything ?
*-*
*Muhammad Gelbana*
http://www.linkedin.com/in/mgelbana
16 matches
Mail list logo