Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a java application which is packed into an executable jar file and it uses it’s own conf directory to store some configuration options.
Now I want to distribute it as a Java Web Start application. I know that I could pack the configuration files in the distributed jar but it should cause some significant changes in application logic.
So is there a standard way or a simple workaround for the configuration directory distribution?
Configuration options for a rich client deployed using JWS are probably best stored in the
PersistenceService.