Skip to main content

User and deployment specific customization of webstart app

1 reply [Last post]
najmi
Offline
Joined: 2003-06-17

I have an app that is WebStart accessible.

I have the following two customization use cases that I am not sure how to best address...

1. Deployment-specific customization

The app's JNLP distribution may be installed at multiple deployments. Each deployment may need to customize the jnlp distribution slightly. Here are two examples:

a) The app uses spring framework's XML configuration files which are loaded from the classpath of the app using spring's ClassPathXmlApplicationContext. I would like to know how a deployment could specify its own deployment specific version of such a spring XML file ahead of the default one in the classpath.

See related posting in spring forum:

b) Each deployment may also need to specify deployment specific system properties that are different from the defaults in the source distribution.

2. User-specific customization

Each user within each deployment may wish to personalize their local copy of my app. Again personalization could mean providing a spring XML config file or system properties to override the ones at the deployment site.

What are some best practices to address these Java Webstart use cases?

TIA for your help.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
swv
Offline
Joined: 2007-05-28

najmi wrote:
2. User-specific customization

Each user within each deployment may wish to personalize their local copy of my app. Again personalization could mean providing a spring XML config file or system properties to override the ones at the deployment site.

I am not sure this applies to JWS specifically, but the *good* applications I have seen have handled customization by keeping customization information in an XML file and reading it at runtime.... so.. things like editor prefs, macros.. stuff like that... I was thinking to do it in javaDB but it seems to be read-only if deployed in a jar as in JWS...