I would suggest putting your hibernate.cfg.xml in both project's 
src/main/resources (in the root directory), then using 
classpath*:hibernate.cfg.xml should work. If it doesn't, crack open core1.jar 
and make sure the file is being properly included in the JAR. If you're putting 
it in src/main/java, it won't be included unless you tell Maven to include 
*.xml files.

On Jun 29, 2010, at 7:49 AM, Josep García wrote:

> Hello,
> I am making progress in converting my AppFuse application to multi-module, 
> for better structure and multiple deployments.
> I am using AppFuse 2.0.2 with struts2 + spring.
> Ok.
> I am now stuck with this:
> 
> I have modules:
> - core1
> - core2
> 
> Each module has his own beans. core2 depends on core1, and references core1's 
> beans.
> In core1 I have src/main/resources/hibernate.cfg.xml with his mapping class 
> defs.
> 
> In core2 I would like to have only the additional mapping class defs in his 
> own hibernate.cfg.xml file.
> 
> Based on what's suggested in post: 
> http://appfuse.547863.n4.nabble.com/how-to-config-more-than-one-hibernate-cfg-xml-td565276.html,
>  I tried having several hibernate config files with this core1's 
> applicationContext-dao.xml update:
>         <property name="configLocations" 
> value="classpath*:hibernate.cfg.xml"/>
> 
> But doesn't work for me. Only core2's hibernate.cfg.xml is loaded.
> 
> I also tried this:
> 
> core2's: applicationContext-dao-core2.xml: 
> 
> <bean class="org.appfuse.dao.spring.HibernateExtensionPostProcessor">
>      <property name="mappingResources">
>          <list>
>              <value>es/isigma/portasigmaquota/model/hibernate.cfg.xml</value>
>          </list>
>      </property>
>  </bean>
> 
> ... core2's beans ...
> 
> but doens't make a difference.
> 
> Any pointers for this?
> 
> Josep
> 

Reply via email to