Jun 10th, 2010, 04:45 AM
Configuration Strategy for J2SE Library?
We've modularized a portion of our app by moving a package of DAO interfaces/implementations out to a self-contained library. How is configuration best managed, within this JAR?
Currently, we're simply loading the Spring config within the constructor of our facade class, which works for our immediate needs, but this feels wrong. What's the cleanest way of managing this?
Are there arguments for simply hard-wiring the configuration within this library, given that no real flexibility is intended, here? (Why should a library be applicationContext-aware? Perhaps it shouldn't...)
Thanks in advance, for your input.
Jun 17th, 2010, 12:56 AM
This thread discusses this issue in detail, and I recommend you read it thoroughly:
I think I've seen more of these sort of discussions in the Architecture forum. Just search, or browse the forum - there interesting stuff there
Tags for this Thread