Java Buzz Forum - Migrating smoothly from rpc/encoded to document/literal web services with Spring WS

Articles |
News |
Weblogs |
Books |
Forums

Artima Forums | Articles | Weblogs | Java Answers | News

Sponsored Link •

Java Buzz Forum
Migrating smoothly from rpc/encoded to document/literal web services with Spring WS

0 replies on 1 page.

Welcome Guest
Sign In

Back to Topic List

Reply to this Topic

Search Forum

Threaded View


Previous Topic		Next Topic

Flat View: This topic has 0 replies on 1 page

Max Zone

Posts: 9170
Nickname: dzone
Registered: Jun, 2006

dzone.com is a link-sharing community where member participation determines what gets published

Migrating smoothly from rpc/encoded to document/literal web services with Spring WS

Posted: Mar 15, 2007 9:12 PM

This post originated from an RSS feed registered with Java Buzz by Max Zone.
Original Post: Migrating smoothly from rpc/encoded to document/literal web services with Spring WS Feed Title: dzone.com: java Feed URL: http://feeds.dzone.com/dzone/java Feed Description: dzone.com: fresh java links for developers	Latest Java Buzz Posts Latest Java Buzz Posts by Max Zone Latest Posts From dzone.com: java

I've recently had to migrate Axis 1.x based web services to Spring WS. The Axis web services were rpc/encoded whereas the new ones use document/literal style. Rpc/encoded style is not interportable, generates bulky XML which is difficult to validate. However, I think they are still common for different reasons. In this context, migrating clients to the new service implies rewriting parts of their code. This could be difficult to manage if the service is public and the clients are heterogeneous, specially if they are not under your direct control. I thought about a simple way to achieve a smoother migration with Spring WS that I would like to share in this post.

Read: Migrating smoothly from rpc/encoded to document/literal web services with Spring WS

Previous Topic

Next Topic


	Web Artima.com