Home > Articles > Web Services > SOA

It's Time to Reinvent Java Web Services

📄 Contents

  1. Current Difficulties with Java Web Services
  2. A New Framework for Java Web Services
Java Web Services are way too difficult, and there should be a simple “ON/OFF” switch for activating services in Java. In this article, Mark Hansen, author of SOA Using Java Web Services , describes the shortcomings of JAX-WS, JAX-RS, and JAXB as tools for enterprise web services. He introduces a new Java framework developed by Proxisoft to make web services easy and move the industry closer to having the “ON/OFF” switch he envisions.
Like this article? We recommend

Like this article? We recommend

Adding web services to Java applications should not require programming. There should be a simple ON/OFF switch. You should be able to select some business logic, flip the ON switch, and publish it as a web service.

Unfortunately, Java isn’t designed that way. Java requires you to write code, annotate classes, recompile, and redeploy. And it isn’t simple coding either — particularly when you run into problems with Java/XML serialization.

In my book SOA Using Java Web Services, I detail my frustrations with Java’s web services support. Page 3 quotes Dave Podnar’s 2006 blog entry:

    Dave Podnar's Five Stages of Dealing with Web Services

    1. Denial: It's Simple Object Access Protocol, right?
    2. Over-Involvement: OK, I'll read the SOAP, WSDL, WS-I BP, JAX-WS, SAAJ, JAXB, … specs. Next, I'll check the wiki and finally follow an example showing service and client sides.
    3. Anger: I can't believe those #$%&*@s made it so difficult!

    4. Guilt: Everyone is using Web Services. It must be me; I must be missing something.
    5. Acceptance: It is what it is. Web Services aren't simple or easy.

Since writing that book, I’ve spent a great deal of time thinking about how to reinvent Java Web Services as a simple ON/OFF switch. After three years working with some smart people at Proxisoft, we’ve made a lot of progress.

This article highlights the problems with Java Web Services and describes how we are solving them. The algorithms and framework described here are incorporated in our Netrifex product.

Current Difficulties with Java Web Services

A legion of issues conspires to make Java Web Services difficult, particularly for enterprise application development. This article highlights three: programming complexity, source code binding, and framework ignorance.

Programming Complexity

JAX-WS, JAX-RS, and JAXB are the Java standards for implementing web services (also known as the JAX-* standards). JAX-WS handles SOAP, JAX-RS handles REST, and JAXB provides Java/XML serialization for both SOAP and REST.

For the most part, using these standards involves adding annotations (for example, @WebService, @GET, @XmlRootElement) to your source code. Most Java Web Services tutorials mask the complexity of this process by focusing on simple “hello world” examples.

However, when you try using the standards with real applications, the complexity grows exponentially. In a recent experiment, I used JAX-* to web-service–enable a simple stock trading demo application that we use for testing at Proxisoft. In order to expose a single class as a service, I ended up having to modify more than 30 other classes with various JAXB annotations. This happens because, in order for Java to serialize a single class, it must know how to serialize all of its dependent classes as well.

Even after introducing the required annotations on the 30 classes, I found that the resulting web service threw exceptions and failed at runtime. Why? Many of the dependent classes did not have no-arg constructors — a JAXB requirement that causes runtime exceptions during deserialization. After solving that problem, other issues surfaced. Method parameters and return types that were interfaces or abstract classes caused similar JAXB failures and had to be modified.

Even after making all these changes in the code to satisfy JAX-*, I still encountered runtime exceptions. The reason was that the application’s class dependency graph included a cycle. To solve this problem, I had to implement the CycleRecoverable interface on one of the dependent classes. Implementing this interface required writing code to handle the runtime serialization errors resulting from cycles.

Source Code Binding

As discussed in the previous section, programming Java Web Services for real-world applications is complex and time-consuming. But for the sake of argument, suppose you master JAX-*. Suppose you slog through all the complexities of mapping your application to web services with these standards. What has been accomplished?

Well, you now have web services baked into your application’s source code. What happens when your application is running in production and you need to add, modify, or remove some web services? You need to modify the source code, unit test, application test, recompile, repackage, and redeploy.

Embedding web services in source code with annotations is not very agile.

Framework Ignorance

In addition to being complex and inflexible, programming JAX-* is too low-level. These programming standards are completely ignorant of application frameworks like Struts or Spring. As a result, when you code with JAX-*, you cannot plug in to the powerful machinery provided by such frameworks.

Consider a Struts application being used for e-commerce. Say you want to web-service–enable it to support B2B integration. You basically have to re-create the entire View-Controller part of the application to support web services interaction.

It shouldn’t be this way. After all, the business logic and APIs that need to be exposed as web services are already encoded in the existing services classes that are invoked by Action classes, and mapped to a web interface by the ActionForms and ActionMapping. You should simply be able to flip an “ON” switch to expose selected parts of this existing infrastructure as web services.

The reason that JAX-* doesn’t work well with Struts is that session management and application context are managed by the Struts infrastructure independent from the business logic managed by the service classes. For example, you could use JAX-* to web-service–enable a ShoppingCart class, but because the resulting service will be stateless, there is no natural way of associating a user’s web service invocation with the instance of ShoppingCart belonging to his session. What’s needed is a framework that understands how Struts manages sessions and can expose the ShoppingCart in a stateful manner.

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.


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.


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.


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.


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


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


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.


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.


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