On 12/14/2021 10:40 PM, Dimitris Zenios wrote:
Hi all it seems there is a raise condition when realizing lazy loaded
services.
I managed to find two issues reported already with the exact same issue
1. https://www.mail-archive.com/users@tapestry.apache.org/msg77239.html
hi,
my suggested fi
On 08/16/2020 10:20 PM, Thiago H. de Paula Figueiredo wrote:
I've committed a fix using your code as a test and uploaded a new Tapestry
5.6.0 snapshot to the ASF snapshot repository at
https://repository.apache.org/content/groups/snapshots/. Could you please
test on your end too? Thanks in advan
Hi everyone,
we recently found a strange deadlock problem; first seemed to be related
to switching from 5.5.0-beta-1 to 5.5.0, at least
in the full application it was easy to reproduce with the latter but (in
a few manual tests) not with the beta.
after trying to reduce it to a minimal test
Hi everyone,
given something like this:
public interface Blub {
public default String foo() {
return "Default";
}
}
public class BlubImpl implements Blub {
@Override
public String foo() {
return "Impl";
}
}
when calling "registry.getService(Blub.class).foo()" using beta-1 this
