Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

JAX-RPC to JAX-WS (Client impact)

 
Ranch Hand
Posts: 192
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We're 'stuck' for a while with JAX-RPC, OracleAS does not yet support JAX-WS.
I've just started with the POC to explore various issues we're concerned about, like authentication and binding, but for the moment it seems we might have to develop our 1st few web-services using JAX-RPC and later upgrade.

The impact on the client bothers me a little, banks tend to be reluctant to upgrade. There's a chance that Oracle will release 11g before the code goes into production, if that happens and we'll give the clients some new WSDLs that I imagine are mostly the same with different soap versions.
Long story slightly shorter, if our service is RPC and we move along to JAX-WS, is the impact on the client limited to downloading some new jars and generating a new proxy or will things like binding throw us a curveball or two?
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Taariq San:
The impact on the client bothers me a little, banks tend to be reluctant to upgrade.



Why would they need to upgrade? Are you supplying Java API stubs to them? If they are simply using your WSDL then design a WSDL that can be serviced by your current JAX-RPC implementation and existing JAX-WS implementations (like Java SE 6 or the JAX-WS RI) - it simply means that you are stuck with WSDL 1.1/SOAP 1.1 and a document/literal messaging style.

The main source of problems (from the client perspective) in a JAX-RPC to JAX-WS transition is that "contract-last" development , i.e. Java-to-WSDL, can lead to some very different WSDLs. That problem is eliminated if you switch to contract first, i.e. WSDL-to-Java development because you keep the WSDL (the interface) stable.

By designing the WSDL to be compatible which both technologies your clients don't even have to know that you are switching from JAX-RPC to JAX-WS. Once the switch is made and you want to use some of the newer features that are available under JAX-WS you can simply publish new endpoints with the new features for new clients or clients that are willing to switch.
 
Taariq San
Ranch Hand
Posts: 192
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Peer Reynders:


Why would they need to upgrade? Are you supplying Java API stubs to them? If they are simply using your WSDL then design a WSDL that can be serviced by your current JAX-RPC implementation and existing JAX-WS implementations (like Java SE 6 or the JAX-WS RI) - it simply means that you are stuck with WSDL 1.1/SOAP 1.1 and a document/literal messaging style.

The main source of problems (from the client perspective) in a JAX-RPC to JAX-WS transition is that "contract-last" development , i.e. Java-to-WSDL, can lead to some very different WSDLs. That problem is eliminated if you switch to contract first, i.e. WSDL-to-Java development because you keep the WSDL (the interface) stable.

By designing the WSDL to be compatible which both technologies your clients don't even have to know that you are switching from JAX-RPC to JAX-WS. Once the switch is made and you want to use some of the newer features that are available under JAX-WS you can simply publish new endpoints with the new features for new clients or clients that are willing to switch.



Nice news Peer, thanks for the insight.
 
No one can make you feel inferior without your consent - Eleanor Roosevelt. tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic