The simple answer is that spring mapping locations accepts a real path, ie, c:\yourlocation . Don't use a classloader location for inside the aar nor an expanded aar. Spring in debug shows you where the classloader locations are, and the path you have for the aar won't be one of them. WEB-INF/classes would be a classloader location, but that kind of defeats the purpose of spring in the aar. So use a real path, don't use a classloader path! The link I gave you shows you how. Or google on using mapping locations with a real path for an example.
Spring inside the aar is an advanced option, sure you're not better off just putting the spring jars in WEB-INF/lib and your mapping files in WEB-INF/classes ? Sorry its not working for you, but it would work if you are reading what I'm saying carefully. HTH, Robert On 7/12/07, Brian Kates <[EMAIL PROTECTED]> wrote:
This is proving to be quite the challenge. At first I put the Hibernate mapping files in domain/mappingfile.hbm.xml. Then I moved it into WEB-INF/classes/domain/mappingfile.hbm.xml. I've tried all kinds of different ways to reference the files in the applicationContext but no such luck. I'm curious if there is a working example of Spring/Hibernate AAR out there somewhere? I'm running out of options! :( As for the link you sent, if I'm prefixing the hibernate mapping with "classpath", do I have to do anything special to include those mappings in the classpath? -Brian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
