Are you using T5.3?
Have you tried moving tracker.recordError(…) from setupRender() to
onUploadException(…)? I don’t think there’s any need to do your own persisting
of the error message (because Tapestry will persist the Form through the
redirect because it has an error).
Unless I’ve missed
I'm trying to use a onUploadException event listener to catch failed uploads
and report the error as a validation error after the page reloads. I have
access to the error when the page reloads, but I don't know how to report the
error as it is not clear how to report an error to the validation t
Property need to be private to be resolved in the .tml
I use to add @SuppressWarnings("unused") when needed. I like to have no
analysis error or warnings. I wish that for my TML files too, but
xmlns:p="tapestry:parameter" is not understood. after also
gives me analysis error. I hope JetBrain
On Mon, 24 Aug 2015 21:19:25 -0300, yazmin georgina quintal
wrote:
I Know tapestry weave my page.java, I think that by some reason the
weaving is replacing variable resultados with a cached value and using
it in place of the returned value from JDO,
Tapestry does change the bytecode of p
There have been some improvements in the recent v15 EAPs.
Also you can adjust the unused inspection to not trigger on certain
annotations. (I think it is some sub-menu found under the "light bulb" when
having an unused field marked)
On Tue, Aug 25, 2015 at 2:29 PM, Poggenpohl, Daniel <
daniel.pog
Hello again,
right after solving after another problem, I thought that maybe you could help
me with another one regarding IntelliJ and Tapestry.
The IDE has Tapestry support, but it seems to use a rather old Tapestry version
(5.1?).
The code inspections seem to be relatively dumb because @Prope
Hi,
Using production mode = false helped solve the problem with properties having
"null" values.
The tapestry execution mode has to wait for now until we need different modes.
Thanks for helping.
Regards,
Daniel P.
-Ursprüngliche Nachricht-
Von: Poggenpohl, Daniel
Gesendet: Dienstag,
We usually simply set -Dtapestry.production-mode=false in the JVM when we
want dev mode.
On Tue, Aug 25, 2015 at 1:51 PM, Poggenpohl, Daniel <
daniel.poggenp...@isst.fraunhofer.de> wrote:
> Hi everyone,
>
> it seems that production mode (is set to true) is the problem.
>
> We use build profiles a
Hi everyone,
it seems that production mode (is set to true) is the problem.
We use build profiles and have three stages:
1. Local development
2. Deploying to a Test VM for load tests
3. Deploying to the official VM
Our tapestry module POM reflects this.
When I add a property
development
It is very good! Also for multi-module development and JavaScript debugging.
S-E
From: Charlouze [via Apache Tapestry Mailing List Archives]
[mailto:ml-node+s1045711n5731127...@n5.nabble.com]
Sent: 25. august 2015 13:43
To: Svein-Erik Løken
Subject: Re: Debugging Tapestry with IntelliJ IDEA
+1
+1 (non-binding :D)
Le mar. 25 août 2015 à 13:25, Stephen Nutbrown a
écrit :
> Just to confirm it also works fine here too. I've found IntelliJ to be
> absolutely fantastic so far. I'm running it using jetty but I know there is
> an option for tomcat... I don't know if that could make a differen
Just to confirm it also works fine here too. I've found IntelliJ to be
absolutely fantastic so far. I'm running it using jetty but I know there is
an option for tomcat... I don't know if that could make a difference?
On 25 Aug 2015 11:33 am, "Chris Poulsen" wrote:
> It works fine with IDEA here.
It works fine with IDEA here. A possibility could be that you are running
in production mode?
On Tue, Aug 25, 2015 at 12:04 PM, Poggenpohl, Daniel <
daniel.poggenp...@isst.fraunhofer.de> wrote:
> Hello everyone,
>
> we are evaluating IntelliJ IDEA for development and so far it has been
> quite go
Hello everyone,
we are evaluating IntelliJ IDEA for development and so far it has been quite
good.
But the Tapestry specifics seem to hinder further evaluation.
Does anyone here use IntelliJ for development?
When we debug code, page properties are always seen as having a "null" value
instead of
14 matches
Mail list logo