users@tapestry.apache.org

2017-05-09 Thread Thomas Mayer
done: https://issues.apache.org/jira/browse/TAP5-2582 Am 09.05.2017 um 14:29 schrieb Thiago H. de Paula Figueiredo: > Hello, Thomas! > > Thanks for you very thorough digging of what's happening here. I think it > shed a light on what the problem is: the copying of annotations from > service impl

users@tapestry.apache.org

2017-05-09 Thread Thiago H. de Paula Figueiredo
Hello, Thomas! Thanks for you very thorough digging of what's happening here. I think it shed a light on what the problem is: the copying of annotations from service implementation to service proxy. At least Tapestry-IoC should provide a way of preventing this from happening in a per-service basis

users@tapestry.apache.org

2017-05-09 Thread Thomas Mayer
@Dmitry, I looked up the sources of Hibernate's Session interface: public interface Session extends SharedSessionContract, EntityManager, HibernateEntityManager, AutoCloseable { There is to say that - SharedSessionContract defines a void close() function. - EntityManager defines a void close() f

users@tapestry.apache.org

2017-05-09 Thread Thomas Mayer
Hi Dmitry, here's the output when executed in debug mode. I also enabled debug log for tapestry. In Tapestry's debug output (which I cleaned up and ordered), I found 3 close()V function signatures. Could they be candidates for the issue?. Best regards Thomas public beginTransaction()Lo

users@tapestry.apache.org

2017-05-09 Thread Dmitry Gusev
Possible workaround could be to use tapestry-jpa, it should work fine with latest Hibernate (5.2.x). It won't give you an instance of `Session` as a service, but you could either: - type-cast `EntityManager` to the `Session` (as Hibernate `Session` extends JPA's `EntityManager`), or - use get it w

users@tapestry.apache.org

2017-05-09 Thread Dmitry Gusev
Hi, The error states that Tapestry Plastic failed to build a proxy class for the Session interface because it found duplicate method signature. I saw this error once when I tried to implement generic support and had two methods with same erasure types. Maybe if you find the name of the method that

users@tapestry.apache.org

2017-05-09 Thread Thomas Mayer
Thanks for the hint. Indeed, that would be an option and it is great to see that Tapestry already covers that use case for Hibernate, too. However, using tapestry-hibernate-core takes me back to hibernate-core 4.3.6.Final which got released in July 2014 (although a 4.3.11.Final also is available,

users@tapestry.apache.org

2017-05-09 Thread Lance Java
There's tapestry-hibernate-core which only depends on tapestry-ioc. tapestry-hibernate builds on top of this with web specific services https://mvnrepository.com/artifact/org.apache.tapestry/tapestry-hibernate-core/5.4.3 On 9 May 2017 03:54, "Thomas Mayer" wrote: > Hello Thiago, > > thanks for