IIRC it goes: 1. configuration 2. mapping overrides configuration 3. code overrides mappings
this is driven by 2 concepts 1. general/broad to specific: configuration file acts like a "catch all " or default setting. this can then be overridden for specific entities/queries in the mappings 2. order of operations: 1st the configuration is loaded, then the mappings. now you have a configuration object you can manipulate prior to creating the session factory. On Wednesday, July 11, 2012 9:14:04 PM UTC-4, Throckmorton wrote: > > In NH3.0, there are three ways of configuring the cache on entities: > > 1. in the mapping file > 2. in the configuration xml settings > 3. in code using the Configuration object > > Is there an order of precedence for these different options? If I have > read-write caching configured > in the mapping file, and then I set read-only caching in code, which > setting does NH use? > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/e0MiaFJBSSwJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
