Home > Articles > Programming > Java

Java Properties Purgatory Part 2

Nonstandard component configuration interfaces (CCIs) for Java lead to wasted time and wasted code. Stuart Halloway looks at problems with the current XML CCIs and proposes a common CCI architecture for all Java components.
Copyright 2002 by Stuart Halloway and DevelopMentor. This article originally appeared in DevelopMentor’s free white paper collection and is reprinted here with the permission of DevelopMentor and the author.
Like this article? We recommend

Abstract: In Part 1 I looked at the sad state of component configuration in the Java world. Today, component developers often rely on property files to configure and manage their components. Unfortunately, this is done in an ad hoc way, with each component developer reinventing the wheel. As a result, Java components are unnecessarily difficult to develop, learn, deploy, and maintain. This is an industry-wide problem, costing countless hours of developer time.

To provide a common vocabulary for discussing component configuration, I introduced the notion of a Component Configuration Interface (CCI). A CCI is any configuration contract specified by a component developer. A CCI is typically not a Java interface, and can take a variety of forms: properties files, serialized Java objects, system properties, XML documents, etc.

I proposed four criteria for designing a standard CCI for Java components: support for structure, lookup, scope, and metadata. In this second part I will use these criteria to

  • Introduce XML as a configuration option

  • Examine the weaknesses of current XML CCIs: the Preferences API and J2EE container configuration

  • Propose a common CCI architecture for all Java components

Using XML for configuration

As of SDK version 1.4, XML parser support is now a standard part of the Java language. Using XML as a configuration format provides an immediate and obvious answer for one of the four CCI criteria--structure. In Part 1 we looked at the difficulty in representing even simple multi-valued strings in property files. With XML, this problem disappears. For example, multiple values for security providers might be specified as

<providers>
<provider>sun.security.provider.Sun</provider>
<provider>com.sun.net.ssl.internal.ssl.Provider</provider>
<provider>com.sun.rsajca.Provider</provider>
<provider>com.sun.crypto.provider.SunJCE</provider>
<provider>sun.security.jgss.SunProvider</provider>
</providers> 
            

This looks so simple that it is difficult to believe the power and benefit to be gained by adopting XML for component configuration. The advantages are overwhelming:

  • There is only one syntax to learn, so there is no need to remember that some properties delimit values with spaces, others with colons, etc.

  • There is no need to write special parsers for configuration data--the XML parser is built-in.

  • XML parsers can validate that the basic syntax of configuration data is correct.

  • Component developers can use an XML Schema or Document Type Declaration (DTD) to specify the exact structure they expect to receive. This is to CCIs what strongly-typed languages are to APIs.

  • There are an enormous number of tools available to create and manage XML data.

  • XML is language neutral, so the same concepts can be applied to non-Java applications. This is important in the real world where most complex applications are not 100% Java (or anything else).

Given all these benefits, you should make XML your standard for all component configuration. However, there are a few potential counterarguments to consider as you choose this course. Here are three (weak) arguments against XML for component configuration in Java:

  1. XML has considerable potential for ambiguity and confusion.

  2. XML is overkill for simple configuration.

  3. XML-based configuration is not backwards-compatible with existing code.

We will look at each of these in turn.

XML: Potential for confusion?

The concern here is that XML is no better than property files, since there are many ways to encode the same data in XML. For example, the following two XML fragments convey the same basic semantics:

<server codeurl="http://www.develop.com">
<!-- 
            etc. -->
</server>
<server>
<codeurl>http://www.develop.com</codeurl>
<!-- 
            etc. -->
</server>

If a deployer specifies codeurl as an attribute, but the component was expecting a codeurl element, then things will break down. How is this any better than misspelling a property name or choosing the wrong delimiter? In three ways:

  1. Even though errors can occur, they are now being detected by an XML parser, which is presumably thoroughly tested, instead of a one-off configuration parser written by a component developer.

  2. Schemas and DTDs can be used to automatically detect a wide range of incorrect information.

  3. XML-aware tools can help prevent these errors from occurring in the first place.

In short, XML provides a full-fledged type system. Yes, confusion is still possible. However, XML gives you a vocabulary that is as rich for CCIs as the Java language is for APIs.

XML: Overkill for simple configuration?

It is true that XML may be more than you need. There is nothing quite as simple as setting a property on the command line, e.g.:

java -Djava.security.policy=my.policy 
            MyApplication

However, there is nothing to say that command-line properties, property files, and XML cannot coexist as configuration options for the same component--as long as there are well-defined rules for precedence that apply to all components. More on this later.

XML and backward compatibility?

The current installed based of Java applications includes thousands of shell scripts to correctly set various CCI properties. A wholesale industry switch to XML would require rewriting these scripts. Also, such a switch would be problematic where pre-1.4 versions of Java are still in use. So, XML cannot be a complete solution. A general-purpose CCI will need a backwards-compatibility mode that includes the various ad hoc solutions currently in place, without encouraging their continued use in the future.

Where are we?

XML alone solves exactly one of the four problems for component configuration, providing structure and type for configuration data. Next we will look at some existing XML CCIs to see how they deal with the other three elements of CCI: lookup, scope, and metadata.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020