Bernard Sirius wrote:
Sorry to be so intrusive :-/
...no problem

now that I've disabled the maxFetchDepth, I bump to
this 31 maximum-for-mysql-joins-problem again.

here's what generated in the applicationContext.xml.
Do you still confirm that it means that proxies are
enabled:
  
I can not confirm you unless you show me a entity hbm, since this config is not within the applicationContext.xml, but on the association mappings.
<property name="hibernateProperties">
  <props>
    <prop key="hibernate.show_sql">true</prop>
    <prop
key="hibernate.dialect">net.sf.hibernate.dialect.MySQLDialect</prop>
    <prop
key="hibernate.cache.use_query_cache">false</prop>
    <prop
key="hibernate.cache.provider_class">net.sf.hibernate.cache.EhCacheProvider</prop>
    <prop
key="hibernate.cache.query_cache_factory">net.sf.hibernate.cache.StandardQueryCacheFactory</prop>
  </props>
</property>

  
I've checked in the hbm's: all the lazy="true"
attributes are on <set> tags, never on
      
<many-to-one>
    
or anything else...

      
but it should not be used in many-to-one, please
refer to
    

OK how can I check that the lazy-modeled
relationships, especially, the one-2-one ones indeed
generate the right mapping info then?
  
Lazy settings will only be used for maps,sets,list and bags, on the "many" side of one-2-many associations, so in any case you will find it on a many-to-one or a one-2-one relationship.
Referring this, Andromda will only use tagged values when they make sense, with this I mean that if you modelled a lazy TV within a one-2-one association, andromda will not do anything with it.

Carlos
bernard


	
		
__________________________________ 
Celebrate Yahoo!'s 10th Birthday! 
Yahoo! Netrospective: 100 Moments of the Web 
http://birthday.yahoo.com/netrospective/


  

Reply via email to