Howard, you are nuts! Thanks for all the hard work. We probably need to
give at least a few weeks to let everybody digest these changes, what do
you think about the public beta release?
Kalle
On Tue, Aug 27, 2013 at 2:41 PM, Howard Lewis Ship wrote:
> This release swaps out Bootstrap 2.3.2 for
I work to correct the @CommitAfter problems. Since I have 'overwritten' the
Tapestry HibernateManager class, I see the following behavior.
For every request a new session object is created and opened.
So when you have something like this:
myPage() {
A: userService.getUserProfile();
B: loca
Hi there,
after my struggle with the current @CommitAfter implementation and the
transaction handling I was able to fix it for the actual project I am
working on. I found several places where my coworker and introduced bugs
because of the current (flawed) implementation of @CommitAfter.
(For
I also now have true read only transaction that set the underlying jdbc
connection to read only and FlushMode.Never for the session. And yes the
read only transactions are also committed so you do not spam your database
logs with rollback information.
2013/8/27 Martin Kersten
> Hi there,
>
>
>
This release swaps out Bootstrap 2.3.2 for Bootstrap 3.0. The ControlGroup
mixin has been renamed to FormGroup. A new Glyphicon component has been
added.
The tapestry-wro4j module has been renamed to tapestry-webresources; it
does the same job, but without the dependency on WRO4J.
All of the Boo
Hi,
I was just wondering if the the T5.4 URLs on:
http://tapestry.apache.org/download.html
could be updated to point to:
https://repository.apache.org/content/groups/staging
For currently, the alpha1 and alpha2 URLs mentioned don't exist.
Steve.
Hi,
Is there a way to include everything of the jquery ui packages without
including everything manually?
Cheers
--
Sincerely
*Boris Horvat*
Hi Geoff,
When a LinkSubmit (or Submit) is in an AjaxFormLoop, it appears that
t:defer is always true. Even when you set it explicitly to false, the
event handler is fired at the end and the t:value (on the
AjaxFormLoop) is always the last value of the loop. Therefore, when
your LinkSubmit/Submi
Thanks for the quick reply.
I will go through these links.
On Tue, Aug 27, 2013 at 1:39 PM, Lance Java wrote:
> I've never fully understood the use case for the select event. I've always
> seen select done by putting a in the Tree's
> parameter.
>
> Here's a couple of examples:
> http://tapes
I've never fully understood the use case for the select event. I've always
seen select done by putting a in the Tree's
parameter.
Here's a couple of examples:
http://tapestry-stitch.uklance.cloudbees.net/databasetreedemo
http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/treefromdata
Hi All,
I need some info on how we differentiate b/w the expansion of a node and
selection of a node.
Could you please give me any references or info on this
Thanks,
Giri
It's clumsy but what I did was duplicate my disabled fields with a dummy set of
t:ids and condition them with an if on the same disabled property value and
then I removed the validate attribute which works fine. In my else block I have
the regular form to submit with the non disabled fields and
Hi,
Yes there were errors, they were hidden by the jquery accordian I used for the
form and caused by using default true along with validate, even though the
fields were not invalid.
John
- Original Message -
From: Geoff Callender
To: Tapestry users
Sent: Tuesday, August 27,
13 matches
Mail list logo