• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

designing webservices adapter

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I need information on designing webservices adapter for transforming transfer objects (implemented as EJB 3.0 in WebLogic 10) to web services object (Web service imlementation) and vice versa. The problem is as follows:

Currently the internal application logic is tightly coupled with the external communication:
· MDataWebServices endpoint portType messages are mapped to Java types that are dependent on Java types of others application modules
· MDataWebServices endpoint uses default Java-to-XSD binding
· MDataWebServices endpoint is based on Java-to-WSDL approach
· MDataWebServices endpoint is not versioned
· There is no dependency management integrated in build process.

All above-listed make uncontrolled endpoint WSDL and trouble versioning.

To resolve this issue MData web services subsystem and surrounding infrastructure need to be reorganized.
what tools do we use to solve the problem and what what design patterns can be used here and how?
 
reply
    Bookmark Topic Watch Topic
  • New Topic