Do you want to use Hibernate *and* iBATIS or just one? The current setup for iBATIS isn't as good as we'd like - mainly because Maven doesn't seem to allow overriding properties at this point.
http://jira.codehaus.org/browse/MNG-2757 Until we figure out a solution, it seems there's only two ways to set a DAO Framework with AppFuse/Maven. 1. Pass it in from the command-line: mvn jetty:run-war -Ddao.framework=jpa-hibernate 2. Set it in your MAVEN_OPTS environment variable: export MAVEN_OPTS='-Ddao.framework=jpa-hibernate'. Both of these seem pretty fragile as it requires end users to do something. If they don't set the MAVEN_OPTS variable, they'll end up with Hibernate instead of iBATIS or JPA. I know it's ugly, but we haven't figured out a better workaround yet. In addition to setting this property, you'll need to modify your web.xml to remove Hibernate's LazyLoadingFilter since there will be no sessionFactory bean available. Matt On 2/3/07, Nick Tucker <[EMAIL PROTECTED]> wrote:
Hi Is there an easy way to set up iBATIS support. When I generate an application using the basic archetype, the appfuse-hibernate jar is included, and this holds the applicationContext-dao.xml. I assume that I could set the appfuse-hibernate jar to be a provided dependency in my pom.xml, and then add the appfuse-ibatis jar as a dependency. Is there a better way - using an archetype or something. I would expect people to not normally want to use more than one dao framework in an application. Nick -- View this message in context: http://www.nabble.com/Using-iBATIS-tf3167698s2369.html#a8787392 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
