Hi all,
The documentation is outdated re:Unit Testing of Page or Components. On
earlier build of Tapestry 5, I could pass context to PageTester as shown in
the docs. However, this is no longer supported in the latter builds. So,
how does one pass context to PageTester now?
Thanks.
Em Sat, 30 May 2009 18:17:46 -0300, Juan E. Maya
escreveu:
I was thinking about something similar to what spring has to offer.
Me too. :) But using EJB3 annotations (are they part of a standard), not
the Spring ones, of course. I guess the step after this one would be to
build some secu
Hi!
As the Tapestry group creator at LinkedIn (there's also one in Facebook),
I'm sorry for the late response to some requests to join. I was not warned
about them by LinkedIn. :( Anyway, welcome to the new members! We're 117
now! :)
--
Thiago H. de Paula Figueiredo
Independent Java consu
It's been a rough week ... I still had my sore throat (noticeable
during the webinar) when I arrived to do four days of accelerated
Tapestry training in Michigan. Returning after midnight on Friday, I
had morning and afternoon slots at Portland Code Camp on Saturday to
talk about Clojure and Tapest
2009/5/31 Robert Zeigler :
> So, you're suggesting that a translator named, eg, "StringTranslator" would
> be the default for strings, "IntegerTranslator" for integers, and so forth.
> It could be done.
Yes, but Translator name property should be meaningful, not class name
of Translator. So, "stri
as per my comment at : https://issues.apache.org/jira/browse/TAP5-721
I just started looking for a way on how to make this work and have an
architecture question. The logic to handle a missing key message or
exception lives in AbstractMessages and is quite straight forward.
Adding a boolean field
