Hi Koka,
Yes, we use it for every request. The application is not even reachable
over port 80. :-)
It seems we found the problem though. It looks like it was caused by
overriding getLocale() in our page base class, although I'm not sure the
problem is 100% gone now, and I don't fully
Hi,
I had the following:
@Property
@Parameter(value=actionZone)
private String actionZone;
which caused the exception at [2]. I would not expect this behaviour
based on the documentation at [1] and am wondering if I should file a
bug report. The situation probably won't happen a lot and in all
I'd like to announce the latest release of the Tapestry Testify project at
Tapestry 360:
http://tapestry.formos.com/nightly/tapestry-testify/
Tapestry Testify is an extension to Tapestry that allows you to write page
and component tests very easily and have them run very efficiently.
**
On Sat, 05 Feb 2011 10:32:49 -0200, Joost Schouten (mailing lists)
joost...@jsportal.com wrote:
Hi,
Hi!
@Property
@Parameter(value=actionZone)
private String actionZone;
which caused the exception at [2]. I would not expect this behaviour
based on the documentation at [1] and am
no, what I 'm trying to point out is that because tapestry is using the same
name as html5..., then validation is not being consistent...
because if the browser does not support html5.., then tapestry will put up
and show the validation error with it's style.
but, if the browser does support
Explain again how it is that Tapestry is outputting a required
attribute, unless it is present in your template. Tapestry has no
reason to do so (though perhaps a later version that has native
support for HTML5 will do so). On the other handle, Tapestry does
have valiation, represented on the
Changed compiler target to 1.5 in our latest tynamo-parent, so new
releases should work again on 1.5 out of the box.
Kalle
On Fri, Feb 4, 2011 at 5:21 AM, Michael Gentry mgen...@masslight.net wrote:
The other day on the Cayenne list we were talking about dropping
support for Java 1.5 in
