Re: tapestry-hibernate + tapestry-cdi

2016-09-23 Thread Adam X
Problem solved. Just to give back to the community here is how I solved it and what I've learned. First, it looks like when using tapestry-cdi in the project, tapestry-hibernate becomes completely unnecessary. In fact, it cannot and should not be used. In general, with JSR-330 (tapestry even

Re: tapestry-hibernate + tapestry-cdi

2016-09-23 Thread Qbyte Consulting
Ive been using tapestry jpa on an application that accesses 3 databases, 1 Postgres and 2 mssql. It's just fine. Surprised tapestry hibernate doesn't support this. Sent from my iPhone > On 23 Sep 2016, at 09:36, Adam X wrote: > > Yes, JPA should an option. I don't think

Re: tapestry-hibernate + tapestry-cdi

2016-09-23 Thread Adam X
Yes, JPA should an option. I don't think foo uses a single hibernate annotation and our foo team often brags how they code to the spec :) So I will try tapestry-jpa (didn't even know about it). If that doesn't solve the problem I will try implementing @Session. I may come back with this if I

Re: tapestry-hibernate + tapestry-cdi

2016-09-23 Thread Kalle Korhonen
AFAIK, tapestry-hibernate simply doesn't support it. However, is switching to JPA an option? You could still be using Hibernate as the provider. tapestry-jpa merrily supports multi tenancy (and more). If JPA is not an option, I'd look into implementing your own custom @Session - may not be too bad

Re: tapestry-hibernate + tapestry-cdi

2016-09-23 Thread Adam X
Yep, like I said, that part is easy and I believe I can get that resolved. My question is how to tell Tapestry that @Inject Session is done by foo+tapestry-cdi and it should use @Inject @Named Session instead? On Fri, Sep 23, 2016 at 10:13 AM, Qbyte Consulting wrote: >

Re: tapestry-hibernate + tapestry-cdi

2016-09-23 Thread Qbyte Consulting
What about exclude tapestries default hibernate dependency with Maven exclude? Sent from my iPhone > On 23 Sep 2016, at 09:05, Adam X wrote: > > Hi, > > I have what seems like a major collision problem and don't know how to > solve this. My current architecture is as

tapestry-hibernate + tapestry-cdi

2016-09-23 Thread Adam X
Hi, I have what seems like a major collision problem and don't know how to solve this. My current architecture is as following: foo weld tapestry-cdi tapestry-core I'd like to have: foo weld tapestry-cdi tapestry-hibernate foo (jar) is a major depenency of my project. It is an internal