How do I upgrade my webservice from JBoss 4.0.4 (and below) to JBoss EAP?

Solution Unverified - Updated -

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 4
    • 5
    • 6

Issue

  • I have a webservice deployed on JBoss 4.0.4 or any version below that. How do I migrate it to a version of JBoss EAP?

Resolution

There are a few scenarios to consider:

  • If possible, the preferred scenario is to upgrade your webservice to use JAX-WS to deploy your webservice. This will require changes to your application and will possibly require changes to your WSDL.
  • If your WSDL is RPC/Encoded, then you should package Axis 1 in your deployment and use it to deploy your webservice.
  • If your webservice conforms to the JAX-RPC specification, then upgrading should take little effort (i.e. you can use JBossWS with few modifications).
  • If your webservice is neither RPC/Encoded nor conforms to the JAX-RPC specification, then you can likely use JBossWS with some to many changes to your webservice implementation.

If you have any doubts about how to migrate, opening a support case with Red Hat is recommended so you can get a profesional opinion on how to migrate.

Root Cause

Before JBoss 4.0.4, JBoss used WS4EE as its webservice stack. Since 4.0.4, JBossWS has been the primary stack. Both stacks are JAX-RPC compliant, so webservices that conform to JAX-RPC won't have any issues migrating. WS4EE is based on Axis 1, so if you have major trouble migrating, it may be easier to just use Axis 1 in your deployment.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.