On Fri, 27 May 2011 23:10:35 -0300, iberck wrote:
Any plans for suppor live class reloading in spring beans?
No, as they're not instantiated by Tapestry-IoC.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars
Any plans for suppor live class reloading in spring beans?
Thanks in advance
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-2-Need-Advice-on-JDBC-and-Transaction-Mgmt-tp3301388p4433969.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
I'm implementing this approach to have live class reloading with TapestryIoC
Services Annotated with spring's @Transactional, but I have a problem:
How can I implement this approach COMPLETE, my problem is when I define for
example @Transactional(readonly=true) or
@Transactional(rollbackfor=Except
I've try it and it's working. Thank you very much.
Now I can use JdbcTemplate and declarative transaction on my Tapestry
Service, so I can take advantage of T 5.2 service reload feature.
This is improving productivity a lot.
Thanks...
Best regards,
Yohan Yudanara
On Mon, Dec 13, 2010 at 8:32 A
Thank you very much for your explanation and code sample, Mr. Christian Köberl
I will try it.
On Sun, Dec 12, 2010 at 10:34 PM, Christian Köberl
wrote:
>
>
> Yohan Yudanara-2 wrote:
>>
>> So, in my conclusion (CMIIW), if I'm using JDBC instead of Hibernate,
>> I'd better stick with service/dao in
Yohan Yudanara-2 wrote:
>
> So, in my conclusion (CMIIW), if I'm using JDBC instead of Hibernate,
> I'd better stick with service/dao in spring bean. Because in spring
> bean, I can use spring declarative transaction and also JdbcTemplate.
> If I want to use tapestry service instead of spring be
Ok, thanks to all...
So, in my conclusion (CMIIW), if I'm using JDBC instead of Hibernate,
I'd better stick with service/dao in spring bean. Because in spring
bean, I can use spring declarative transaction and also JdbcTemplate.
If I want to use tapestry service instead of spring bean, I need to
w
On Sat, 11 Dec 2010 22:01:08 -0200, Yohan Yudanara
wrote:
hmm.. maybe I could use DataSourceTransactionManager instead of
HibernateSessionManager, because I'm using JDBC instead of hibernate.
When using this code, where do we place our DAO for accessing database
? tapestry service or spring
Thanks for your reply..
hmm.. maybe I could use DataSourceTransactionManager instead of
HibernateSessionManager, because I'm using JDBC instead of hibernate.
When using this code, where do we place our DAO for accessing database
? tapestry service or spring bean ?
Thanks in advance..
On Sat, De
Unfortunately, I prefer use JDBC to Hibernate.
I'm not using Hibernate in my projects.
If I'm stick to JDBC, is it better to stick with Spring Service for
declarative transaction and accessing database ?
Thanks in advance
On Sat, Dec 11, 2010 at 11:53 PM, Josh Canfield wrote:
> For most cases u
For most cases using tapestry-hibernate should be sufficient. Have you
looked at that?
http://tapestry.apache.org/current/tapestry-hibernate/userguide.html
Are you doing something that would make this not sufficient?
On Sat, Dec 11, 2010 at 2:36 AM, Yohan Yudanara
wrote:
> Hi..
>
> Tapestry 5.2
I would stick with Spring for transaction handling, since there's a lot of
knowledge and tricks in the Spring transaction management and a lot you
could do wrong.
We have our own implementation of Spring @Transactional in Tapestry but
we're now switching to a hybrid version using the Spring
Platf
Hi..
Tapestry 5.2 live service reload is awesome.
However, I'm used to accessing database using Spring JdbcTemplate
(using spring bean with @Repository annotation) and manage transaction
using spring declarative transaction (in ApplicationContext.xml).
I'm considering to use tapestry service inst
13 matches
Mail list logo
