• 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
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Approach for Generic and Reusable Client for webservices

 
Ranch Hand
Posts: 227
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Team,
Since a long time, i posted to this forum, We have one design issue in our application

1. Our application has to interface with third party webservices for a functionality [ lets say find Employee details]
2. WSDL is shared

Before going for the approach, we would like to see if we can build a generic solution
Option 1
going for Wsdl2 java stub based approach, but if schema of WSDL changes, we need to regenerate, recompile
Option 2
Going for the xml construction and use Saaj Api wrap the xml with soap
Option 3
Going for the java to xml - Jaxb and attach the SOAP + XML generated from JAXB
Option 4
is there any middleware approch to be gone

Requirement
a. We should have very limited change, even wsdl changes
b. Efficient way to maintain the code oop way


Kindly suggest what design pattrerns to use

Details
a. Jboss 4.2



 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic