S
success_ny
I would like to package my Java application (executable, not J2EE or
web) in a JAR and not package my resource bundle properties file in a
JAR. My reasoning is as follows: one of the reasons I use resource
bundle as a .properties file is that it makes it easy to make changes
to certain properties dynamically at run-time without recompiling the
application. Especially if the application is in production, any
changes to the JAR would be complicated. So, ideally I would like my
resouce bundle properties file to reside separately from the JAR where
the code is packaged so I can change, say, flag settings (like, enable
debugging at run-time) or make other changes without touching the JAR.
Does it make sense? How do I load Resource Bundle if it just resides on
the file system and is not part of JAR efficiently?
Thank you!
web) in a JAR and not package my resource bundle properties file in a
JAR. My reasoning is as follows: one of the reasons I use resource
bundle as a .properties file is that it makes it easy to make changes
to certain properties dynamically at run-time without recompiling the
application. Especially if the application is in production, any
changes to the JAR would be complicated. So, ideally I would like my
resouce bundle properties file to reside separately from the JAR where
the code is packaged so I can change, say, flag settings (like, enable
debugging at run-time) or make other changes without touching the JAR.
Does it make sense? How do I load Resource Bundle if it just resides on
the file system and is not part of JAR efficiently?
Thank you!