Hi Angelo,

yes ... the service you get from tapestry-hibernate is not mainly just reading 
the config. This is simple, you could do it yourself, this is just an
additional benefit.

The main service you get is that sessions and transactions are openend, closed 
and committed (hopefully even rolled back in case of exception) at the
right moment during request processing so that you don't have to care about.

Manually commiting a transaction though causes an error when tapestry tries his 
automatic commit.

Have fun!

Marcus.



                                                                                
                                                                                
    
                      Angelo Chen                                               
                                                                                
    
                      <[EMAIL PROTECTED]        An:       
users@tapestry.apache.org                                                       
                           
                      hoo.com.hk>              Kopie:                           
                                                                                
    
                                               Thema:    Re: T5: Hibernate      
                                                                                
    
                      10.09.2007 12:18                                          
                                                                                
    
                      Bitte antworten                                           
                                                                                
    
                      an "Tapestry                                              
                                                                                
    
                      users"                                                    
                                                                                
    
                                                                                
                                                                                
    





Hi Davor,

Never mind the question, the error comes from a invalid table name, I forgot
it's case senstive. I'd like to now if can use the transaction normally,
like:

  Transaction tx = _session.beginTransaction();
        List fruits = _session.createQuery("from Fruit f order by
id").list();
        System.out.println(fruits.size() + " found");
        tx.commit();

the commit will have an excpetion:
[WARN] ThreadCleanupHub Error invoking listener
[EMAIL PROTECTED]:
Transaction not successfully started
org.hibernate.TransactionException: Transaction not successfully started




_____________________________________________________________________
prosystems IT GmbH
Anwendungsentwicklung
Postfach 31 51
53021 Bonn (Germany)

Tel: 0228 / 3366 - 3329, Fax: 0228 / 3366 - 73329
mailto:[EMAIL PROTECTED] http://www.prosystemsIT.de
Amtsgericht Bonn - HR B 13189
Geschaeftsfuehrer: Vassilios Timiliotis, Richard Adams


Der Austausch von Nachrichten mit der prosystems IT GmbH via E-Mail dient 
ausschliesslich Informationszwecken. Rechtsgeschaeftliche Erklaerungen
duerfen ueber dieses Medium nicht ausgetauscht werden. Verfaelschungen des 
urspruenglichen Inhaltes dieser Nachricht bei der Datenuebertragung koennen
nicht ausgeschlossen werden.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to